World of Warcraft: Forever went live in every region at the same moment: 3:00 p.m. PST on November 4, which is 23:00 UTC and 7:00 a.m. on November 5 in Beijing. Twenty-two years of separate realms ended, the login queues that everyone had braced for mostly did not arrive, and the argument about the game moved within a few hours from "will the servers hold" to "why is Stormwind empty" and "why can't I roll Horde on PvP".

That is a strange pair of problems for a launch, and it is the pair worth understanding, because both come from the same design decision and neither will be fixed by waiting out a queue.

The launch: short queues, and one specific glitch at the gate

The first-hand accounts agree on the shape of it. Eurogamer reports from its own session that, for European players who stayed up from about 11 p.m. to 3:50 a.m. UK time, the login queues were "short and constantly moving", with no random disconnects and at most a lost spell cast or two. Space4Games, publishing its own launch-night screenshots, was placed at position 783 with an estimated three-minute wait.

The one reproducible snag was at the selection screen: players who connected the instant the servers came up found the ruleset boxes unclickable. Backing out and rejoining the queue cleared it, though for some it took several attempts, and the whole thing had settled within roughly half an hour.

Blizzard's own read on the night, from executive producer Holly Longdale on X, as quoted in full by Eurogamer: "At the risk of jinxing things, so far so goodish which is crazy by itself. The team prepared a lot since the wildness of Beta. And this launch was crazier than the insanity we imagined but thankfully the team built plans and contingencies. They are incredible in my opinion."

On attention rather than population, Eurogamer also notes Forever climbing to the top of Twitch's most-viewed games during the first day, with streamer Ahmpy at roughly 18,300 live viewers. Blizzard has published no player or subscription numbers, and it has not done so since around 2015; treat any figure you see circulating as an estimate by whoever posted it.

Blizzard's own bug list, published the next morning

At 15:42 UTC on November 5 — 07:42 Pacific, 23:42 Beijing — Blizzard opened a Known Issues thread, prefaced with a framing worth reading literally: these are issues the team has judged "notable, impactful, and already tracked with plans to fix in the future", and the list is explicitly "not a comprehensive list".

What is on it:

Two things follow from that table. First, the PvP vendors are gone for now: the post says only "temporarily unavailable", gives no date, and that means anyone planning to spend honour in the opening days has nowhere to spend it. Second, and more useful for reading Blizzard's posture: the faction lock, the empty capitals and the missing boats are not on this list, even though all three were acknowledged separately. Absence from this thread means "not on this list", not "not happening".

The one hotfix with a named cause: Invite-a-Friend

The clearest fix of the first day landed before most of Europe woke up. At 02:43 UTC on November 5, Kaivax confirmed a live hotfix for players who entered through an Invite-a-Friend code: they had been "unexpectedly restricted from using certain chat channels, leveling past 10, participating in guilds, forming parties, or trading items with other players." The advised remedy is to log out and back in.

That is a specific failure worth naming plainly. The whole point of the invite programme is to put a returning friend into a group with you for a week; the bug removed grouping, guilds, trading and part of chat from exactly those players. Blizzard's post does not say how many accounts were affected, and some players on the forums reported that a single relog did not immediately clear it.

Layers: Blizzard admits it split the world too finely

The complaint that dominated the first twelve hours was the opposite of a launch-day crowd. Players reached capital cities and found almost nobody: one thread opened with a player counting "maybe 8 people AT BEST" in Ironforge while trade chat showed a channel population in the forties.

Blizzard's senior game designer Josh "Aggrend" Greenfield answered it on the forums at 06:35 UTC on November 5 (22:35 Pacific on November 4), in terms that concede the tuning rather than the design: "we are aware of some issues with certain areas not feeling as populated as they should. We will be tweaking some numbers tomorrow to help things feel a bit more lively."

"Tomorrow" there means November 5 Pacific time, which for readers on UTC+8 is the small hours of November 6. No numbers, thresholds or target populations were given, and we found no follow-up post confirming the tweak had shipped before we published this.

Worth keeping separate in your head: Forever's layering has two prompts that push in opposite directions, and coverage has blurred them.

• The crowded-zone prompt. When an area is saturated, the UI offers a refresh — move to another instance now, or wait about five minutes. This is the load-shedding mechanism Blizzard described in its pre-launch technical briefings, and we covered it in our guide to the realmless architecture.
• The group prompt. When you join a party and your friend is on a different layer, the game is supposed to offer you a way across. At 15:51 UTC on November 5, answering a report that grouped players could not see each other, Kaivax described the intended flow step by step: a blue message in the lower right after accepting the invite, clickable, producing a pop-up with a "Refresh Now" button, which should place you with your party.

Players in that same thread reported that no pop-up appeared for them, and that what worked was logging out and back in, or walking to the next zone together and back. None of that is officially confirmed as a fix; it is what players report working.

Boats and zeppelins: portals where the docks are

The transport failure was real, and Aggrend described its cause at 06:39 UTC on November 5: "We are aware of some issues with transports such as boats and zeppelins becoming lost in the maelstrom for extended periods of time." The temporary remedy was to spawn portals near most transport docks and inside the zeppelin towers, with a proper fix promised "in the morning" and the portals to be removed once that fix was verified.

Two caveats. "In the morning" is Pacific time, so UTC+8 readers should read it as November 5 evening into November 6. And we have not seen an official confirmation that the fix shipped or that the portals were removed — the Known Issues thread does not mention transports at all, and players were still discussing the portals hours later, some asking Blizzard to keep them permanently as a convenience.

The faction lock: the one problem you cannot queue past

Five minutes after the servers came up, at 23:18 UTC on November 4, the loudest new thread on the Forever forums was not about queues. It was about this message: "This faction is currently unavailable on this ruleset due to population imbalance." By our check it had 217 posts and 12,786 views, with a second thread passing 181 posts by mid-morning and a third — "Faction Imbalance is unfixable once it starts" — at the same count by 11:45 UTC.

Two different strings are in circulation, and players kept conflating them: the faction-unavailable message above, and "Creation of that type of character is currently throttled", which appears to be a broader creation throttle and which some players saw on non-PvP rulesets too. Neither ships with a countdown, and Blizzard has published no threshold, no lock duration and no estimate of when a faction reopens.

The important context is that this is not a launch-day bug. Blizzard announced the mechanism before launch — faction-balance controls on the PvP ruleset, modelled on Season of Discovery, where new character creation can be limited for the majority faction — as we reported when the RP-PvP ruleset was confirmed. Threads about the same lock exist from October 17, October 27 (during name reservation) and November 1. What changed on November 4 is scale, and the fact that the realmless design removes the old escape hatch: on a normal realm launch, an over-full faction meant picking a different server. Here there is nothing to pick. Waiting for the other faction to grow is the entire mechanism, which is precisely what makes it feel like a wall.

The counter-argument is also live on the forums, in a smaller thread titled "Please do not back down from faction locks and balancing Blizzard". A 50/50 split is the design goal, and the alternative — the imbalance that turned some Classic realms into a monoculture — is what the lock exists to prevent. Both positions are player opinion; neither is Blizzard policy.

Characters on the wrong ruleset: reports, no confirmation

A separate cluster of reports has no official answer at all. Players say characters created during name reservation on one ruleset — PvP, or Roleplay — appeared on Roleplay-PvP instead, and in some cases the original characters were gone from the ruleset they were made on. One thread opened at 09:17 UTC on November 5 describes three reserved characters on Horde PvP being moved to RP-PvP after the overnight maintenance, and the poster says they have screenshots. Another, filed as a bug at 02:29 UTC, describes making three characters on PvP that somehow existed on RP-PvP as well.

None of this is confirmed by Blizzard, and we have not reproduced it. One documented behaviour is adjacent and should not be confused with it: Oceanic players connecting to Australian data centres were told before launch that they must create characters on Roleplay or Roleplay-PvP or their ruleset would not appear — a rule, not a bug. That does not explain reports from players who say they never selected RP-PvP. If you are affected, the practical warning is to check which ruleset a character actually sits on before you level it, because deletion is the only fix players have found, and re-creating can run straight into the faction lock.

What we are watching next

Three things, all with timestamps we can check rather than promises:

1. The layer tweak. Announced for November 5 Pacific — November 6 in the small hours for UTC+8. Population in capitals is the observable, and no target has been published.
2. The transport fix and the portal removal. Promised for the morning of November 5 Pacific. Unconfirmed at the time of writing.
3. Whether the faction lock ever reaches the official list. It is the largest player complaint of the launch and the only one with no stated resolution path. Its absence from the November 5 Known Issues thread is the fact to track.

We have seen no announced change to December 9, when the first raid tier is due to open.

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