NPC State: npc freeze/no-movement

[MikeJeffers]

Tends to occur when hostiles are too far, unable to resolve path, but sometimes in other cases - unclear on the edges of the problem.

NPCs should always fallback into a state that is somewhat logical. Idle/no-movement is not acceptable when being aggressed.

[aqpanaciy]

I have been studying this problem for a long time. There are at least three reasons why NPCs don't move while aggro:

• if the player does not move, then according to this condition, the entire analysis is skipped;
• here, when searching for a new path, the NPC stops and if the search fails, it will continue to stand. The old path is not reset, and the NPC tries to move along it at zero speed;
• for some unknown reason, here the start and end points of the path coincide, and the vector after normalization has NaN values in components. Accordingly, far Update(...) does not work.

[aqpanaciy]

Work plan:

• rework the < void UpdateHostile(TimeSpan time) > method to analyse even stationary targets in AggressorAI;
• when stopping the NPC, reset the path to NULL;
• fix WaypointMovement;
• сheck other conditions that may cause the NPС to freeze;
• develop a test plan for the changes described above;
• test according to plan.