Oh okay, never heard of one of those but alright. This bug isnt one of em tho
We are testing a solution which has shown significant improvement for some beta testers. In the meantime, I have made a change so that you should get disconnected within ~20s of when the problem occurs, instead of “silently” disconnecting for minutes on end. This should be a slightly better user experience since you won’t waste your time on a dead connection.
Thank you all for your patience while we work on this!
16 Likes
This issue has been happening non-stop to me for ages, thank you for your hard work! 
2 Likes
Thank you for this! Although it’s definitely annoying that I’d have to rejoin entirely like every 5 minutes, it’s way better than not realizing you’re already out of the game for a solid 10 minutes.
I’d also like to add some info here that might help with troubleshooting. BEFORE this new update that now lets you know if you’ve disconnecting, you would only be disconnected on the client but not the server. Meaning that while everyone and everything including client-sided scripts would be frozen on my end, other people can still see me moving around. It’s as if my client is still sending data, but I’ve stopped receiving any data.
I’ve attached a video here that shows what each screen looks like when the other disconnects, and the other doesn’t.
Extra: When you are “disconnected” and you leave the game, it actually takes an extra minute for your account to actually leave the game. That means you need to wait a while before rejoining, otherwise you will just keep getting the “Same account launched in different device” error. This does not happen when you just leave while still normally connected.
12 Likes
Oh you have no idea how happy I am that you atleast made it so i get kicked instantly. Thank you for your hard work! Any progress on the fix or any eta? This has been an issue for ages and I cant wait to play roblox normally again
3 Likes
I am very excited to announce that the fix will be in version 671, which will be out on Windows/Mac next week (31st). Mobile to follow
I want to thank everyone who contributed to this devforum post, and a special thanks to those who posted/DM’d their logs to me. Also thank you to those who took it upon themselves to debug and investigate their network environments in hopes of isolating the variable. Without you guys this bug may have lived on for who knows how long.
Bug details
Without giving too much detail away, I will just shed a bit of light on what the issue was since we were all so invested in it. Certain network environments which are subject to more traffic re-ordering could activate a very old bug in our crypto algorithms, causing decryption to start failing, without recovery. It takes a certain amount of traffic (a lot), combined with reordering at a specific moment to trigger this. Which is why the bug was more prevalent for certain users, and on certain experiences. Moving forward, we have a much better grip on our traffic security code so issues shouldn’t go unnoticed again.
12 Likes
Finally, after 2 years, it’s going to be fixed—thank you!
6 Likes
Oh my god you’re making Roblox truly great again, THANK YOU!!!
3 Likes