Blocked from starting a game? Now you can see which one
You can only be in one game at a time, and until now being told so was a dead end: no room named, no way back to it, no way out of it. The refusal now comes with the game it is talking about and a button for each way forward.
In plain words
Opening a second game has never been allowed while your first one is unfinished — that rule is old and it is not what changed. What changed is what happened when you met it. You pressed Create, or Join, and got one flat sentence: you are already in another game, leave it first. It did not say which game. It did not offer to take you there. It did not offer to leave it. If you had closed that tab, or forgotten the room entirely, the sentence was true and useless at the same time.
Now the refusal names the room you are already sitting in, and carries the two buttons that actually resolve it: open it, or leave it. The notice appears in the three places you can run into the rule — the banner at the top of the lobby, the create-a-game form, and the room list — and all three are drawn from one description, so they cannot start disagreeing with each other later.
For the technically curious
The interesting part is that nothing here was broken. The rule was correct, and the banner meant to warn you about it was correct. They were just two separate statements of the same rule, and they had drifted apart: the database guard refuses you when you hold a seat in a game that is waiting OR active, while the banner only ever asked about games that were active. A player sitting in their own room that had not started yet was therefore refused by one rule and told nothing at all by the other. Neither half was wrong on its own, which is exactly why nothing caught it for so long. The rule is now written once, in one place, and both halves read it from there.
| Week | Error rows logged site-wide |
|---|---|
| 10–17 Aug (before) | 576 |
| 17–24 Aug (fix lands mid-week) | 221 |
| 24–31 Aug | 21 |
| Most recent | 1 |
It was also much louder than it looked. Quick match walked every candidate room and swallowed each failure separately, so a single click could write up to thirteen refusals into the log a few seconds apart. It asks once now. The log deflated by removing duplicates, not by hiding anything.
One number deliberately did not improve: the refusal itself. It happens more often now than it did before, because the game has more players in it — around 1,700 times since the change, to 295 different people. That is the rule doing its job. What changed is that it is recorded as an ordinary, expected outcome rather than as a site error, and that the person it happens to is handed a way forward instead of a full stop.