Closed Jacob-Griffin closed 1 month ago
So it kinda was. The problem was that after submitting a round, the round data synced before we set "The round we just finished was the one in round data", so it was saying the last one in finished the next round. Came with the content safety changes.
Just changed it so it stashes the current round before sending the result, then setting the stashed round after a successful submit. Seems to fix it
For some reason, the last person to get auto submitted doesn't properly check when the round moves on. Since they do see the new round number and the new timer, this must be a problem with watching the "waiting" variable