Which issues were added on October 8?

Blizzard’s main known-issues post retains older entries. Read the newer reply and build notes alongside it so an explicitly fixed problem is not mistaken for a current one.

New October 8 known issues
SymptomOfficial statusWhat it means
Ferocity does not increase the pet crit value on the character sheet Visual bug only It does not mean the talent stopped working.
Some profession-window icons appear broken New October 8 issue No driver change or file-deletion fix was announced.
Skyborne Cat Form and some creature, pet and mount textures remain old Waiting for a later build Their delivery differs from the updated Bear and Travel Form textures.
Short answer

October 8’s new WoW Forever beta issues concern the pet crit display, profession icons and pending textures. Older LUA and charter entries remain in a separate list; explicit later fixes take precedence over older issue descriptions.

Why does Cooldown Manager miss some effects?

All classes, racials and trinkets are now supported. Consumables remain planned for a later patch, replacing the old description of only five supported classes. If the feature is off, check Options > Gameplay Enhancement. A consumable outside the current scope does not mean your entire class is unsupported.

Where did my gamepad action-bar settings go?

The options moved to Edit Mode. Previous Options settings do not transfer automatically: open Edit Mode, select the gamepad action bar and set them again. Layouts are now stored separately by UI type. October 8 also fixes input after looting and changes the initial focus when opening the map.

What is the status of Legacy and Barber Chair LUA errors?

The main issue list still contains the Legacy error from opening tabs one and three via Y before level 25, along with the Barber Chair error. However, Legacy testing points were granted on October 8, and clicking an earned challenge now opens its window. The older level condition should not be presented as a universal workaround for every current tester.

When reporting the error, include the shortcut, tab, character level and whether the same steps reproduce it. Describing the action that opens the error is more useful than simply saying Legacy is broken. No official file-deletion or addon-removal procedure is provided for these symptoms.

What if I cannot sign a guild charter?

Blizzard’s main list retains unsigned charter turn-in as a temporary beta workaround. That is not an announcement that launch guild requirements are removed. The October 6 maintenance also addressed a separate error when joining or leaving a guild.

Which older entries have later fixes?

Older issues and later fixes
Older issueNewer official information
Party leader transfers world instances when forming or changing a group October 1 says the leader should no longer transfer.
Character pane lacks level and class October 8 adds them to the left pane; it does not make the same claim about titles.
Personal Resource Display Combo Points October 8 updates both the resource display and target frame.
Retribution Aura uses the wrong character’s spell power October 8 makes it use the Paladin’s spell power.
Demoralizing Shout / Roar generate no threat Both are fixed on October 8.
The escort NPC in Escaping Ban’ethil runs too fast October 8 slows Sentinel Lynessa Duskblossom.

“Fixed in the next build” is not confirmation for the current client. But when a later build explicitly lists the fix, an older entry alone does not prove the bug persists. Include the build and reproduction steps in a new report to preserve that distinction.

Is a failure to launch the same kind of problem?

A LUA window occurs inside the game. Installation and Battle.net access failures happen at a different stage. Record the exact error and where it appears, then check system requirements and beta access separately. A known pet-stat display problem does not indicate that your account has lost beta permission.

Related guides