Closed igezt closed 2 years ago
Sorry, but this is a very generic issue and the cause is normally your internet. If there's no consistent rhyme or reason to these disconnects(which I do want to note, there's a big difference between a crash and a disconnect), then this isn't an issue with the game.
I can leave you with some extra information regarding these disconnects though. As you may or may not be aware, TETR.IO's servers are hosted in France, so your connection is always going there and back to send game state and inputs. This is why localized speed tests are not indicative of an issue on our end. If you press F8
ingame, you can actually see your ping live as one of the counters, although this may impact performance. osk has described the expired ribbon disconnect reason as such below:
your connection drops (for any reason), but ribbon is not able to fix it due to the high ping (15~25s depending on your luck) by the time your pc notices the connection's gone and is actually able to create a new one, so much time has passed that the server doesnt know you anymore
on the server: every 5s every socket is marked stale, and receiving a ping (pings are always client->server->client) will unstale it if a socket is stale but the 5s timer hits it, the socket is closed every 10s, all ribbons that do not have an active socket are marked stale, reconnecting correctly unstales it if a ribbon is stale but the 10s timer hits it, the ribbon is closed
on the client: every 5s a ping is sent, and the current socket is marked stale, receiving a pong back from the server unstales it if the 5s timer hits it again and its still stale, reconnect
Checklist
OS and Version
Windows 11
Browser and version
Chrome 97.0.4692.71
Describe the bug/issue
I keep crashing from something called "expired ribbon", cant quite remember what it is. But I've been crashed from 5 TL games of my last 6. I am not sure what to do
Reproducing
Expected behavior
I get disconnected with an error message
Screenshots
No response
Console logs
Additional context
No response