You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
updated to 0.C-28866-gbb41bf6 (tiles) from a build that was a few days old, and got an error that said that my save file folder wasn't empty. Figuring it a bug, hit update game again. Repeat bug. Checked my saves in current, empty. Checked my backups, empty. Checked my previous version saves, empty. Previous version manual backup, one folder. Please either impliment a revert if it throws an error, or otherwise resolve this potentially disasterous bug.
The text was updated successfully, but these errors were encountered:
Happened to me too, but I backed up my game into a different directory (before changing the launcher setting to use a subdirectory) so I was able to recover it.
And as I mentioned in another issue, it can also error when restoring the previous version. I tried to use that feature but all it did was empty the config folder and refused to do anything further.
There could be better solutions to this issue than what we current have. One would be a reworked file operations queue with Cancel and Retry options when an issue with the file system is found.
This is not an easy thing to solve but with time and efforts, we can get this going.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
updated to 0.C-28866-gbb41bf6 (tiles) from a build that was a few days old, and got an error that said that my save file folder wasn't empty. Figuring it a bug, hit update game again. Repeat bug. Checked my saves in current, empty. Checked my backups, empty. Checked my previous version saves, empty. Previous version manual backup, one folder. Please either impliment a revert if it throws an error, or otherwise resolve this potentially disasterous bug.
The text was updated successfully, but these errors were encountered: