Shutting Down Servers Under Sub-Places Causes ID=17 Connection

During QA testing prior to an update, I was in a server with my community’s game testers and we encountered an issue that required we shut down the server.

We have a “Soft Shutdown” mechanism that reserves a server of the same place, teleports all players in the current server to the reserve server, and then back to that sub-place again.

Using this mechanism and shutting down a server under a sub-place causes the return server to error and show an ID=17 connection error to all players attempting to rejoin. Consequently, this error will not resolve itself and my testers could not produce a new server under the sub-place until all users connected to the error server had disconnected.

The affected sub-place:

The universe (and main place) affected:

Expected behavior

Sub-places should have reserve-able servers that follow the same logic as the main place does.

1 Like