 |
When an AI is initially hit by a projectile, it is handled in method OnProjectileHit in State.cpp. This calls SetUpSearchData which, for a projectile hit, sets the alertPos in memory to a position halfway between the AI and the shooter. Presumably this half distance represents the AI knowing roughly where the shot came from and so would start going towards the shooter to follow up. This code is generic for all states. Unfortunately the shot then causes the AI to switch to the Pain state which, in its Init method, then sets the alertPos to the AI's current position, overriding the previously set value. Therefore the subsequent search starts in the wrong place. I think that the easiest fix would be for the Pain::Init code to check if the cause of the pain (which it does know) was a projectile and not override the alertPos in this case. |
|
|
Just to say that the previous note is for the 'firing an arrow from afar' part of the bug report. |
 |
Thanks for that information! I didn't realize a better algorithm for shot direction detection was once implemented, but a bug that's likely been around for over a decade is overriding it. Simply picking a location between the victim and attacker should be accurate enough: I was thinking the AI could trace a cone toward the player and pick points inside that cone to go to, but if the override problem can be solved it probably doesn't need to be that complex. The current behavior is definitely wrong though, I made a video which showcases how a guard goes searching in every incorrect place when I hit them from behind. https://www.youtube.com/watch?v=Bi-8CezzNqE Fixing this should improve players being able to attack AI with blackjack / sword without them realizing someone is hitting them if the player's light gem is dark, which technically is caused by the issue you described. What's going wrong is when you hit the AI it simply goes in a search state without attacking, which would work but they go searching in a random direction: If they picked the right set of positions, they would head toward the player and bump into them instead which would trigger an attack... since they only go around randomly they appear completely clueless instead. |
|
|
Seemed relevant enough to bump. Someone else encountered a very similar result on Moongate Ruckus and posted their own video. Having experimented with how AI react to alerts, I'm a bit more aware of what is happening here, and that apart from the FM specific lightgem offset this is a core issue that still exists. https://www.youtube.com/watch?v=w3ewvA1Q0wI |
- Anonymous
