Based on Blizzard’s September 24 known-issues post. The rest of that build is in WoW Forever beta patch notes.
Why do mobs disappear when I join a group?
Added on September 24: creating or changing a party can transfer you to a different world instance, and the mob you both wanted blinks out. Blizzard is working on improvements and promised an update soon.
Until it's fixed, invite before you head to the mob, so any transfer happens before the pull, not mid-fight.
Is Cooldown Manager broken?
Check that it’s on first: since the September 24 build the Cooldown Manager is off by default and lives under Options > Gameplay Enhancement. Only Druid, Mage, Priest, Warrior and Warlock are testable right now, and spell ranks aren’t supported yet. Known tracking bugs:
- Banes and Curses stop tracking if you drop your target and retarget one that already has them.
- Healthstone, pet cooldowns and item enhancements (Windfury, rogue poisons) can’t be tracked.
- Priests track every spell by default.
- Arcane Blast can’t be tracked, and Mana gem needs an extra spell cast before its cooldown shows.
Warriors and Hunters still have a separate issue: queueing Heroic Strike, Cleave or Raptor Strike turns off your spell queue window, so abilities can feel laggy.
Why does Legacy throw a LUA error?
The Y hotkey opens Legacy even before level 25, and doing that throws LUA errors on tabs 1 and 3. Leave it alone until you hit 25.
Barber Chairs also trigger a LUA error. If that's what you hit, leave your addons alone; it's the game.
Can't sign a guild charter?
Hand it in anyway. Signing can fail, so Blizzard temporarily allows unsigned charters; it's still marked work in progress.
What the September 24 build fixed
Three “fixed in the next Beta build” items from September 18 are named in the September 24 notes:
- Starshards (Night Elf Priest racial) now gets pushback resistance from Twilight Focus.
- Vengeance (Retribution Paladin) now only triggers off non-periodic crits and caps at 3 stacks.
- Holy Strike now scales 25/29/32/36/39/43/46/50% weapon damage by rank, so every rank is a real upgrade.
The same build fixed Mac water and display bugs and a memory leak that slowly dragged performance down.
Does "fixed in the next Beta build" mean it's fixed?
No. It means the fix isn't in the game yet. These are still flagged that way and don’t appear in the September 24 notes: the Waylaid Crate bugs, the Create Firestone Rank 3-4 tooltip and Coldridge Valley not revealing on the map.
Blizzard also moved two quest bugs under “Resolved” on September 24: the too-fast NPC in Teldrassil’s “Escaping Ban’ethil” and extra XP from Loch Modan’s “Snowbound”. Both notes still point to the next beta build and neither is in the build notes, so you may still see them.
What other bugs are known in the beta?
| Area | Bug |
|---|---|
| Friends list | Character friends are disabled in the beta |
| Minimap | Can sit partly off screen; Stormwind display issues are due in a later build |
| Personal Resource Display | Doesn’t show combo points |
| Character pane | Doesn't show level, class or titles (work in progress) |
| Druid, Bear Form | Armor from consumables and buffs gets multiplied by the Bear Form bonus |
| Mage, Arcane Missiles | Taking damage while channeling fires a full-damage bolt instead of a truncated one |
| Resurrection sickness | Wrong duration at low levels |
| Warlock and Hunter pets | Character sheet shows wrong or missing mana, hit, expertise and speed values |
| Glancing blows | Wrong chance and reduction for casters; wrong melee penalty vs higher-level targets |
What should a beta bug report include?
- Class, level and zone; if you were grouped, when you formed the group.
- The key or ability you used right before the error.
- What you expected, what happened, and whether it happens again.
Not "Legacy is broken" but "opened it with Y, tab 3 threw a LUA popup, again after relog". Crop chat and account details out of screenshots.
What if WoW Forever won't launch at all?
LUA popups happen in game. If the client won't start or Battle.net warns you during install, check your GPU against the system requirements and note the error code.









Share your experience