Beta known issues

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

The later naming notice follows these dated beta reports.

Selected issues · reviewed 12 October 2026. The October 10 graphics follow-up was checked against the original staff post. Older sections keep their own evidence dates. A planned fix, an explicit resolution, and a player workaround are different kinds of evidence.

The October 1 update has published notes. Newer dated entries below take precedence where they explicitly correct an older report.

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.

October 8 testing issues

Blizzard's new dated list reports:

• Skyborne Druid bear and travel textures were updated; cat textures, some Zephras Isle creatures and other creature appearances await a future build.
• Ferocity does not show its pet critical-strike increase on the character sheet. Blizzard identifies this as a display-only bug.
• Some Professions-window icons appear broken.

The list supplies no exact client build or delivery date for the pending textures. Character models covers the separate SD Skyborne roadmap. Beta maintenance (October 8, 2026) records that day's service announcement and confirmed return.

October 1 testing issues

Blizzard's new list identifies these problems:

• Closely positioned attackers can be parried or blocked from behind; leaving more space is the stated workaround.
• Consecutive casts can delay the next spell's preparatory audiovisual effects.
• Changing Gamepad UI mode resets the active layout.
• Scroll of Liminal Passage and Mage Research access can malfunction.
• Some debuffs generate no threat; Retribution Aura reads the recipient's spell power.
• Installation size is excessive, with a reduction planned.

The same list retained a Warrior hit-chance bug. A later Warrior follow-up reports the correction and removal of Dual Wield Specialization's hit bonus; check that later source before treating the earlier entry as current. This is source chronology, not an independent gameplay retest.

October 6 restart notice

See Beta maintenance (October 6, 2026) for the dated changes and their limits.

Mac graphics follow-ups

Blizzard developer Rommax reported that build 70205 had deployed with performance improvements, while requesting further tint-bug reports. The developer later confirmed that 70245 corrects Secondary Lighting using raid settings despite those settings being disabled. A fix for abnormal shadows was still prospective in that October 6 post.

The developer also explained that mtl_1_1 shader naming and an Unknown Apple GPU-family label in logs do not themselves indicate a rendering fallback or cause the reported slowdown. These statements do not establish that every Mac crash, tint problem, or performance regression is resolved. Record the actual build when comparing results.

October 8 graphics follow-up

At 23:05 UTC, Rommax reported that abnormal Mac shadows should be fixed in that day's build. MSAA had been disabled while its visual bugs were deferred; further performance, hitching, water and tint investigations remained underway.

The source literally names 79291. This article preserves that identifier rather than silently changing it to a different build. The tentative wording is not an independent gameplay confirmation, and the post gives no guarantee that MSAA will return before release.

October 10 graphics follow-up

Rommax reported that build 70338 should fix Stormwind's water rendering. The tint problem was still unresolved; a reproducible case had been found and a fix was hoped for the following week.

This is a tentative developer report about that location, not proof that every water or Mac graphics problem is fixed. The projected tint fix has no confirmed delivery date in the cited reply.

Australian login-dialog correction

Blizzard marked the erroneous Australian social-features restriction dialog fixed on 3 October at 17:34 UTC. This addresses the specified beta bug; it does not describe general account-verification policy or every player's access problem.

October 1 service incident

Blizzard acknowledged a beta login-blocking incident at 00:03 UTC on October 2 (October 1 PDT). It is a historical incident report, not evidence that the service remains unavailable today.

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.

September 23 Auto Shot and wand notice

Blizzard identified a beta bug that shortened the intended 0.5-second cast before Hunter Auto Shot and wand attacks. Players consequently needed to stand still for less time than intended. Kaivax's September 23 announcement planned a fix in a later beta build, with the following week as a tentative target.

This notice establishes the intended cast time and the reported bug at that date. It does not identify a delivered fix or a build containing it. Use a dated follow-up or a repeatable gameplay test before marking it resolved.

Later official updates

Read the October 1 update alongside the historical September 24 development notes and its 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 September client notes. Read the later official graphics notices before comparing a retest, and preserve the original report’s build.

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.

Sources

HELP IMPROVE THIS FOREVER REFERENCE

Evidence still needed

Clarify the literal build identifier in Rommax's October 8 graphics follow-up; Repeatable Mac shadow and tint retests in a recorded Forever build; Follow-up status for pending October 8 textures and profession icons

Record the Forever build, observation date, and a source or screenshot. Update the article and remove only the tasks your evidence resolves.

Add evidence or resolve a task · What to record · Browse research tasks