Shut Down All Servers Does Not Shut Down All Places In Universe

I have two places inside of my game, A and B. A is the main place and is the “game”.

When I am in A, and I “Shut Down All Servers” from the game page, the game shuts down.

When I am in B, and I “Shut Down All Servers” from the game page, the game stays up and I am not disconnected.

To shut down B, I have to navigate to the Places section of my stuff and shut each place in my universe down separately.

Main place:

Seems like this bug has been around for a while - Shutdown button on Develop page does nothing for universe places.

Is there any way to see how many players are in each of my places in a universe? The server list on the games page is not correct (I know since A has max players = 20 and B has max players = 80 and there are no 80 player servers on my game’s page).

13 Likes

There is a way to do this, though it’s tucked away in the Develop page.


19 Likes

Good workaround, but finding my game on that page is a PITA.

“Shut down all servers” should do what it says.

4 Likes

Shutting down all servers at once seems to be discouraged nowadays, given that it massively spikes your API usage for a few minutes while everyone is rejoining your game. On a large scale this becomes catastrophic, as we’ve seen with large updates to Adopt Me.

They recently introduced a feature called Migrate To Latest Update which gradually starves off old servers and teleports those players into new servers, without forcing them all out at once. It *might* work on a universe-wide scale?

4 Likes

We actually have a use case in World // Zero to have this not shut down all servers in the universe. When releasing a new update we don’t shut down mission instances, they get the update when they beat/fail the mission and are teleported back to an overworld. This will be true for battle-royale style games as well.

It’s nice to have explicit control over which place gets servers shutdown - but the option to shut down all places in a universe is really hidden

3 Likes

“Migrate to Latest Update” doesn’t help me test my code. I don’t even understand what the point of that button is. It makes no guarantees. I either care if players get new code or not. If I don’t care, I know they will all get my new update eventually. If I do, I really want them on it now.

Teleports don’t work in Studio so I have to test universe code live.

I don’t want to guess which versions of my code my different places are running.

5 Likes

Migrating to the latest update doesn’t allow us to instantly load users into the newest update and fix game-breaking bugs on previous versions. We have around 38 individual place servers we manually have to shut down each update. We would like an Shutdown Entire Experience option which includes all its individual places.

1 Like

Hi everyone, following up on this issue. Is there any assistance still needed? Thanks

I actually just came across the post, because I’m having sort of the same issue, where I have a Main Menu Place, and have multiple different places for other regions in the game, where players get teleported to. When I’m shutting down the game through the Main Place, which is the main menu, only that specific main menu place gets shut downed, and not every other place. The main idea would be to have a Shutdown All Places, so that every single place in the experience is shut downed equally. This would help a lot, since migrating to latest update sometimes feels a bit janky, and doesn’t really work.

1 Like

Am having the exact same problem