-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Matchmaker game timeout sometimes cancels the wrong game #866
Comments
So people are able to requeue even though the server still has them in a game? Should the removal of people from a game only happen once the cancellation and failure to start is officially recognized? |
Well what happens here is that one of the players never connects to the first game and after a while the other 3 leave the game and requeue. They're not in the game anymore and the server knows that, however when the game finally does time out it just sends the cancelled message to everyone who was in the match (everyone who received a corresponding I think I'm going to start by fixing the issue that I know exists which is that the match can take way too long to time out, and I wanted to add the game id to the message anyways... After that I'll think about if it's really worth trying to make the player state tracking more complicated, because I think what you're suggesting is a lot easier said than done given how it's implemented right now. |
Understood. As that tracking would depend on how it is currently done. I would also wonder if it is possible to just send a cancel message once any of the game connections are dopped during the set up phase but not sure if that requires the same tracking |
Yea that would be easier to do but it would prevent any reconnection attempts. Although, I don’t think we have a system in place for reconnecting in that way anyways so it would probably be fine to do that. |
Just as a second reference apparently this can also happen with one game without relaunchign as swkoll had a game that started the all players got match cancelled |
Is there a reason that this is still open? |
Wait what? I'm not sure I understand what you're saying. |
The cancel message happened after the game had already launched and been playing for a few minutes. |
But no one had requeued or anything |
Game id? |
It never got a game id that I am aware of as it never showed in replay vault |
It will still have an id, although if it didn’t properly launch then it won’t have been written to the database |
Yes so I meant it doesn't have an id that I can recover |
1 similar comment
Yes so I meant it doesn't have an id that I can recover |
Here, the first game
15904960
failed to start at around 17:59:29 however, no match cancelled message was sent. After about 10 minutes the handler in LadderService finally saw that the game didn't launch and sent the match cancelled message at 18:10:46 which ended up cancelling a different game that had launched in the mean time.I think we should first of all include a game id in the match cancelled message so that the client can check if the message that's arriving is actually meant for the current game. And second of all figure out why it took 10 minutes for the game to time out when the maximum timeout should only have been
2.66
minutes.The text was updated successfully, but these errors were encountered: