Autosaving constantly overwrites the first autosave file, and never makes multiple instances

Bug Reports Studio Bugs
#1

Issue

Due to a misinterpretation of Studio’s input where I had been saving to file on a published place, I had assumed exiting studio had published the place as well (as the tab of the place did not say the name of my local file, and instead had the published place’s name, which leads me to assume the latest push was to the website rather than to the local file).

As a result of this mistake, I have now lost about 7 hours of work due to loading up the online version of my game and instantly saving it to file after doing my first subsequent change to a different part of the game (I had only realized I was on an old version when it was too late). Upon navigating to my autosaves folder, I came to see that there was a single file for my entire place despite the many autosaves that occurred over my work time the night before.
image

Why are there not any more auto recovery files? Seeing the suffix AutoRecovery_0, that implies that Studio should be saving multiple instances of recovery files, not just constantly overwriting AutoRecovery_0

Reproduction

  1. Open a blank baseplate and save it to file with a distinctive name that you can easily recognize in the autosaves folder.
  2. Navigate to studio settings, and set the Auto-Recovery Interval setting to 1 minute (this should allow for quick testing)
  3. Make a number of changes, and wait for an autosave to occur.
  4. Repeat step 3 at least one more time
  5. Navigate to autosaves directory. I expect to see PlaceName_AutoRecovery_0 and PlaceName_AutoRecovery_1, but only see AutoRecovery_0.
13 Likes
#2

How in the world has this still not been addressed? I accidentally deleted something 10 minutes ago and cannot access it because auto-recovery has overwritten the file. Is there at least a setting/plugin to disable this behavior? I value my time and sanity over my disk space…

3 Likes
#3

This is an alarming fact, taking into account that this has always happened, to the point that I could even say that it is a feature of Studio, but not a bug.
However, now that I’ve realized that if there’s a “_0” suffixed to the autosave file, it indicates that this would serve for versioning, which in fact it never did.
So much so that I never thought to alert Roblox to this major issue, and I thank you for that.

Workaround

I already went through these problems of losing many hours of work due to this failure in the autosave, so I resorted to an external solution for versioning that has saved my life several times:

This program resides on the taskbar and allows you to make scheduled backups at the frequency you want and at the same time create versioning for each backup.
In short, this program will be able to do what Studio can’t do, that is, have a history of all your autosaves in various files and be able to refer to them on your HDD in case of any need.

1 Like
#4

Can’t you just download a copy of the game to your computer? This is what I do, just saying.