Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Autosave bug in 0.53 #487
The presence of .bkp files is 100% related to the "windows blue screens", it means he was not able to save and return to the main menu successfully (btw, if there were .tmp files means something wrong happened during the game being saved and would be more problematic).
"Player not found" means:
TODO the flow above could be improved: the current dungeon level, with player at the dungeon exit square should be saved with the player STILL present on the dungeon level, and a .bkp file be created AFTER that, because between the last .bkp and trying to exit the dungeon level, happened things that would be lost if the AutoSave functionality didnt happen in between, but I think this may be just a minor improvement (not sure tho).
ok, if he manage to upload the compressed savegame it will help but I guess it will still be a big upload.
I think ivan 0.53 is quite old code related to fixing such problem.
Also, if he wants to try manually fixing it, he can (backup all savegame files first, and then...) rename all .bkp files removing ".bkp" from them, and try to load the game again, the player will probably still exist in one of them! Unfortunalely this is not so simple to recover the savegame correctly, see below :/
now, thinking better, the game should NOT keep so many backup files...
There are many files saved at 10:32 PM (the newest save time), the seconds (even miliseconds) would help more tho...
When you discover the correct one do this:
But.. it will be even better if he install v0.54 and manage to successfully import the old save (because of all new features and fixes including about recovering from lost/dup player), but that is not granted at all, so initially putting effort on trying to manually recover still at v0.53 is more granted to work.
PS.: anyone feel free to post a shorter reply summarizing this bloated comment I did if it helps :)