As we announced in RDC, our team has been hard at work making improvements to the way you update your experiences. Today we’re happy to announce a number of changes and features we’ve made in the past few months to make releasing updates a better experience for you and less disruptive to your users.
We’ve heard feedback from the community that there’s been confusion around the update options available and what they do (and even whether they’ve taken effect). We’ve released new updated text, starting on Creator Hub, that better conveys what’s going on, which includes the renaming of “migrate to latest update” to “restart servers for updates.” We’ve also updated our documentation to more clearly convey what’s happening.
We added the ability to use “migrate to latest update” to update an entire experience, not just a single place within an experience.
To access this, you can navigate to your experience thumbnail on the Creator Hub homepage:
The “migrate to latest update” option has taken up to 6 minutes to complete an update. We’ve now optimized this so that for the large majority of your experiences, this will complete in less than 1 minute. Now, only the largest of experiences on the platform will take closer to 6 minutes. Servers running older versions will stop being considered during matchmaking the moment you start the update.
As we’ve announced at RDC and the creator roadmap, when players are kicked out of a server due to an update we save the state of the server so that players are able to stay with the same set of players when they rejoin. We also will start replacement servers in advance for these players, allowing them to rejoin almost immediately.
Privating your experience now closes all places within your experience, not just the root place.
For the past few years we’ve had two different options for updating games: “shut down all servers” and “migrate to latest update.” We’ve seen developers repeatedly getting confused about the differences between the two. We’ve even seen top developers press both buttons just to be sure their updates are working.
With prewarming, “migrate to latest update” has become the better option for players - our data shows they get back into the game faster, play longer, and quit after rejoining to find a new server less frequently. On top of that, it doesn’t unnecessarily kick players that are already playing on the latest version.
We’ve heard concerns about this feature though - the feature was not well documented, it launched with some bugs, it was only available for individual places, and took a long time even if you only have a few instances to update.
We’ve heard you loud and clear, and we’ve now corrected these drawbacks through the improvements described above. In order to remove the confusion around these two features and simplify development going forward, we will be consolidating to “migrate to latest update” as the primary update option to improve clarity on what is happening.
We’re releasing auto-reconnect (described below) after the holiday season in early 2024, at which time “Shut down all servers” will be retired.
Moving forward you will have the following options to close servers for updates:
- Restart Servers for Updates - Used for normal game updates. Updates your experience or place in less than 1 min for most experiences. Players get to rejoin with a new server ready and with the same set of players. Servers running older versions will stop being considered during matchmaking the moment you start the update.
- Make private - Used to stop game-breaking bugs. Immediately kicks all players at the same speed as “shut down all servers” and prevents new servers from starting and players from reconnecting.
If these options are not sufficient for how your experiences are updated please share your feedback with us so that we can ensure all use cases are accounted for.
One of the most requested features around game updates is to have Roblox automatically reconnect players instead of just disconnecting them. While we aren’t ready to release this yet, a lot of the work that’s gone into “migrate to latest update” has moved us closer to being able to do this.
As we shared in the creator roadmap, we are continuing to work on making this happen, and we expect this will be released after the holiday season in early 2024.
Please let us know if you have any questions.