Someone just raised a change request, asking for Ironman to save less frequently: [1.4.1.8] (Change request) Ironman saves too frequently.
The OP of that thread asked why it had to save so much, and couldn't it just save only on game exit. I pointed out that it was to avoid you cheating by reloading when something bad happened; with the current system, you can at most reload to the start of the current month.
Then I had a thought: how about if Ironman only saved once yearly, but then also saved whenever you open the Menu? The yearly saves would be for protection against crashes and so on. The Menu save would prevent you ever reloading in case of something bad happening.
So the behaviour would be: Whenever you open the menu, the Autosave message pops up, and the menu does not appear until the Autosave completes.
The result:
The key part of the optimisation is 'in this same load'. This optimisation would allow the user to open the menu a few times in succession, even across a few days, without it saving every time. It would thus allow him to cheat once to reload back to nearly one week ago, in case of bad event - but only once, it would not let him keep cheating over and over, and that's because the "don't save if last saved less than a week ago" part only applies until he reloads.
Example:
The OP of that thread asked why it had to save so much, and couldn't it just save only on game exit. I pointed out that it was to avoid you cheating by reloading when something bad happened; with the current system, you can at most reload to the start of the current month.
Then I had a thought: how about if Ironman only saved once yearly, but then also saved whenever you open the Menu? The yearly saves would be for protection against crashes and so on. The Menu save would prevent you ever reloading in case of something bad happening.
So the behaviour would be: Whenever you open the menu, the Autosave message pops up, and the menu does not appear until the Autosave completes.
The result:
- It saves the game nearly twelve times less frequently
- So it runs a lot faster when played at high speed.
- You can cheat even less than you can now - you can never reload to avoid bad stuff, because as soon as you open the menu to load, it saves again!
The key part of the optimisation is 'in this same load'. This optimisation would allow the user to open the menu a few times in succession, even across a few days, without it saving every time. It would thus allow him to cheat once to reload back to nearly one week ago, in case of bad event - but only once, it would not let him keep cheating over and over, and that's because the "don't save if last saved less than a week ago" part only applies until he reloads.
Example:
- Nov 11 1444: User starts a 1444 game
- Jan 1st 1445: Yearly autosave
- Oct 20 1445: User opens the menu = SAVE
- Oct 23 1445: User opens the menu again, = doesn't save, because it's <7 days since last save
- Oct 26 1445: User gets a bad event!
- Oct 26 1445: User opens the menu again (= doesn't save, still <7 days since last save) and reloads; he loads Oct 20 1445
- He can only load back 6 days, not to start of month (26 days in this example) like he can currently in Ironman
- He can avoid this bad event.. but only once, as you will see:
- Oct 20 1445: User plays again from reload
- Oct 26 1445: User gets a bad event again!
- Oct 26 1445: User opens the menu to reload... = SAVE, because although it's still <7 days since last save, he has since loaded the game again - this is a new load
- So he cannot avoid the bad event a second time, only once, and he can only load back 7 days at most.
- This is even more secure than current Ironman, but it uses far fewer save games to achieve it.