Omg i died!!

[kovah]

Errr... Yeah.

Scenario: 4 level 7'ish folks are fighting things in the Viridale.

One of the four get's rushed and dropped to unconcious by the bad guys. (yes my spelling sucks) The npc's that knocked said person unconcious, instead of turning to the immediate threat of the other 3 that are still actively beating on them, continue to beat on the unconcious person.

Now, I don't know what you would do in this scenario.. But, if it were me, i would immediately turn and begin fighting those that are still beating on me instead of the clearly non-threat that the passed out guy poses.

Back in the day Sundren NPCs used to completely ignore you, even if you were solo, when you got knocked unconcious. This did not make sense and I understand the change. What irks me is when I'm in a party and get dropped, the NPCs keep hitting my laying on the ground clearly no threat to them self instead of focusing on the immediate threat of those still actively attempting to kill me.

Is there any thought to disallowing this practice once again? Yes, solo it makes perfect sense, GET IN A GROUP YOU FOOL!!!! but why would something continue it's attacks against a target that isn't harming them when there ARE other targets trying to kill them?

Does that make sense?

[The Almight Red]

I think it makes entire sense. In fact, it made me wonder about the system of stabilizing, because of this.

It makes the stabilization system (adapted from PnP I assume) almost a moot issue, unless your team has time to kill everything before the mobs smashing the unconscious person can get them damage by 10 more points (at maximum!).

I've been told that coding AI can be a very, very lengthy process, so it's understandable that these types of changes take time.

But I certainly agree that it makes little sense for everything to gang up on the incapacitated person until they're dead, before focusing their attention on others that are actively looking to harm them.

If the AI was changed to leave alone someone incapacitated when other hostiles were present, it makes that crossing of your fingers to stabilize all the more viable. You hope and pray that you roll well on Fortitude as your mates dispatch the rest of the baddies. It brings in that nail biting prospect again, which is always fun.

[Iso]

I get Kovah's point and will just say I agree, it does seem strange that they aggressively attack unconscious people instead of trying to knock others unconscious. Almight is also right, the AI design to instruct them to disengage unconscious types and go after the ones still standing could be difficult to impossible to implement.

If the Sundren team could make it happen, more power to them.

[DireBadgerEntersRage]

I, too, support this idea, and hope it's doable.

[KimKandor]

I don't think it's impossible, it calls for a faction shift momentarily for the unconcious and an imediate stop of actions on the attacker, otherwise he'll continue attacking for another round. It's been done for years in nwn1 harking all the way back to the HCR days. Not knowing Sundrens AI editing I can't be sure what would need changing here.

Funny, that exact scenario just happened to me yesterday, in fact I was way at the back of the group trying to formulate a strategy when another player began attacking with some darts. Suddenly, the chief and 2 other goblins rush forward, surround me, and continue attacking me after I was unconcious untill ultimately I was dead. I had rolled well and would have recovered. My companions were attacking them as this happened, I had been the last to shoot an arrow. While unconcious, one of my companions tried to heal me. The onslaught was so intense, that even with the healing, and the stabilizing it was futile.

That's happened to me more than once, though not as obviously as in that particular time, and I've seen it happen to others I've been partied with. I'd also like to note that all three of us were the same level in that party, and all of us about the same xp from a level. Tis frustrating for sure.

[GodBeastX]

Beating on bleeding people is a known issue. Apparently the code I wrote back in the day to ignore bleeding people isn't working these days.

*Goes back to drawing board*

[Iso]

It was nice while it did!

[kovah]

It was nice while it did!

It was great when I was soloing! You even got ignored for a few seconds which gave you time to pot/heal/stealth! It was pure hax!

I'd not want it that way again personally, but while in group... Now if that could be changed I would love you long time.

[gbbishop]

i think this would be great! apparently gbx agrees if he once wrote code to do just this...

[Fezzik]

The question remains though, is the person continually beating until the affected corpse is dead, or is it just doing it until the end of the round? They have always beat on people until the end of their round, then ignored them... until someone healed them to a few hit points in which case I'm sure there is a code somewhere that says something like...

{ If(GetPlayerChar(GetNearDeathDude))==WasJustBeaten DownandThenHealed())
. { Attack()=CriticalGuaranteed(GetNearDeathDude);
. }
}

[grant]

Fezzik, you forgot the ...or the player is lagged and unable to heal then swarm character line of code.


Yes from personal experience (solo) spittlefist archers at least will keep firing arrows into you as as long as you lay there. In a party setting both the onscreen action and the combat log have been so chaotic that I have not seen if it is true or not.

[Thief Of Navarre]

Seems a bit silly I agree, perhaps the patch changed things so existing code doesnt work as intended. I dunno, speculating..