WoW ForeverWiki & Guides
English
☰
GuidesClassesRacesZonesQuestsSystemsDungeonsRaidsNews & UpdatesLanguageEnglishEspañolDeutschPortuguês (Brasil)

Beta Known Issues

WoW Forever Beta Known Issues: Bugs, Fixes & Current Status

Track WoW Forever beta known issues, Blizzard acknowledgements, announced fixes, quest bugs, class bugs, UI issues and what has actually been verified fixed.

By WoW Forever Wiki TeamSeptember 20, 20268 min readBeta live · Living issue tracker

WoW Forever beta has an official Known Issues list, and several entries already have fixes announced for a future beta build. This page tracks the difference between "reported," "Blizzard acknowledged," "fix announced," and "verified fixed" so that a future-patch note is not mistaken for a fix that is already live.

Current official issue categories

Blizzard's September 18 list includes problems affecting:

  • Barber Chairs and Lua errors;
  • the friends system in beta;
  • minimap positioning;
  • Waylaid Crates;
  • at least one quest escort;
  • class/racial interactions;
  • pet behavior;
  • other beta systems that can change with subsequent builds.

This page will be updated from official notes and reproducible beta testing.

Current client build and crash reports

Player crash reports now clearly identify WoW Forever Beta 1.60.1.69913 on multiple systems. Separate forum threads describe Mac full-system freezes or WindowServer crashes when entering the world, plus GPU/client hangs on build 69913 across other hardware and unsupported Linux/Wine setups.

These reports are not yet part of Blizzard's official September 18 Known Issues list, so we label them as player-reported crash clusters rather than official Known Issues. Community workarounds such as lowering overall graphics quality or setting Secondary Lighting to Fair have helped some Mac users, but they are not confirmed universal fixes.

The official September 18 post still describes the Waylaid Crate, Escaping Ban'ethil, and Starshards/Twilight Focus fixes as landing in the "next Beta build." Although newer client builds are now observable, Blizzard has not updated that post to mark those specific issues verified fixed. Until they are reproduced successfully after the relevant build, they remain Fix announced here.

Fix announced does not mean fixed now

Blizzard already marks multiple issues as fixed in the next Beta build.

That wording should be treated as:

Fix announced → deployment pending

not:

Fixed

We only move an issue to Verified Fixed after the relevant build is available and the behavior can be reproduced successfully.

Waylaid Crates

The official Known Issues post says some Waylaid Crates do not function correctly when the required quantity conflicts with an item's maximum stack size.

It also lists a specific Apprentice Curiosities problem involving Greater Magic Essence / Lesser Magic Essence targeting.

Blizzard says these are fixed in the next beta build. Until that build is active and verified, they remain in the fix announced state here.

Escaping Ban'ethil

During Escaping Ban'ethil, Sentinel Lynessa Duskblossom can run too fast and repeatedly use Strike.

Blizzard says the issue is fixed in the next beta build.

This is also an example of the kind of quest problem that belongs in both the Quest Index and this Known Issues tracker without creating duplicate canonical pages for the same bug.

Starshards and Twilight Focus

Blizzard lists an issue where Starshards does not benefit from the Twilight Focus talent.

A fix is announced for the next beta build.

Because this touches class/racial behavior and talent interpretation, we keep it separate from the fixed-snapshot Talent Calculator. The calculator is a reference planner, not a current bug-state simulator.

Beta bug reports can make it easy to misread a related talent as the broken mechanic.

Where Blizzard reports an ability issue, we will not automatically label every talent that modifies that ability as defective. The exact affected spell, rank, build, and fix wording need to be preserved.

UI and controller issues

Not every beta limitation appears in the formal Known Issues list.

Controller users are actively reporting Edit Mode friction, remapping limitations, and UI scaling concerns. Those observations belong primarily on Controller & Steam Deck Support unless Blizzard promotes a specific problem into the official Known Issues list.

Issue status format

Every issue we add should use one of these labels:

  • Reported — player report or reproducible beta observation.
  • Acknowledged — Blizzard has publicly recognized the issue.
  • Fix announced — Blizzard says a coming build contains a fix.
  • Verified fixed — re-tested successfully after the relevant build.
  • Regressed — previously fixed behavior returns in a later build.

This lets the page survive rapid beta patches without turning into a list of stale "fixed" claims.

What belongs on this page

Good fits:

  • widespread beta bugs;
  • official Known Issues;
  • class/spell bugs with material gameplay impact;
  • quest blockers;
  • UI/client bugs affecting many players;
  • bugs with an announced fix that players are searching for.

Poor fits:

  • one player's unexplained crash;
  • unsupported hardware troubleshooting;
  • balance complaints without a bug;
  • server queue status that changes hour by hour;
  • speculative datamining with no observed problem.

Sources