Joerg: please revert this once you've found the problem!
Unfortunately that commit 2006-10-10T19:57:14Z!joerg.hinrichs@alice-dsl.de did several things. This keeps:
1) The renaming of status to gamestatus,
2) The use of gamestatus's snapshot member rather than a standalone.
3) Changes to firing of events in replays
1) harm_weight is 1 - aggression, but we were handing aggression
directly in all but one place! This lead to negative aggression
settings becoming actively masochistic: rewarding self-damage!
Changed battle_context constructor to take aggression and convert
internally, since that is how it was being used.
2) aggression was only taken into account when comparing chance to
kill, not damage. This means that the bug above only showed up in
cases where there was a chance to kill. This may re-balance some
scenarios slightly.
I suspect this may have been involved in bug #6095 (AI too uncautions
with its leader).
fixes bug #7245 (stats in replay counted not from 0) and #6937 (at
replay end shows the scenario objectives). Also prevents to be thrown
back to the title screen if replay ends with victory or defeat.
- makes some use of gamestate wording more consistent
- enables (again) saving of events and variables for mp savegames
- uses the same gamestate information for mp saves, campaign saves and autosaves
- keeps replay information for mp saves so that they always start from
the beginning
- corrects the messed up savegame WML structure
I tested this in itself but not against latest changes: If there are
any incompatibilities/problems please tell me
