BriefingsNov 17, 2026 · RealmList Editorial

ForeverWoW Pushed Its Launch From November 22 to December 21, and Its Own Fix Log Shows Why

Four days after announcing a November 22 launch, the community project emulating WoW: Forever postponed it to December 21, 2026, with January 20, 2027 as a final fallback. Nothing shuts down and the beta continues without a wipe. The reason it gave — "more core problems than we expected" — is spelled out in its own changelog, where warrior abilities stop scaling with attack power, a druid ability that exists in no version of Forever is still being pruned from trainers, and about a hundred quests had non-functional objectives.

AI illustration made for RealmList. It evokes a server project under construction, not an in-game screenshot.

ForeverWoW's November 22 launch is off. In a news post dated November 15, 2026, the project pushed its opening to December 21, 2026, with January 20, 2027 as a final fallback if the first date is missed — four days after it had announced the 22nd as a fixed date.

The post is unusually direct about why. Players who joined after the announcement filed far more bug reports than the team expected, and those reports showed the server core is further from finished than the inside view suggested: "they also showed us something we had underestimated from the inside: there are more core problems than we expected. We don't want to open the server in this state. We clearly rushed the November 22 date, and we apologize to everyone who was already getting ready for launch."

What the new timeline actually changes

  • Nothing shuts down on November 22. The open beta that has run since October 1 continues, and there is no wipe on the original launch date — the wipe now happens immediately before the real launch instead.
  • Accounts survive, rewards keep growing. Accounts stay as they are, the beta reward tiers still stand, and points continue to accrue while the test server is up. Tier status is visible in the account page on the website.
  • December 21 is a target, January 20 is the floor. The project says it will confirm one to two weeks before December 21 whether it is on track, and calls January 20 "final" — a promise about its own behavior, not an external guarantee.
  • Bug reports are still the lever. The team asks players to keep filing through the in-game "Report a Bug" window and the forum, framing report volume as what determines how soon the server opens.

For anyone who had arranged time off around the 22nd, the practical reading is simple: there is no launch to attend, but there is still a beta to test, and everything you do in it will be deleted whenever the real launch happens.

The "core problems" are visible in the changelog

The most useful evidence is not the apology but the changelog published the next day, covering November 12–16. Read as a list of what had to be fixed, it explains what a "core problem" means for a project emulating a live Blizzard client rather than a frozen 2006 one:

  • Basic combat math was wrong. Warrior Bloodthirst and Revenge "scale with attack power again"; Sweeping Strikes and Retaliation "strike again instead of just spending charges"; Bloodrage again puts the warrior in combat; rogue Preparation again resets cooldowns; and "defense from items is no longer counted twice." These are not polish items — they are the arithmetic underneath every fight.
  • Talent and ability plumbing was incomplete. The Poised talent "works" and can now be learned from rogue and druid trainers; Winter's Chill now triggers only from Frostbolt; Arcane Missiles fires faster during Missile Barrage; rogue trainers now teach Shank; Alliance shaman trainers can reset talents again.
  • Spell lists did not match the game being emulated. "Tiger's Fury has been removed: this ability does not exist in WoW Forever." Wherever that ability came from — a Classic-era spell table, or an earlier build of the server — the line makes the underlying problem plain: what players could train was not what Blizzard's client actually ships.
  • Quest chains did not chain. After a turn-in, "the next quest in the chain is offered right away by the same NPC"; "objectives of nearly a hundred quests with special completion conditions now work"; enemies now attack the NPCs you escort. For a game whose pitch is the 1–60 journey, broken chains are close to a structural defect.
  • Group and client basics were missing. Party and raid world markers now work; a macro with several /use commands now uses every item; creatures, dialogue lines and item names were fixed "in all client languages"; /sit and /sleep no longer break after opening the map.
  • The server itself was unstable. Crashes on a dropped connection at login were fixed, and "the server now runs faster when many players gather in one place" — the crowd problem a launch would have magnified.

Two entries matter beyond bug-fixing. Support was added for a new client version, with the launcher updating the game automatically — Blizzard shipped a patch during the beta week and the project had to follow it, which is exactly the maintenance burden we flagged when surveying the Forever emulation scene in October. And a new .xp command (x0, x0.1, x0.25, x0.5, x0.75 or x1) lets players throttle their own experience gain, with innkeepers offering the same choice — a toggle that will change how anyone plans a beta run or a deliberately low-level character.

What this says about the category

ForeverWoW is not a 3.3.5a realm running a core that has been stable for fifteen years. It runs ForeverCore, the project's own core, against a client Blizzard is actively patching and selling, and the changelog above is what that costs. The comparison is not flattering to deadlines: a team that had been in open beta since October 1 discovered in the week after announcing a launch date that attack-power scaling, quest chaining and class trainers were still broken.

None of that makes the postponement a scandal. Delaying is the correct call when a launch would have shipped those bugs to a crowd. It does mean the honest way to read any community server's launch date — including this one — is as an intention, and our guide to checking population and launch claims applies with full force: the number on the homepage said 68 players online at our November 17 snapshot, down from the 84 we recorded on November 15, and neither figure is audited.

The legal picture has not changed either. This project emulates a client Blizzard released on November 4 and continues to sell, in the same year the company ended Turtle WoW and Stormforge. We are not aware of any action against ForeverWoW as of this verification, and we are still not listing it in the realms directory.

If you were going to play

  • The beta is still open, and accounts created now still carry into launch with their reward points. Characters do not.
  • Expect a wipe at some point before December 21, not on November 22.
  • Check the tier, not the calendar. Reward tiers are fixed when the test server closes for the launch, so the clock to earn Silver or Gold now runs to December, not to the 22nd.
  • Treat January 20 as the real deadline. A project that missed its first date by four days of self-review is unlikely to be held to a target by anything except its own statement.
Verified on November 17, 2026 (Asia/Shanghai). The postponement post (dated November 15, 2026, 04:26 site time) and the November 12–16 changelog (dated November 16, 2026, 10:02 site time) were read directly on foreverwow.biz; the site publishes timestamps without a time zone, so we quote them as shown rather than converting. The only independent corroboration is the Private Server Hub listing, updated November 15, 2026, which now records a planned launch of December 21, 2026 and states the November 22 date was postponed — everything else in this article, including the reason for the delay, the reward mechanics and every changelog entry, is the project describing itself, and none of it has been tested by us in-game. The 68-player figure is a homepage widget snapshot at verification time, not an audited count, and the earlier 84-player figure came from the same widget two days prior. Dates here are the project's own commitments and can move again. We are not aware of any Blizzard legal action against ForeverWoW as of the verification date; that is an absence of information, not a clearance.