Client side ping’s fail must send warning for a player (instant disconnect and concede problem)
Possible problem: in rare use cases with bad/unstable connection some users can catch instant disconnection and concede.
Possible reason: If game do nothing and no any messages from a server side (e.g. game waiting someone’s action) then only background auto-ping feature help to keep good connection status. But it must be research/confirmed.
Another possible reason: jboss network’s inner timeout and ping fail (example: xmage client has too big ping timeout so jboss network fail first).
Possible fix: inform player in all game chats about ping fail and reconnection require (it must be client side message like messages about connection problem of other players).
Not sure if this is the case or not, but I have been under the impression that when the player that created the match has connection problems, they are more likely to get booted and insta-concede than if they are playing in a match created by their opponent.
Just had an interesting case where a short disconnect caused the player to instantly concede the match, but they weren't kicked from the tournament.
Also, it'd be nice if drafts had some sort of reconnection logic as well, letting a player rejoin and take whatever cards the draftbot picked for them.
#13390 hide the problem, but the real reason is unknown (client want to send disconnection to the server side in some use cases).