[Bug][0.85] Loading an Auto-Save kills new units

While loading auto-saves has quite a few problems, such as automatically moving units on load, I'm just going to report this one particular issue for now.  This issue has been reported before, but perhaps not with steps to reproduce.  Also, it's still a problem in 0.85, so still worth mentioning.

1. Set auto-save to save every 1 turns (otherwise this will be annoying to reproduce since you'll have to match up the turns).

2. Start training any unit in any city.

3. When the unit is finished training, load your last auto-save. 

4. Your new unit is gone.  The city's queue is empty.  If you spent resources to start training the unit, those are gone, too.

Normal saves do not seem to have this problem, only auto-saves.

3,774 views 3 replies
Reply #1 Top

I noticed this too. This really needs to be fixed.

Reply #2 Top

Reloading on an autoload kills several events. If you just hit a fame milestone and get a Champion on an autosave, if you reload the autosave, you miss out on the champion. If a wandering monster attacks your unit on an autosave turn, you can reload the autosave and the monster will not attack. As I can figure out, any event at the start of the turn gets lost when loading an autosave.

 

Reply #3 Top

Actually you can call the entire loading button broken, there are a lot of things wrong when you are reloading a savegame and the root of the problem seems to be that when reloading a savegame, the current session basically runs through an entire turn and does not stay at the time it was dumped into the savegame.