Beta Known Issues

WoW Forever Known Issues: Mac Crashes & Bug History

Check WoW Forever known issues, Mac crashes, quest blockers and UI bugs. Compare dated Blizzard fixes with beta reports and launch-client checks.

By WoW Forever Wiki TeamOctober 29, 20268 min readBeta closed · Dated issue history, launch re-test pending

Use this guide for Mac crashes, quest blockers, class interactions and UI problems in WoW Forever. Start with the relevant checks, then compare dated issue records. An old beta report is not proof of a current release-client bug.

Mac performance improved in some beta builds, but that does not establish that every crash or graphics problem is fixed for launch. The beta closed on October 23. This page keeps dated developer updates and historical Known Issues separate from independent testing; we have not benchmarked the release client or re-tested the fixes below.

Troubleshooting before launch

What you see	Safe first check	Guide or evidence
Install is missing, an OS error appears, or Play returns after Launching	Confirm which game version Battle.net selected and copy the exact error before reinstalling	Installation checks
Mac freezes, colors look wrong or FPS drops after entering the world	Record hardware, macOS, build and location; back up settings before changing one graphics option at a time	Mac checks and October 21 developer plan, not confirmation of a universal fix
Among the Faithful shows sparkles but no wardrobe	Compare your chain step with the upstairs inn interaction before abandoning the quest	Wardrobe walkthrough and player reports
A minimap, UI or controller problem resembles an old beta report	Save your UI profile, record the build and compare the dated report with your own symptom	Addon/settings backup and controller guide
A class spell behaves differently from its description	Record the spell rank, talents, target and build; compare the normal ability button before blaming a macro or talent	Dated issue history and announced ability changes
Mail or trading shows Temporary Economy Hold	Check the exact message; a generic trade failure alone does not establish this restriction	Account restriction guide
You cannot enter a realm after the beta	Check the phase and access date before treating a closed service as a client bug	Access schedule, not a live realm-status check

These are troubleshooting paths, not confirmed cures. The historical table below records what sources said at the time, not which bugs are still active today.

Mac after beta: what should you check?

If the client will not install or launch at all, start with client selection and installation checks. For colors, lighting, freezes or frame-rate drops after entering the world, record the Mac model, GPU, macOS version, game build, location and graphics settings. Include when it happened, but remove personal account details from public logs.

Before changing profiles or reinstalling, back up addons and settings. When the intended service is available, compare the same location and settings, changing one option at a time. A crowded test area, a different resolution and a different Mac are not comparable benchmarks. Reports about one M-series model do not establish a frame-rate target for another.

The latest developer posts we verified below do not confirm a universal tint fix. The October 21 plan is not proof that the planned build shipped or solved the problem. This is also not a live server-status page; check access dates separately.

What to include in a bug report

Copy this checklist into your report and fill in what you observed:

Game version/build, date, time and time zone.
OS, hardware and graphics settings for a crash; quest name/ID and chain step for a quest blocker; spell rank and talents for a class issue.
Exact location, target or interaction, followed by the steps that reproduce it.
Expected result, actual result and exact error text. Say whether it also happens with the ordinary spell button or after safely disabling addons, if you tested those comparisons.
Screenshot or relevant log excerpt, with account details, personal file paths and other private information removed.

Do not describe an untried workaround as a successful test. For a freeze, record the last action and any saved error rather than repeatedly forcing the same crash.

Dated beta issue history

September 18 issue list and September 24 follow-up

Blizzard's September 18 post lists the following issues. The base list was checked September 23, and specific September 24 development-note changes are marked in the table. Fix announced means Blizzard wrote "fixed in the next Beta build"; we have not independently verified the fix in a live build. Work in progress repeats Blizzard's wording.

Issue	Status
Barber Chairs produce a Lua error	Acknowledged
Character friends are disabled in beta	Acknowledged
Minimap can sit partly off-screen	Acknowledged
Waylaid Crates fail when the required quantity exceeds the item’s maximum stack size	Fix announced
Apprentice Curiosities rejects Greater Magic Essence and incorrectly accepts Lesser Magic Essence as a target	Fix announced
Escaping Ban’ethil escort bug: NPC speed and repeated Strike	Officially listed resolved September 24; independent client re-test not performed
Starshards does not benefit from Twilight Focus	Listed fixed September 24; client re-test pending
Vengeance can trigger from periodic critical strikes	Listed fixed September 24; client re-test pending
Holy Strike rank progression feels wrong	Rank values changed September 24; client re-test pending
Character pane omits Level, Class and Titles	Work in progress
Create Firestone ranks 3 and 4 omit part of the conjured-item tooltip	Fix announced
Warlock pet mana and scaling details are missing from the character sheet	Work in progress
Warlock pet health scaling from Stamina displays incorrectly	Work in progress
Hunter and Warlock pet Hit scaling is missing from the character sheet	Work in progress
Hunter and Warlock pet Expertise is not displayed	Work in progress
Pet Movement Speed base values display incorrectly	Work in progress
Caster Glancing Blow chance and damage reduction are incorrect	Work in progress
Melee Glancing Blow damage reduction against higher-level targets is incorrect; displayed chances are therefore inaccurate	Work in progress
Opening Legacy System with Y before level 25 causes Lua errors on tabs 1 and 3	Acknowledged
Guild charters may be impossible to sign; zero-signature turn-in is temporarily allowed	Work in progress
Coldridge Valley does not reveal on the map when explored	Fix announced
Cooldown Manager implementation varies by class	Work in progress
Consumable and buff armor bonuses are multiplied by Bear Form armor bonuses	Acknowledged
Queued Heroic Strike, Cleave or Raptor Strike disables the spell queue window	Acknowledged
Damage taken during Arcane Missiles channeling can trigger a full-damage bolt	Acknowledged
Resurrection sickness duration is wrong at lower levels	Acknowledged

Player crash reports on build 69913

These historical player reports concern 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 September 18 Known Issues post describes several fixes as landing in the "next Beta build." Blizzard's September 24 development notes explicitly address Starshards/Twilight Focus, Vengeance and Holy Strike ranks, but we have not re-tested them in a client. Waylaid Crates remains Fix announced here; Escaping Ban'ethil was listed resolved in the September 24 follow-up, without an independent re-test by this site.

Mac graphics: developer updates in October

October 2 (UTC): WoW Developer Rommax said build 70205 had deployed performance improvements.
October 6 (UTC): build 70245 fixed Secondary Lighting using RAID graphics settings even when those settings were disabled. The UI could show Fair while the effect actually ran at Good.
October 8 (UTC): Rommax said the shadow issue should be fixed in that update. MSAA was temporarily disabled while its bugs were unresolved; performance, water visuals and rare tint issues still needed work.
October 10 (UTC): Rommax expected build 70338 to correct Stormwind water; the tint issue was still under investigation.
October 16 (UTC): build 70450 included a diagnostic test. Rommax did not expect it to fix tint/color problems and requested reports, rather than declaring them resolved.
October 21 (UTC): Rommax described a delayed fix build planned after Server Slam, hoping it would address tint. That is a plan, not deployment or successful-fix confirmation.

These are dated developer reports, not this guide's independent client verification or proof that every Mac crash is fixed. For continuing visual issues, include your GPU, macOS version, game build, location and server time in a reproducible report.

Fix announced does not mean fixed now

The historical Known Issues post marks multiple issues as fixed in the next Beta build. The table preserves that source wording, not a claim that these bugs remain unresolved in every later build.

That wording should be treated as:

Fix announced → verification 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.

The historical post announced a fix for the next beta build. This entry records that announcement; it does not establish whether the issue is present in your build today.

Escaping Ban'ethil

The historical escort symptom was Sentinel Lynessa Duskblossom running too fast and repeatedly using Strike.

Blizzard's September 24 Resolved Issues follow-up lists this escort issue as resolved. See the Escaping Ban'ethil archive for the historical symptom and the boundary between an official status update and independent testing.

For other missing NPCs or stalled objectives, use the Quest Index to find the matching walkthrough.

Starshards and Twilight Focus

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

Blizzard's September 24 notes say this interaction was corrected. That is an official patch-note claim, not an independent client verification.

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.

Beta players reported Edit Mode friction, remapping limitations and UI scaling concerns. Later official gamepad changes and the limits of those older reports are covered on Controller & Steam Deck Support; do not assume every September limitation persists at launch.

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.

Check the date and build beside a status before applying it to your own client.

Common questions and next steps

Does a listed fix mean my problem is solved?

No. Compare the affected symptom and build with the dated source. A planned fix does not prove deployment; an official resolved entry is stronger evidence, but neither is an independent test of your hardware or current client. If your symptom differs, use the matching troubleshooting guide rather than applying an unrelated beta workaround.

WoW Forever Beta — dates, access and phase information.
WoW Forever Quests: starts, requirements and dungeon checklists.
Controller & Steam Deck — input and handheld-specific beta behavior.
WoW Forever Talents — talent structure and fixed-snapshot tool.

Current friction guides

Among the Faithful owns the quest-specific wardrobe/stuck intent and keeps recent workarounds separate from this broad issue tracker.
Can't Install WoW Forever? owns Battle.net install, OS requirement and Play → Launching → Play troubleshooting.

Economic restrictions are not automatically beta bugs

If your message explicitly says Temporary Economy Hold, use the account and trading restriction guide. It distinguishes the published account restriction from service failures; a trade or mail error alone is not proof of a hold.