Autosave Recovery for ACTIVE map
Autosave is great, but it only works for saved maps.
Many users have inspiration and hyperfixate on building, and don’t consider that they may not have even saved the map yet.
Because Dungeon Alchemist doesn’t prompt users to save the map when starting the build, you’re expecting them to remember to stop building and save, which risks losing hours of work if you encounter a problem.
Autosave should ALWAYS save your current map on the autosave interval to AppData, regardless of whether you’ve manually saved or not.
After the set amount of Autosave versions, old auto-save files would be deleted from AppData preventing bloat.
This allows users to focus on building maps without worrying about losing progress if they were too inspired and forgot to save over hours of work.
When it’s saved, that autosave should also be in your Map’s save-file location for ease-of-access, but still be located in AppData as a system default for crash-recovery.
This also allows users who are inclined to find the solution to find their unsaved project in the AppData autosave instead of starting from scratch, in the instance a crash-recovery does not work.
Comments1
Izaac Fabian
Apr 8
Personally I think an AppData folder or C:/user/Documents/Briganti folder for an autosave backup of any working map on the autosave interval would make sense.
This way, it's not located in a user folder, but it is backed up locally on the interval chosen regardless, and can be treated as temporary files and overwritten / deleted as your next interval hits.
It'd just be untitled-date-time-autosave.dam or whatever and located somewhere the user could locate it under the situation where crash recovery doesn't work.
Similar to how Premiere works explicitly for that reason