In absolutely no situation I can think of is autosaving AFTER a fight actually useful. Usually when you load an autosave it's because you'd like to try the battle you just fought again, with a different approach. By autosaving after fights, you render the autosave feature borderline useless and force the player to use manual saves when they need to savescum something.
At least, at LEAST use a rotating autosave with 3 files similar to Paradox games. Using a 1 save autosave that saves after fights makes the feature literally useless and removes the entire point of autosaves.
The last save for an autosave should ALWAYS be BEFORE the most recent outcome, NEVER after.
The only situation I can think of where this would actually be useful is as a quasi ironman feature, but you definitely don't want ironman mode to be the default feature in an early access game!
Two solutions here
1: rotating autosaves
2: save before fights, and not after.
Those are your options. Any other option is instant critical design fail.
At least, at LEAST use a rotating autosave with 3 files similar to Paradox games. Using a 1 save autosave that saves after fights makes the feature literally useless and removes the entire point of autosaves.
The last save for an autosave should ALWAYS be BEFORE the most recent outcome, NEVER after.
The only situation I can think of where this would actually be useful is as a quasi ironman feature, but you definitely don't want ironman mode to be the default feature in an early access game!
Two solutions here
1: rotating autosaves
2: save before fights, and not after.
Those are your options. Any other option is instant critical design fail.







