One hotfix, one subject: the battleground queue works again. Since v0.36.0, when the queue found a match the cue and the chat line arrived just fine — but the Accept / Decline prompt never appeared for some players. Thirty seconds later, silence counted as a decline, and since it takes ten people to seat a 5v5, no match could ever start. The dungeon finder’s “group found” prompt carried the same flaw. Nothing else changes: no combat values, no items, no data.
Released August 13, 2026Since v0.37.065 files touched
💡 Click a card for details.
01The battleground queue works again
This is the whole point of the hotfix. If you stopped queuing a few days ago because “nothing ever pops”, it wasn’t you: it was a bug, and it is fixed.
What was happening Fixed
The queue really did find matches: the cue played, the chat line arrived. But the Accept / Decline prompt never opened — and 30 seconds later your silence was counted as a decline.
See details
Why no match could start The snowball
A Thornhollow Fields battleground is 5 versus 5: it takes ten players accepting to seat a match.
So it only took a few players not seeing the prompt for the whole offer to fail and everyone to be dropped back into the queue.
A player who “declines” this way is held out of the queue for 30 seconds — deliberately short, precisely so it does not punish the eight others who did answer.
The result: the queue churned endlessly without ever seating anything.
What does not change Unchanged
You still get 30 seconds to answer an offer.
The cue still fires immediately, as before — it is the prompt that waits until it has something truthful to show.
No queue, lockout or team-composition rule is modified.
02The dungeon finder too
The same flaw lived in the dungeon finder’s “group found” prompt — and there it was even more likely to fire.
A wider window to hit Fixed
The dungeon finder receives its state twice a second, while the interface refreshes four times a second.
So the information could trail the announcement by up to half a second — a bigger gap than on the battleground side, and therefore a bigger chance of missing the prompt.
It gets exactly the same fix, with the same waiting margin.
Nothing else on the dungeon side Unchanged
No boss, no rift and no loot is touched by this hotfix.
The changes to Bonelord Xarreth and Grix the Tunnelking came in v0.37.0 and stay as they are.
An accessibility detail Worth knowing
The prompt is announced to screen readers without ever stealing focus — otherwise it would cut across whatever you were doing.
Previously, when it opened too early, that announcement fired on an empty box. It now waits until it has real text to announce.
03What was actually going on
For the curious: the outage was not in the queue itself, but in the order two server messages arrived.
A race between two messages Explainer
The “your queue found a match” announcement and the contents of the offer travel in two different messages. The first always arrives ahead of the second.
See details
The guard rail New
The prompt now waits instead of concluding the offer is already resolved: it opens at the first opportunity where it can genuinely read the offer.
That wait is bounded to about 5 seconds: an offer that dies before it can be read cannot leave an invisible prompt stuck forever.
New tests now pin the arrival order of the two messages on the server: if anyone changes it one day, it will be a conscious decision rather than an accident.
And that is all Scope
No markup, style or balance changes.
No data migration: nothing to redo on your character.
All 21 locales are unchanged — the prompt’s strings were already translated, they simply were not being shown.