Don't change default studio shortcuts without notice (data loss, missed game publishes)

In the last year, ctrl+S was changed from Save to File to Save to Roblox.

I work from local files, and there was no notice that the behavior had changed unless you paid very close attention to the output. I open the file, do work, save to file. At this time I was adding features that did not depend on or see each other, so I was able to work for days before realizing that I was opening the same file every day and it was not saving. I lost several days of work.

More recently, alt+P and alt+shift+p were also changed from Publish to Roblox and Publish to Roblox as to Save to Roblox and Save to Roblox as.

In the last week, I made several updates to Lumber Tycoon 2 which did not actually publish. Once again, everything appears normal unless you scrutinize the specific output text. I thought my update was published almost a week ago but it was not, and as a result I have to further delay my game update.

These changes are negligent. Don’t silently disrupt developer’s workflows. If a critical shortcut like this is changed, a prominent notice must be shown.

13 Likes

I raised a stink about this ages ago when the change happened and was forced to switch to a feature request that was subsequently never followed up on. This + all critical dev output getting dumped into the console instead of literally anywhere that’s visible was a major source of accidents for me for multiple years.

The “fix” for my workflow was giving up and doing things the way they’ve forced me to: with team create, cloud saves, and faith that I’m not about to have moderation shove a rake down my throat and delete 8 years of my life’s work, with the occasional to-file backup. :slight_smile:
(In case there was any question, this is not acceptable.)

5 Likes