File backups in development builds #610
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There has already been an incident that there is a break of preferences by 9de1e2a (originated from #425; attempt of fix as in #503). Ideally, this kind of save file scheme changes should always be conducted and followed-up so as to preserve the quality of version continuation on save files, even on pre-releases. This is related to the quality of pre-releases.
Then, in case of save file corruptions, this allows backups of both preferences and world saves. Backups of preferences are performed automatically when saving and upgrading preferences with development builds; backup prompts are shown when users are attempting to load old worlds in development builds. (This might be extended to generally all versions, and all loadings of conflicting versions respectively.)
(Edited on 2023/01/11)
Old summary