Beta known issues

Source: View source Version: Forever beta issue review (2026-09-29) Review: Source checked Last reviewed: 2026-09-29

Selected issues · reviewed 29 September 2026. Follow the dated developer posts below. A planned fix, an explicit resolution, and a player workaround are different kinds of evidence.

Blizzard's September 18 list records glancing-blow and resurrection-sickness problems, Legacy-menu errors below level 25, pending Waylaid Crate corrections, and the temporary removal of guild-charter signature requirements. Its remaining entries should be checked against later explicit corrections rather than assumed current solely because they remain in the older list.

September 27 queue correction

On 27 September at 17:57 UTC, Kaivax reported that Blizzard had fixed a fault that was filling the beta login queue. The response addressed a report of entering a queue after disconnecting.

This is a dated developer report about that fault. It does not promise that queues cannot occur, establish current server status, or confirm that all disconnection and character-lockout problems are fixed. The post gives no client build number or population limit.

September 24 additions and resolutions

Blizzard's follow-up identifies these testing problems:

• Changing party membership may move players between world instances.
• Tracking gaps affect Healthstones, Arcane Blast, pet cooldowns, and weapon enhancements.
• Retargeting can disrupt Bane and Curse tracking; Mana Gem tracking needs another spell cast.
• Priests track every spell by default.
• Stormwind's minimap has display problems; the Personal Resource Display omits combo points.

The same follow-up marks Escaping Ban'ethil escort behavior and Snowbound excess experience as resolved. This is Blizzard's stated resolution, not a new wiki gameplay test.

Later official updates

Read the September 24 development notes and its later stability notice. The September 22 client notes and September 21 quest correction retain their original scope. None establishes that every earlier issue is resolved.

Character lockout reports

For the error “Character with that name already exists”, Blizzard requested the affected beta character's name and, if possible, the exact last successful play/disconnection time. These details help locate the relevant logs. Include the timezone with your timestamp. The cited request does not confirm a universal fix; it concerns an existing character's lockout rather than advice to rename that character.

Class testing

Read the dated issue notes on Druid, Hunter, Mage, Paladin, Priest, Warlock, and Warrior before interpreting a test. The original list also covers interface and exploration issues; this page is a selection, not a complete tracker.

Check whether the report concerns a tooltip, a character-sheet display, or actual combat behavior. Those are different observations. Keep character level and equipment fixed when comparing two tests, and record the first error rather than a chain of later errors caused by it.

Community troubleshooting reports

Error after gameplay-style selection

A player identified build 1.60.1.69893 when reporting WOW51900309 after selecting a gameplay style on September 18. Several replies reported progress after fully closing lingering Battle.net/WoW processes and allowing an update; others reported continued problems. This is a community report, not a Blizzard-confirmed cause or universal fix.

Mac world-entry freezes

A player reported whole-system freezes on a Mac in build 1.60.1.69913, and said setting Secondary Lighting to Fair before entering the world avoided the issue in their subsequent session. This is a player-reported workaround; later replies describe continued crashes despite that setting. It is not a Blizzard-confirmed fix.

This older report predates the new client notes. Preserve its original build when comparing a retest.

For an installation or missing-access problem, begin with Game access and System requirements. A gameplay report is not evidence that an account has the required beta entitlement.

Record a useful report

Forever client version/build and date:
OS and relevant hardware:
Character, level, location, and affected ability or quest:
Steps to reproduce:
Expected result:
Actual result and first error:
Does it happen with addons disabled?
Screenshot or original report URL:

Use Project:Beta verification when submitting a wiki correction. Mark a resolved issue only with a dated developer update or an explicitly described retest. Keep player workarounds separate from official fixes.