But seriously just allow us to easily switch between these behaviors. Sometimes Roblox is down or servers don’t want to respond fast enough and saving to the cloud fails like on the screenshot above. I don’t trust Roblox servers with keeping my data secure. One time it said that it saved it but, once I reopened my project all the changes I made were gone and since then I kept saving multiple times to the cloud and making a backup file.
There’s no such thing as ‘instant save’ and if you want to measure speeds, writing to disk will always be faster than uploading to a remote server (which has a higher failure rate). Saving to cloud is great but they shouldn’t be hiding basic features that users rely on behind multiple clicks, this is just bad UX.
A common paradigm that’s followed in software dev is to save locally and then sync to cloud in the background, this provides a smoother user experience in my opinion. It would be nice if Roblox set a default and then let us easily customize it to best fit our workflows.
Good feature, but as others are pointing out, please link the save keybind back to local file saving. Some people could be terminated by mistake, lose access to their account(s), or just want to keep the project as secret as possible. Many people are keyboard users and don’t want to have to use their mouse to save, so just bring it back.
I have a CreatePlaceAsync place as well and now I am not able to publish directly to that place anymore via studio. Saving via studio doesn’t work either. There is an HTTP 400 error in the output window when I try to do this. I need to update my place and saving/publishing to it still is broken to this day. Although this thread says now that cloud saving is disabled, it appears that something is still blocking publishing/saving to CreatePlaceAsync places. Please fix this soon!
Will this be fixed anytime soon? it has been weeks now and I unable to publish or save any updates to my games. This is very frustrating and there is no new information about whether this will be fixed soon.
Shortly after this feature got re-enabled some of the devs that I work with started getting “this place is unpublished” errors on their places despite the output clearly saying that the games have been published. One of them took like 3 people to publish for play testing.
It would’ve been nice to get a better heads up that this feature has been re-enabled than a lousy edit that no one got to see unless directly pointed towards.
Edit we have also lost 3 hours of work because of this behavior. Studio didn’t save an auto save because of the fact that it was thinking that it was published. A bug report will be definitely coming.