I am still receiving reports of this on my game that teleports up to 4 players to a reserved server of a different place in the same universe. (Main lobby to arena)
I am also receiving some reports of reserved server teleport failures.
Game:
2 Likes
I just got the error again
oof
Still happening, I get DCed from 10 seconds to 5 minutes after joining any match, even in the main menu.
I also have this issue, Noticed it today only. I play Dungeon Quest and this happens pretty often.
This is still happening. I know that everyone is trying their best to fix this and an issue that is this long lasting has to be a difficult one to solve, but it is killing my games.
Last week, our game Ruddev’s Battle Royale was put into the featured sort. This game heavily relies on teleportservice to get players from the lobby / matchmaking place to where the battle royale actually happens, which means there is inherently a lot of waiting time. Despite our fair share of advertisements we put into the game, it wasn’t until the featured sort inclusion that the game received a boost in player counts (going from about 100 concurrent to peaking at about 3700 concurrent).
When the game was taken off of featured sort yesterday, we quickly realized that our player counts would rapidly drop for a bit and then stabilize, coinciding with reports from our community that they were being kicked out of the game with this exact error message. This had been going on for a few days but the featured sort acted as a natural way to soften the blow for players - it wasn’t until yesterday that we really started to see the negative effects this had on our game and our community. We went down to about 1200 concurrent players yesterday as a result.
Now, as this is happening again today, our numbers were approaching 400 concurrent players. Reports of this is still happening, with many community members asking us to fix our game, thinking that it’s our fault the game is broken. Through this we’ve had to spend money on the game to try and desperately get people in and stabilize the playerbase, but this seems to be resulting more in kids joining our game, thinking it’s a broken one because of this error, downvoting, and leaving.
Our game depends on a large amount of players to function and we saw the effects of low playercounts for a long time. We were incredibly happy when we saw the featured sort gave the game the jumpstart it needed in order to grow, but it seems now that we’re on the verge of all of that being taken away from us again. When we are constantly having new players think the game is broken, it will be increasingly difficult to get them back into our game to convince them that it wasn’t our fault that this was happening.
11 Likes
This has to be fixed if its still going on. This scared the heck out of me and I thought my account was stolen until i heard it was a bug.
1 Like
Thanks for the reports, we appreciate it!
Our engineering team has been actively monitoring & working on a solution to solve the issue.
If you continue to experience any issues please let us know.
3 Likes
Not sure if this is related, but when Roblox Player crashes, after relaunching, sometimes this happens repeatedly, and sometimes goes away when I refresh the browser tab I’m launching from…
It also resets the audio and sensitivity settings, which causes my ears to be blasted off (headphones are quite loud sometimes)
This is still an issue, happens quite frequently to players of Island Royale after teleportation. Getting sick and tired of it happening.
2 Likes
A few users told me that once there game crashes after using exploits this is an error they get when trying to rejoin the same server. I’m sure this is not the only reason but it’s a common report I get.
Closing topic as this issue is resolved. If you experience similar issues in the future please post a new bug report.