Studio's startup widget repositioning can cause undesired instance insertions whilst loading an experience

Reproduction Steps

Part One

  1. Open Roblox Studio
  2. Open an experience, observe that as its loading, not all of your widgets load at the same time. Some of them quickly reposition to another location once Studio has completed opening.

Part Two

  1. Open Roblox Studio
  2. Open an experience from the UI, but click it multiple times as its opening
  3. During the widget reshuffling, it’s possible that the “Insert Basic Objects” widget will have temporarily been underneath your mouse cursor as you’re clicking a few times
  4. Observe that you inserted either a Part, Tool, or SpawnLocation by accident
  5. Your camera shows it for a split second, but then readjusts back to where you last saved your experience; if you weren’t paying attention, you may accidentally publish your experience without noticing this new addition (and if it was a SpawnLocation, this is VERY bad)

To help with repro, my Studio layout looks like this:

Throw a few spam clicks onto the first experience on your list, especially on the left side

Studio looks like this for a few seconds whilst the rest of the widgets load

Studio looks like this once everything is loaded

Expected Behavior

Widgets cannot be interacted with whilst Studio is still reshuffling them + loading, or even better, the widgets don’t reshuffle at all.

Actual Behavior

The widgets reshuffle, if you double-triple+ clicked on your experience, you may’ve just accidentally inserted an undesired object - especially a SpawnLocation.


Be incredibly cautious when opening an experience.

Issue Area: Studio
Issue Type: Other
Impact: Very High
Frequency: Often
Date First Experienced: 2023-02-04 00:02:00 (-08:00)
Date Last Experienced: 2023-02-04 00:02:00 (-08:00)

Thanks for the report. We’ve filed a ticket to our internal database and we’ll keep you updated on progress!

1 Like

Today, opening a place is semi blocking and you can end up with weird issues if you try to interact with the application. We’re looking to make this a better experience in the future.

The bug appears to be marked as “Closed.” I still encounter this on a weekly basis and would say this is still an issue.