[1.1.53] Game to Continue not updated by Save
Posted: Wed Feb 16, 2022 3:06 am
I believe there is an inconsistency between how you remember the game "last played", for use on the Continue button, and what game should be used to pre-select a file for the Save function.
Here's a case that seems wrong to me. My backup strategy is to create another save each day I play, preserving what I had done the previous day. For example, say I "Continue game-23" from yesterday, and immediately "Save game-24 " for today.
If I play for a while and then save again, game-23 is preselected for me, but I think I've been playing on game-24, and if I don't notice, I lose my backup from yesterday.
Then when I come back tomorrow, you suggest I Continue game-23 (and it did actually save there, which is sort of correct), but I'm thinking I was playing 24. In the simple case I'll probably sort this out, but if I digress to play around in a test world for a bit, then come back to resume my "latest" game, I may not notice that it's missing yesterday's progress.
My workaround is to completely exit the game after first saving under the new name. Re-launching the game, it then works as expected, using game-24 for both Continue and Save.
Essentially, in the case I describe it seems to function as "Save A Copy" but keep playing in the current one, while I'm expecting it to behave like "Save As", creating a new save and then continuing in that one. My guess is that the fix, assuming you agree one is needed, would involve updating your memory of the last file used for saving, but there may be some reason you prefer not to do that.
This is not new behavior, and dates to sometime around the UI overhaul for 1.0, when Play (sadly) changed to Continue. I should also note the possibility that this is Mac-specific, though I doubt it. I'm currently on the latest release (1.1.53), and single player only.
I apologize for not raising this long ago, but it's fairly obscure, things mostly work fine, and my workaround is simple enough (as long as I cache sprites and prototypes) and has become routine. Thanks for your consideration, and exemplary work as always.
Here's a case that seems wrong to me. My backup strategy is to create another save each day I play, preserving what I had done the previous day. For example, say I "Continue game-23" from yesterday, and immediately "Save game-24 " for today.
If I play for a while and then save again, game-23 is preselected for me, but I think I've been playing on game-24, and if I don't notice, I lose my backup from yesterday.
Then when I come back tomorrow, you suggest I Continue game-23 (and it did actually save there, which is sort of correct), but I'm thinking I was playing 24. In the simple case I'll probably sort this out, but if I digress to play around in a test world for a bit, then come back to resume my "latest" game, I may not notice that it's missing yesterday's progress.
My workaround is to completely exit the game after first saving under the new name. Re-launching the game, it then works as expected, using game-24 for both Continue and Save.
Essentially, in the case I describe it seems to function as "Save A Copy" but keep playing in the current one, while I'm expecting it to behave like "Save As", creating a new save and then continuing in that one. My guess is that the fix, assuming you agree one is needed, would involve updating your memory of the last file used for saving, but there may be some reason you prefer not to do that.
This is not new behavior, and dates to sometime around the UI overhaul for 1.0, when Play (sadly) changed to Continue. I should also note the possibility that this is Mac-specific, though I doubt it. I'm currently on the latest release (1.1.53), and single player only.
I apologize for not raising this long ago, but it's fairly obscure, things mostly work fine, and my workaround is simple enough (as long as I cache sprites and prototypes) and has become routine. Thanks for your consideration, and exemplary work as always.