The WoW: Forever beta is over. Community manager Kaivax closed it out on the official forums on October 23 after five weeks of testing, two days later than originally planned because Blizzard wanted one final stress test on October 21. What is left is a short, now fully dated countdown: a few days of focused fixes, Early Name Reservation on October 27, and launch on November 4.

The final 24 hours were a deliberate party

Blizzard closed on a high note. A day before shutdown, Kaivax announced 24 hours of "shenanigans and upheaval" across seven zones — Zephras Isle, Dun Morogh, Elwynn Forest, Teldrassil, Durotar, Tirisfal Glades and Mulgore — with an explicit warning that the event "almost certainly includes items and experiences that will not be a part of WoW Forever after it launches."

What players actually found, as reported by Wowhead and re-checked by ForeverDB, went further than the announcement:

• A new goblin vendor, Gabbi Goodwhistle — Specialty Beta Goods & Training, outside the capitals, selling fireworks, a group movement-speed scroll and a 200% experience elixir.
• World bosses roaming the starting zones: Azuregos, a "Super" Hogger, Voracious, Thunderaan and Lord Kazzak — dropping familiar legendaries including Sulfuras and Thunderfury.
• Full Classic Tier 1 sets and Molten Core weapons dropping from ordinary mobs in every starting zone.
• The Wrath-era Scourge plague spreading across Azeroth one more time, via the 2008 contaminated-crate event.

None of that carries meaning beyond the sendoff: Blizzard's own warning is that the celebration content is one-time-only, and nothing from the beta — characters, gold or names — transfers to live.

The layering statement: what is being fixed, and what is not

The more consequential news of the same window is a statement Blizzard gave GameSpot, attributed to associate production director Clay Stone, addressing the beta's most persistent complaint. Forever's layering assigns players to world copies based on criteria like familiar players, language and PvP balance, but testers found the layer switches far more aggressive than in any previous WoW: leaving groups, crossing zone borders, riding transports and stepping out of a capital city could all quietly shuffle you into a different world.

Stone confirmed two targeted fixes before launch:

• Transports: players "don't get decoupled from other players they see on transports (i.e. boats and zeppelins) after loading screens."
• Capital city exits: large groups of players will no longer be re-layered "when they enter or leave capital cities."

Both fixes aim at the exact clips that defined beta criticism — most famously a Reddit video of a boatload of Alliance players crossing to the Eastern Kingdoms, losing their layer on arrival, and being massacred by the Horde ship that replaced their companions.

What the statement does not address is layer switching at zone boundaries, the issue the world-PvP community cares about most: large open-world battles currently evaporate when a raid crosses an invisible border, and the border itself has already been used as an escape hatch — losing sides running out of a fight to phase into safety, or attackers killing and fleeing into another layer. Stone only commits to "consistently be making more improvements, as necessary, through launch and beyond," and concedes that "there will always be some amount of layering" on high-capacity infrastructure.

The countdown is now fully dated

Kaivax's closing post and Blizzard's name reservation article pin down every remaining date:

Reservation details worth planning around: you can create up to three characters total across all rulesets during the window, which closes November 3 — two names on the PvP ruleset leaves you only one for Normal or Roleplaying. Names are first-come, first-served and not guaranteed. The client is installed through the Battle.net desktop app by selecting World of Warcraft: Forever as the game version.

The Roleplay-PvP ruleset is slated to join Normal, PvP and Roleplaying at launch, and Blizzard has said it is working to make it selectable on reservation day — still phrased as a goal, not a guarantee.

Update, October 29: the goal held. Reservation opened on October 27 and Blizzard's first bug post — telling Oceanic players to create Roleplay and Roleplay-PvP characters before Normal or PvP ones — only makes sense if the ruleset is live and selectable. Two bugs were confirmed on day one: the Oceanic ruleset ordering bug above, and a restricted-name filter that was rejecting legitimate names, including any containing "con". Both are covered in our day-one report.

What the quiet two weeks are actually for

The End of Beta episode of the official podcast filled in the practical reason for the gap: lead software engineer Ana Resendez said the beta ran on different hardware than the live game, so the team is now standing up the real servers, the realmless configuration and the rulesets to be ready for reservation day. The same episode explained that Forever has no language realms — a language preference setting feeds the layering system, and the only hard divisions are regions and rulesets. Cross-region play is not happening at launch, though Resendez would not rule it out permanently.

::note Verified on October 25, 2026 against Kaivax's October 23 closing post, Blizzard's official name reservation article, GameSpot's layering report (with Clay Stone's full statement) and ForeverDB's October 24 sendoff write-up, which separates Blizzard's own announcement from Wowhead's event reporting. The celebration details (vendor items, boss drops, Tier 1 loot, the Scourge plague) are Wowhead's report, not Blizzard's; the final sendoff post was not independently accessible. The December 9 raid date is from Blizzard's earlier roadmap reporting. All times above are regional as stated; layering behavior at launch is a stated intention, not a verified result. ::