• Playing Battle Royale Countries on Macbook MacOS, Chrome Version 141.0.7390.123 (Official Build) (arm64)
  • Advance through until it's 1v1 in round 7
  • I recognize the country
  • Quickly click on (in this case) Bulgaria
  • Click on the "Guess" button to lodge my guess (approx. ~1:19 on countdown)
  • "Guess" button becomes muted indicating click event was registered
  • The clock runs down past the 1:15 early lock-in threshold and continues until 1:11 or 1:10 without notification of results
  • I receive a failure/game-over screen notifying me the correct answer was (as I had correctly guessed) Bulgaria
Obviously there was some sort of hiccup / glitch after I guessed before the lock-in threshold. However, a 9-second network glitch would be pretty unusual on my end, as I have a gigabit fiber connection. This is not the first time I've experienced apparent glitches specifically in Battle Royale. It seems like it could be related to previously noted misbehaviors:
I assume the timestamp of the click/submit event is recorded locally, and sent as part of the payload to the server. So if I click "Guess" at 1:19 and the network abruptly hiccups but eventually the payload arrives, you should be able to sort out how to score that correctly? I get that battle royale is maybe the redheaded stepchild, but the game mode definitely feels more fragile than duels. Is it that there's just so much data/timing juggling on the backend?