 |
Note from demagogue: "Just on the stealth score, for future reference, when rising levels are connected, it might be good to have the system register the highest alert and cap it there, until it goes back down to zero, then the system resets. Then running and hiding won't be more costly than coming into view and fighting. But it has to be thought out too. A player should expect a higher score if they prolong the running too much, so it could recount after maybe 30 sec or so as well." |
|
|
Moving to 2.05 because it's a large design change which could hinder getting 2.04 out in a timely manner. |
|
|
For now, I'm not going to introduce a addition to the stealth score for running around for 30s or more while spotted. This represents a new way of looking at things, and means creating future registration events based on timers, and knowing when to disable those timers if the player manages to hide before the timers run out. It's too much for me to add timers and their maintenance at this stage. |
|
|
Track alert events in a list for each AI, and register meaningful alerts when the AI returns to Idle State or the player reaches Mission Complete. Measure the amount of time the AI spends in each Alert State as it rises toward Combat, and only register those that indicate the AI spent “some time” there before rising again. “Some time” is defined as half the time allotted for ramping down in each Alert State, with both Searching and Agitated Searching clamped at 10s. Rev. 6609: AI.cpp AI.h IdleState.cpp MissionData.cpp |
 |
Anyone checked that sighting objective still fails after this change? |
|
|
Do you have evidence that it fails, or are you asking because you looked at the code and found something wrong? |
|
|
How about this for evidence - a guard sees player and attacks but the objective does not fail? Map is Talbot Collateral here. |
|
|
Good evidence. I'll look at the objectives in that map and see what's happening. Edit: An optional objective in Difficult mode is to not have any AI rise to an alert level of 5 (Combat) because of the player. If the guard is attacking, and no "objective failed" message is displayed, then there's a problem. I'll look at this today. |
|
|
The problem lies in waiting until the AI returns to alert level 0 before registering the highest alert level attained. An objective like this optional objective needs to be registered immediately, instead of waiting for the AI to return to 0. Perhaps a better way to solve the OP problem is to register the alert level changes, but to have lower alert levels removed from the Statistics math when they are overridden by a higher alert level in the same alert cycle. (I.e. don't wait until returning to level 0 to register.) |
|
|
Now the registration occurs immediately, but if a subsequent alert on the same cycle (the time between being at Idle, rising in alert level, and falling back to Idle) occurs, the “counting” of the previous alert is undone, based on some time durations between alert N and alert N+1. Rev. 6671: AI.cpp AI.h IdleState.cpp MissionData.cpp |
- Anonymous
