Original editorial illustration by RealmList, generated for this article. This is artwork, not game footage or official promotional material.

Blizzard said the World of Warcraft: Forever beta would open minutes after the Forever segment of the September 17 developer Q&A ended. It did not. The doors opened roughly an hour later, after two blue posts asking for patience, and for most of the people who had planned their evening around it, the first hours of the beta were spent looking at a queue counter rather than at Azeroth.

That is the honest headline of day one: not a crash, not a rollback, but a launch that had to be walked back from a hard timestamp into a soft one, in front of an audience that had already been told the time.

What the evening actually looked like

The sequence, reconstructed from blue posts and live coverage:

Blizzard has not given a reason beyond "a couple of final issues," and the timestamped blue posts sit in the middle of a stream that ran long, so treat the delay as "closer to an hour than to minutes" rather than a fixed clock offset.

For some players the client did not appear in the Battle.net version dropdown at all until the launcher was shut down completely and restarted. Once it did appear, the queue became the story. Reported positions climbed from the low thousands into five digits within the first hour; Reddit threads reported 15,000 to 20,000-plus ahead of them and estimates near an hour. One widely shared account describes waiting roughly twenty minutes to move from position 6,000 to the front, being disconnected at the threshold, and being returned to around position 15,000.

A reader poll run by the German outlet PlayCentral, with 405 respondents during the evening, is the most concrete snapshot of how the night went for the general audience: 4 percent said they were in. 40 percent reported installation or launch problems, and 32 percent were in the queue.

Blizzard's own acknowledgement was brief and posted to X: that the team was working through final issues and expected the doors to open soon. A staff reply in the forums the following day was telling in its understatement — "We almost have the doors thrown open."

The known-issues list is the more useful document

The queue is a launch-night problem. The list Kaivax published alongside the beta going live is a preview of what is genuinely unfinished, and it is worth reading in full because it is the only artifact that tells you what Blizzard already knows is broken.

Systems and display

• Barber chairs throw a LUA error.
• The minimap can render partially off-screen.
• The character pane does not display level, class, or title.
• Character friends are disabled in the beta.
• Running /y (Legacy System) before level 25 throws LUA errors on tabs 1 and 3.
• Guild charters cannot be signed properly; Blizzard temporarily enabled submission without signatures.

Items and quests — mostly flagged as fixed in the next beta build

• Waylaid Crates fail on items whose maximum stack size is smaller than the required quantity.
• Apprentice Curiosities crates wrongly reject Greater Magic Essence and wrongly accept Lesser Magic Essence.
• Night Elf priest Starshards does not consume the Twilight Focus talent.
• Retribution paladin Vengeance can trigger from periodic critical hits.
• Create Firestone ranks 3 and 4 have incorrect tooltips.
• The Coldridge Valley map does not display.
• In "Escaping Ban'ethil," Sentinel Lynessa Duskblossom runs too fast and spams Strike.

Pets and combat maths

• Warlock pets do not show mana on the character pane, their master scaling is unstated, and stamina-to-health conversion is wrong.
• Hunter and warlock pets do not display the master's hit scaling, pet expertise is hidden, and movement speed values are incorrect.
• Spell glancing blow chance is wrong at every level, with incorrect damage reduction attached.
• Melee glancing is correct against same-level targets but applies the wrong damage-reduction penalty against higher-level targets.

The pet and glancing-blow entries are the ones to keep an eye on. They are not cosmetics — they sit underneath every damage number in the game, and the first phase of this beta is specifically about the level 1–20 experience where those numbers are small enough for an error to be visible.

Why the queue is a design consequence, not just a demand spike

Forever does not have realms. You choose a ruleset — Normal, PvP or Roleplay — and land on the same world as everyone else on that ruleset. Season of Discovery veterans will recognise the shape: when you remove realm sharding to protect the social fabric of the game, you also remove the option to spread load across dozens of smaller servers.

That trade-off was known and accepted, and the beta proved the demand side of it. The relevant question is not whether queues happened on day one — they did, and Blizzard's own staff pointed at sheer demand — but whether the same architecture holds on November 4, when the audience is orders of magnitude larger than a beta opt-in list and there is no "it's only a test" caveat. Whether the queue numbers were capacity, a login-service bottleneck, or both is not something the night answered; Blizzard has not said.

One practical note worth carrying forward: the busiest windows were weekday evening. If the pattern holds, the first beta weekend is where the load test actually gets interesting.

What is not in question

The beta window is unchanged — September 17 through October 21 — and the launch date is unchanged at November 4. Nothing from the beta carries over. The first phase remains capped at level 20, with a raise to level 30 planned later, which means Hall of Thanes (13–18) and Ruins of Lordaeron (15–20) plus the reworked 1–20 questing and profession content are the parts of Forever currently under the most scrutiny. Raids, Hardcore, and the mid-game are still untested by anyone outside Blizzard.