When I save to file, the Ctrl-S save location should never change even if I publish

As a Roblox developer, it is currently too hard to make sure I’m saving my game where I expect to save it, which is dangerous and can lead to data loss.

I currently edit my game by loading it from Roblox, and work in Studio. I save periodically to a local file by using Save As (it’s much faster, is more visible and assuring when it succeeds, and I prefer this also for other reasons), and then use Ctrl-S from then on as I work. When I’m ready to publish, I will publish to the website via File > Publish to Roblox, and then I will continue working. When I’m done working, I will publish and close Studio.

However, after recent changes to how publishing works in Studio, when I publish to Roblox, this will reset my Ctrl-S location so it will save to Roblox instead of to my local file.

This is confusing and causes me to very frequently accidentally save to Roblox without realizing, which is extremely bad because if I assume I’m saving to a local file but I’m actually not, this could cause me to lose a lot of work depending on what I do next. Studio does not communicate that a save has succeeded properly, nor where it is being saved to. The output widget is extremely out of the way, and is not always focused. This should never change without me explicitly changing it.

If Roblox is able to address this issue, it would improve my development experience because I would always know where I’m saving to. If I explicitly choose to save to a certain place with a certain saving mode, I don’t expect it to ever change unless I explicitly change it.

Part of why I save to a local file is because I value ownership of my own files (i.e. I don’t trust Roblox to keep my game due to concerns about moderation, cloud availability, I want redundancy, etc). Roblox needs to be accommodating to users who don’t want to work directly out of the cloud.

The cloud is much slower than my local drive as well, taking multiple seconds to save during which time if I use Studio, I’m unsure which version of my game is getting published, or if me using Studio will mess it up.

There’s also very minimal feedback when a cloud save succeeds. It feels unsafe and flimsy.


It looks like this resets to saving to Roblox if you test your game too, but only sometimes?

1 Like

I’ve noticed this too, which I actually lost some data (not a lot thankfully) but I lost it because it saved to a local file instead of to ROBLOX. And then ROBLOX updated preventing me from retrieving it.

Not sure if all ROBLOX updates break saves, but in my case it did.

It doesn’t make sense since Alt+P = publish, Ctrl+S should only be to save to file.


This is still spoiling my workflow. I have to constantly adjust where I’m saving to as I work throughout the day and I feel like I can’t trust Studio to save my file properly anymore.

I have to explicitly choose the save option from the file menu that I manually open with my mouse and then verify in the output it saved to the right place because ctrl S is unusable and ruined because of this problem.

1 Like

This is getting in my way again. I am trying to test mobile stuff on device by publishing and launching the game on my phone, but I’m working on the tech in a local file (because it’s just a script in a baseplate, I want iteration speed over completely pointless cloud cruft slowing down everything I do).

Every time I publish it changes my Ctrl + S location and because I expect to be working on a local file for this project, there is a high chance of me wasting a bunch of time because of accidentally cloud saving, loading from local file next time, and then cloud saving over it, and then needing to go figure out how the version history labyrinth works.

Bottom line this is horrid UX for the majority of my workflow.


I agree. There are certain rules that every computer user expects to stay the same that you just should not touch no matter how “innovative” you think your new solution is, the save feature is one of them.

1 Like

until Roblox acknowledges the feature request, here are two bandaids that may help:

setting a short cut:

simple plugin to warn you in output: