TCP error - quite frequent [SOLVED]

[Exotic_Retard]

this happens quite often to me - after ~80-100% of games, when switching tabs, and anything else which would request something from the server
- i presume i get disconnected after a few minutes but the lobby just doesn't notice until i try accessing it.

i have logs with me - they are quite reproducible - if you want more i can always give them. at a rate of one every few minutes sometimes

i get the impression that if im using the lobby for things other than chatting then i dont get disconnected - but im not sure though.
ironically when making this report i couldnt forcibly reproduce the error, but it happened a few times earlier in the day

Spoiler: show

i think that Sheeo was messing with me the entire time and fixed my faf as i was making this report, only to break it again in a couple of days

Sheeo told me this is going to be super useful so im gonna post it here

not sure how much you can get out of 3 lines but i dont know anything about code so yeah.

hope this helps !

edit: im not insane! i got another error! anyone else happy about their stuff not working?

[Exotic_Retard]

well i was all happy with this for a bit but recently its been impossible to play because i get (presumably) tcp error while in the lobby - error:"host has abandoned lobby" when he didnt actually - about 30 s after joining - and i need to refaf for trying to join again

given it took ~15-30 min for me to start a game - this is getting a bit inconvenient :/

hope this helps

in any case im waiting patiently for next lobby update hoping it will be fixed

[ckitching]

This sounds similar to the weird connectivity problems quirks of the server implementation create.

Hold tight, the upcoming server update will probably help considerably.

One of the weird things this can cause is to mistake any reason why you disconnected from the host as "host abandoned lobby". What really happened was you lost connection to the host for one of a variety of ridiculous reasons.

Thanks for reporting it! We'll work faster...

[Sheeo]

We're tracking it on our server repository here. Since the code has changed a lot since current deployment, it's likely a fixed issue already. I'll close it on github when I've confirmed.

The log was helpful, and typically they are with errors such as this. So in the future please do not hesitate