If you save a game right before executing your planned move, this is too late... The planned move will be executed implicitly before the game is actually saved. See the debug.err file at http://pastebin.com/Ltht7ZuJ. (I could provide the autosave before the season plus the manually saved game.)
The above problem may be related to the proximity of a city. I have noticed also that units may change their position in a saved game if they are close to a city. This does not matter much though since movements through the city are free.
I can verify I have the same bug. Movement is used and units are at the end of their path when a game is restored (or at least for quick saves).
I've reported this bug so many times my fingertips are bleeding. Stardock doesn't care. Stardock doesn't care cuz half the people playing never notice including half the people at Stardock. Well I notice and I care and good to know that you both care, but Stardock doesn't care.
If saves are not reliable, that makes me very nervous and pretty much wanting to spend my time on something else...
I've come across this issue many times - even gone to battle when I didn't intend to. I guess the best plan for the time being is to 'zero out' the move orders before saving the game.
Stardock Counter-Savescum<sup>TM</sup>?
Seems like it would be easy to replicate and fix. But it's also easy to avoid, so pretty low priority.
I still would like to see a site to collaborate bugs and keep a neat/manageable log of all the bugs we stumble across. It would make tackling them easier for the staff too. I have no talent with webhosting though ;_;.
There are many great features available to you once you register, including:
Sign in or Create Account
