 |
These are the conditions where an AI would flee: 1 - Reached combat state, but unarmed, or is marked "is_civilian" (armed or not). 2 - Has a ranged weapon, but no melee weapon, and finds himself in melee range (too close to use his ranged weapon). This seems like an odd one, since I'd assume that an archer, for example, should shoot arrows at you from any distance. Just yesterday I watched an archer run away from me, then turn and shoot. Maybe this needs to be looked at. 3 - Health level drops below "health_critical", regardless of whether they're armed or not. 4 - An unarmed or civilian AI is hurt in any way. 5 - Witnessed a death or KO, and is unarmed, or is a civilian. 6 - Hit by an arrow, and is unarmed, or is a civilian. |
 |
Ah, it was probably 2--there was an archer present. I don't have strong objections to him running back out of melee range before firing at you (seems like a prudent thing to do), but he probably shouldn't be playing his "flee" barks when he does it. edit: I'd also be fine with him just shooting at any range, if that's easier. |
|
|
Turn off flee barking when an AI with a ranged weapon and no melee weapon gets too near an enemy. The AI will flee, then reassess his situation. If he can still see the enemy, he’ll start using his ranged weapon. Fixed an old bug where an AI wouldn’t leave Flee Done State if he spotted an enemy. Rev. 5820: CombatState.cpp FleeDoneState.cpp FleeState.cpp PainState.cpp State.cpp AI.cpp AI.h |
|
|
I'm not marking this RESOLVED at this point. If the original problem was caused by the archer yelling as he fled, this fix should correct that. If the original problem was caused by something else, that's still around. We'll see if the problem arises again. |
 |
No reports after v2.0 |
- Anonymous
