Skip to main content
All patches

10 Sep 2026 · v1.133.0 to v1.134.0

Fixes, 10 Sep 2026

3 New1 Improved4 Fixed

3 New

  1. He offers the characters he already knows about instead of asking you to type

    Apply to a guild, sign up to an open raid, verify yourself, and he used to hand you an empty box while your characters sat in his own records. He lists them now, filtered to the game and region that raid or guild is actually on, with typing still there for anything he has not met. Connecting Battle.net is offered at the same moment, which is the moment it is worth anything, and he says when he last read your account rather than pretending the list is live.

  2. A community server posts raids anyone can join, without being asked twice

    Community mode turned off the roster and the verifying, then left every raid members-only, which on a server with no members means nobody. Raids there are open by default now, and signups stop waiting on an approval nobody was set up to give. Both are defaults, so a community can still run something for its regulars only.

  3. A community goes by its Discord name, and can be found

    Every public name came off the in-game guild, so a server without one was Guild a4f2 and could not appear anywhere. A community is known by its Discord server name now, kept current when it is renamed, and can list itself beside the guilds with what it actually runs counted rather than claimed. Nothing appears there without an open door and something opened to outsiders in the last three months.

1 Improved

  1. Connecting Battle.net no longer loses your place

    It used to take you off to a page of its own, and people never found their way back to the application they were halfway through. A small window opens instead, you sign in with Blizzard, it closes, and you are still on the same page with the same half-typed answers and your characters now listed. If the window is blocked you come straight back to where you were instead. He says up front what he asks Blizzard for, which is your character list and nothing else, and the page that says so is now a way onward rather than a dead end.

4 Fixed

  1. My characters treated every character as if it were one game

    Refresh all told one account it had refreshed fourteen characters and quietly failed on twenty-eight, because everything on that page assumed a single game version and read Retail characters as Mists ones. A Demon Hunter was offered a role list with no tank in it, the per-character refresh reported success on a character it had failed to read, and Add an alt offered you characters you already owned. All of it was one wrong assumption.

  2. A raid he saved but never actually posted

    Make a raid on the web, get a cheerful yes, go to the channel, find nothing. Discord had refused the post and he had no idea why, so neither did you. One guild built the same Karazhan three times before one stuck. He checks he can see the channel before he saves anything now, and when Discord still says no he tells you which permission is missing instead of nodding.

  3. Him insisting your realm does not exist

    Save your realm in settings and he could file it as "moon guard" while Blizzard calls it "moon-guard", then announce that your realm is not on Blizzard's list at all and that your game version must be wrong. It was not. The same typo quietly broke verifying, because every armory lookup went to a realm nobody has. He writes realm names down properly now, and reads the old ones properly too.

  4. A signup page offering a character from the wrong game

    Signing up to an open raid on the web listed every character he had on you, from every server and every version of the game, so a Mists character turned up for a Burning Crusade night. It reads the raid it is for now.