 |
Rather than having an AI tell MissionData about alert level increases as they are happening, it would be more accurate for stats purposes to precede this line in IdleState::Init() owner->m_recentHighestAlertLevel = 0; // grayman 0003472 with a call to MissionData to record an 'episode' of increasing alertness. This guarantees only one registration per 'episode' and eliminates the possibility of registering multiple times as an AI goes up and down and up and down in alert level after leaving IdleState. Ditto for AlertIdleState::Init(). |
|
|
From demagogue: "My intuition is it could be defined in a time band. If the level is ramped up in less than maybe 3 or 5 seconds, it should count only the highest, as if it's one event. But if it's more than that, they count separately, the logic being you were under alert and could have gotten out, but didn't, so get separate punishment. Or more generally, after 3 seconds or so in a dynamic situation, it's more fair to call the 2 interactions separate "events"." |
|
|
Moving to 2.05 because it's a large design change which could hinder getting 2.04 out in a timely manner. |
|
|
Moving to 2.07 due to the amount of work involved. |
|
|
Moving to 2.08 for the same reason: big design change. I'll try to get to it after 2.07 is released. |
 |
In the hopes of getting at least the loot total to render, I went poking around with this again. setting a static int for: int MissionStatistics::GetFoundLootValue() const { static int sum = 0; in MissionStatistics will render value out of x for loot but the value will be totally incorrect. I tried moving up the codebase to where LOOT_COUNT is inherited from but thus far have not been able to compile anything set to static up there. |
|
|
Removing myself as "Assigned To" because I doubt I will ever have time to work on it. |
- Anonymous
