The first week of the World of Warcraft: Forever beta produced the story everyone expected: queues, disconnects, and five-figure login waits on opening night. The second week is producing the story that matters more for November 4 — a beta that is now being treated as an unstable environment on purpose.

On September 22, Blizzard's community manager Kaivax surfaced in the loudest of several threads about a bug that locks players out of a character with the message "Character with that name already exists." His request was unusually specific: the name of the beta character you are locked out of, and the exact time you were last successfully playing it before the disconnect. That is the shape of a reproduction attempt, not a support reply.

Twenty minutes earlier, in the same thread, Kaivax had already written what most betas would never say out loud: "About the same time you posted this, a Senior Game Producer told me that he wants to restart Beta realms today."

Restarting the realms is the feature

A mid-test realm restart is easy to read as a bad sign. In this case it is closer to the opposite.

Forever is not a normal launch: it replaces named servers with a single ruleset-based population, which means realm-level state — names, characters, and whatever is breaking the name-uniqueness check — is exactly the layer Blizzard cannot validate on a small scale. When the fix requires restarting the test environment rather than patching it, the practical consequence for testers is simple: week-two characters may vanish without warning, and that is not a bug report.

Kaivax framed it that way himself, adding that the team recognises "that Beta testing is very different than playing a live game." Nothing from the beta carries to launch regardless — progress, items, professions and gold are all wiped when testing closes on October 21, and the November 4 launch starts from an empty economy.

Mac players got an answer

Our Mac crash guide covered the workaround sequence the community converged on after Apple Silicon players hit whole-machine freezes when entering the world. On September 22, Blizzard responded to a separate, meticulously documented report listing eight distinct graphics bugs, each isolated to a single setting with its own reproduction steps — and the answer was not a canned one:

"I just want to thank you and others who have provided us with such incredibly detailed and useful reporting. We have multiple different analyses (and potential fixes) for Mac issues underway, and posts like yours are extremely helpful."

That is the most substantive Mac acknowledgement the beta has produced. It does not mean a fix has shipped, and it certainly does not mean the freeze-on-login problem is solved. It does mean Mac reports are being read by people with a fix in progress, which changes the calculus for anyone deciding whether it is worth writing one up.

The known-issues list, as it stands

Blizzard has not published dedicated beta forums; the WoW Forever forum is the single channel, and the September 18 known-issues post is still the reference. The current entries, with sources:

Two of those are worth reading as design signals rather than defects. The Bear Form armour multiplication is the same class of bug that has defined Druid tanking in every Classic re-release, and the spell queue window behaviour on Heroic Strike and Raptor Strike is a mechanic players have learned to exploit or fear depending on the era. Both are the kind of thing a beta exists to catch.

What is still missing

Three things remain unresolved, and each one has a deadline attached:

• The Server Slam date. Blizzard has confirmed an open window of several hours during which anyone can play, but has not announced when. Published guides disagree on the access requirement — some say any Battle.net account, others say an active subscription or game time — and Blizzard's own wording leaves it open. Treat the date as unknown and the requirement as unconfirmed until it appears on Battle.net.
• Phase two, and the level 30 cap. The cap rises from 20 to 30 later in the test, described as "after two weeks," which points at roughly October 8. That phase adds the Excavation Site: Wetlands dungeon and is the natural moment for a tuning pass on everything testers have reported.
• Whether anything announced for the beta arrives at all. Blizzard has said more zones, dungeons and the new battleground will open up as testing continues. None of those windows are dated either.

If you are testing this week

• Report with timestamps, not feelings. The name-lockout thread is the clearest example in this beta of a developer asking for a specific data point. Character name plus the last successful login time is a reproduction; "the game is broken" is not.
• Assume the environment will be reset. Do not build a character you are attached to, and do not treat a wiped profession or bank as lost progress — the beta ends in a wipe by design.
• If you are on a Mac, the report is worth writing anyway. The crash path is still unsolved, but the community workaround exists and Blizzard has confirmed it is actively analysing the client's rendering pipeline. A report with your chip, your settings and your reproduction steps is the input that work needs.
• Plan for the level 30 phase, not the current one. A month of testing with a cap that moves means the most useful feedback window is the one after the cap rises — and it is also when the content most relevant to launch becomes reachable.

The honest read on week two is that the beta has settled into the least glamorous and most useful part of its schedule. Opening night proved the login servers can be overwhelmed; the rest of this test is about proving that the systems underneath them can be fixed before a much larger population arrives.