mirror of
https://github.com/yquake2/xatrix.git
synced 2025-02-24 21:01:45 +00:00
f83ea253c8
M_MoveFrame() calls first the AI functions that decide if a monster should attack or not. After that the monsters think function is called which walks through berserk_frames_stand[]. Even if the AI function found an enemy and decided to attack, the monster is still standing for this frame and berserker_fidget() is called. It may override the earlier earlier decision, aborting the attack. Even worse this may let the berserker stuck, because AI_STAND_GROUND may be cleared which prevents further attacks. This bug was present in the original code, so this is small gameplay change. It's likely also present in both addons. Reported and analyzed by @BjossiAlfreds in issue #433. He also suggested the fix. |
||
|---|---|---|
| .. | ||
| header | ||
| monster | ||
| player | ||
| savegame | ||
| shared | ||
| g_ai.c | ||
| g_chase.c | ||
| g_cmds.c | ||
| g_combat.c | ||
| g_func.c | ||
| g_items.c | ||
| g_main.c | ||
| g_misc.c | ||
| g_monster.c | ||
| g_phys.c | ||
| g_spawn.c | ||
| g_svcmds.c | ||
| g_target.c | ||
| g_trigger.c | ||
| g_turret.c | ||
| g_utils.c | ||
| g_weapon.c | ||