Skip to content

[Bug] Mesh-check fail can cause points change before next game's end #3

Description

@Piddox

Describe the bug
The following can happen:

  • Mesh-check fail happens, player does not enter the game and continues queuing
  • During the queuing or once the next game has already started, the game is logged on Strata as a loss
  • The next game ends, but if the result of this game is not yet on Strata, the tool will pick up the points change of the mesh-check fail game rather than the actual game played
  • This can continue until on game end the latest game is registered on Strata, and the tool is fully caught up

Possible solution
Apart from GO fixing the mesh check fail, possible solution:
At game start, preemptively fire one or two API calls to make sure that if there was a points change during the queuing phase, it is caught before the next game end. But this is tricky since the next game could only take a few seconds, if for example the opponent insta-quits.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions