The Issues:
For the first issue, there's not much Valve can do since they can't tell who disconnects on purpose and who is having connection issues.
However - The second issue I described can definitely be addressed. If the match actually starts and both teams have all players at 0:00 on the clock the red message (and associated ban of affected user) should never pop up. All players are present and the game recognizes this as such since it started the match (whereas if a player isn't present the game is cancelled before match start).
More Context:
I strongly suspect that this problem is related to the red sea cable cut back in September. Reason being that it seems to affect users from particular regions more than others (I'm in the ME) and my setting of a VPN to Singapore (which doesn't use the affected cables from my region) addresses the problem at the cost of higher ping. Also I personally never had this particular issue prior to September.
I've also noticed anecdotally that ME and Indian players are more affected than others (both of whom were affected by the cables). Perhaps something to do with the alternative routing ISPs put in place after the incident?
Really hope you guys can take a look at this 2nd issue as it REALLY sucks for your users that are unfairly banned and sometimes sent to low priority queue (OMG i can't believe how bad it is, never experienced anything like it in my life. I'd literally rather have a longer ban than see it again for even one game)
I know this is affecting more users than just me so i hope the impact of addressing this is obvious to the team.
Thanks for making an excellent game btw - I wouldn't have taken the time to write this if I didn't LOVE deadlock.
- Unresolvable - Some users are unable to join matches (get immediately booted out to the scoreboard screen) and are unable to rejoin (get booted out to the hideout). This often leads to bans. (FYI a consistent workaround is to start a VPN -> restart steam -> open deadlock again -> reconnect to match - this works 80ish percent of the time I'd guess)
- Resolvable - In the event an affected user does manage to rejoin the game, the match usually starts as normal. However, a guesstimated 20% of the time where the user reconnects, the match starts with the red warning about "leaving counting as a loss but not being penalized". I believe this is a distinct bug since if a user leaves a match in the early game we usually get the green message saying the match is not counted at all. The red message should not pop up in the scenario i described ever.
So a user who reconnects successfully allowing the match to start and playout as normal is still penalized. In my experience this is more likely to happen the more time that passes before successful reconnection.
For the first issue, there's not much Valve can do since they can't tell who disconnects on purpose and who is having connection issues.
However - The second issue I described can definitely be addressed. If the match actually starts and both teams have all players at 0:00 on the clock the red message (and associated ban of affected user) should never pop up. All players are present and the game recognizes this as such since it started the match (whereas if a player isn't present the game is cancelled before match start).
More Context:
I strongly suspect that this problem is related to the red sea cable cut back in September. Reason being that it seems to affect users from particular regions more than others (I'm in the ME) and my setting of a VPN to Singapore (which doesn't use the affected cables from my region) addresses the problem at the cost of higher ping. Also I personally never had this particular issue prior to September.
I've also noticed anecdotally that ME and Indian players are more affected than others (both of whom were affected by the cables). Perhaps something to do with the alternative routing ISPs put in place after the incident?
Really hope you guys can take a look at this 2nd issue as it REALLY sucks for your users that are unfairly banned and sometimes sent to low priority queue (OMG i can't believe how bad it is, never experienced anything like it in my life. I'd literally rather have a longer ban than see it again for even one game)
I know this is affecting more users than just me so i hope the impact of addressing this is obvious to the team.
Thanks for making an excellent game btw - I wouldn't have taken the time to write this if I didn't LOVE deadlock.
