When teleporting to servers in World // Zero, we create a reserve server.
Occasionally, players will fail to teleport and see a popup such as this. This specific example happened on a Windows 10 client.
This causes users to have a horrible experience in our game as they are being pulled apart from their party group or friends, who go on to play the mission without them.
Additionally, clicking “Ok” does nothing and clients have to close Roblox. (This might require an app restart on mobile?). This is true for all disconnect messages, none of the buttons work. (Including when you are inactive for 20 minutes)
I don’t know about that.
I’ve got some pop-up messages like that, and some of them have been disconnected messages in Studio. If you go to the developer console > server and do game.Players.YourUsername:Kick(“Reason”) it does not work when you click the leave button.
Additionally, this has happened a few time on the client as well, when you do get kicked from some admin modules or when you do it as the methods listed above.
This is starting to happen absurdly frequently for me, tonight it’s been >50%. I’m also using reserved servers, in my case a static reserved server access code that is reused for multiple server sessions.
It seems like it’s 100% guaranteed to happen if the last server using the access code shut down recently within the last three or so minutes, but it’s also been crazy frequent for other servers that haven’t been open in >30 minutes.
We have TeleportFailed events but if Roblox is just bypassing that with their own error screen that closes the game it makes that event completely useless. Really wish this was fixed.
I was able to find a TeleportService event connected to the initialization failure that lets you retry in the case of a 771 failure: Teleport Error Code 771
Also just wanted to note that the 771 error code doesn’t close the game, and you can “override” it if you retry the teleport. But I agree it’s super annoying and shouldn’t need to be bypassed via a retry so often.
