As a Roblox developer, it is currently too cumbersome to set an existing Place as the Starter Place of an Experience, or to swap Starter Places between existing Places.
Right now, Roblox provides no native way to simply select a Place and designate it as the Starter Place.
For example, imagine an Experience with two Places:
- The first was created early on for initial development.
- Later, a second Place was added to serve as a “main menu.”
If I want the “main menu” Place to be the Starter Place, I can’t simply set it as such. Instead, I’m forced to override/publish Places to swap them around.
This process has several drawbacks:
- Versioning: Developers must mentally track when swaps happened, makes it harder to manage updates and place history.
- Developer confusion: Newer developers often struggle with why something as simple as swapping Starter Places requires such an unintuitive workaround.
- Scalability: As soon as you’ve overriden one or multiple places more than once, it becomes infeasable to keep track of when each override happened.
The entire point of having separate Places is to provide clean, self-contained containers for different parts of a game. The current requirement to override/publish into another Place undermines this purpose and creates unnecessary friction.
Proposal: Add a native option in the Asset Manager or Roblox Creator Dashboard to designate any existing Place as the Starter Place of an Experience.
(Mock-up of a button under Configure > Places)