 |
Here's what's happening ... When an AI is alerted, the event is logged in mission statistics based on the AI's alert level at that moment. A simple counter is kept per alert level, and the counter bumps up by 1. If an AI hears a player footstep, that raises his alert level a small amount. If he hears enough footsteps to raise him to alert level 4, he'll draw his weapon and start searching. Along the way to level 4, each footstep registers as a unique alert for the level the AI was at when he heard it. So we might see statistics similar to the following when the player walks toward an AI, but stays out of sight: Alert level 1: 1 Alert level 2: 1 Alert level 3: 1 Alert level 4: 15 Alert level 5: 0 If the AI spots the player, the sighting is one alert event, and each subsequent player footstep as the AI chases the player is registered as a unique alert event at level 5, and you can easily end up with stats that look like this if you lead the AI on a long chase: Alert level 1: 1 Alert level 2: 1 Alert level 3: 1 Alert level 4: 15 Alert level 5: 150 We took care of the cascading for level 5 by simply tracking unique sightings and total time seen, so that changes the stats to: Alert level 1: 1 Alert level 2: 1 Alert level 3: 1 Alert level 4: 15 Alert level 5: 1 It still leaves the high '15' value for level 4, though. I'm guessing the original intent was to track the number of unique events that raise an AI to a particular alert level for the first time. The code is not doing that. Instead, the code counts the number of times an AI is found to be at a certain level when an event occurs. |
|
|
Only bump the alert stat counts if the AI’s alert index increases. Also fixed a bug in keeping track of the previous alert level, when the level wanted to cross indices but was capped. rev. 5293: AI.cpp |
- Anonymous
