WoW Forever race and class matrix: every announced cell

Choose a character without relying on a tier list #

Blizzard’s Deep Dive names six additional pairings: Gnome Priest, Human Hunter, Dwarf Shaman, Orc Mage, Troll Warlock and Undead Paladin. An announced pairing is useful for a shortlist; it is not evidence of a best race, complete talent tree, or current damage ranking.

1. If you have a group, agree its faction and ruleset before choosing the appearance you want.
2. Use the matrix to shortlist a supported pairing, then confirm that the launch character-creation screen offers it on your account.
3. Check the class profile for its announced role and known limitations. Keep racial utility separate from unmeasured throughput.
4. Save two or three candidates in the class shortlist, then choose based on the activity you actually want to play.

Current access: live since November 4 #

WoW Forever went live in all regions on November 4 at 3pm PST / 23:00 UTC. Blizzard closed the beta on October 23, and name reservations ended November 3. The dated beta instructions and observations below are historical, not a way to join the closed test or proof of launch behavior.

The sourced matrix #

“Both factions” and “Alliance only” / “Horde only” describe the Skyborne selection announced by Blizzard; the race’s faction is chosen at character creation. The six combinations for existing races come from the September 13 Deep Dive recap and the announcement. An “Unknown” cell is not a denial: it records that this edition has no source for that combination yet.

Blizzard’s September 30 and October 7 class deep dives now directly cover Priest and Warlock as well as the other class profiles. The complete playable race/class matrix still needs current client evidence.

How to read an unconfirmed cell #

Cells use three labels. Officially announced: named by Blizzard in the sources cited here. Reported: described by Wowhead or WOWTBC.GG without independent verification in this edition. Unknown: no reviewed source supports the combination, which is the honest state for the rest of Classic-era matrix.

Do not infer that an absent combination is impossible, and do not import a Classic-era matrix to fill cells. The beta character-creation screen is the place to confirm combinations you care about.

Official Skyborne racial effects #

Blizzard’s October 26 tuning supersedes the September Skyborne values: Wind-Blessed gives 2% Haste; Skysight gives 15% movement speed for 15 seconds; Read Leyline gives 50% Health and Mana regeneration for 15 seconds. Using Skysight at an elemental convergence grants Charged for one hour, raising its movement-speed benefit to 30%. Using Read Leyline at a Ley Line grants Attuned for one hour, raising its regeneration benefit to 100%. The October 27 clarification says both effects persist through death and are removed on entering a raid. Read Leyline cannot be used during Innervate and is replaced by that more powerful effect. Kingy has not tested these interactions; the new notes do not restate every other racial or cooldown.

Blizzard’s October 7 update says SD Skyborne characters and SD Skyborne Druid forms are still in development for early 2027. HD refinements are also planned; do not assume the generic HD/SD option already covers Skyborne.

Coverage is not a ranking #

Blizzard’s class deep dives now cover the roster directly. Their published descriptions support character planning, not measured class rankings or optimized talent allocations. Compare the class profiles and check current tooltips before choosing a build.

A familiar class name does not establish that Classic or Season of Discovery mechanics carry over. The complete playable race/class matrix still needs client evidence.

Verify your row in the beta #

The beta cap increased from 20 to 30 on October 1. Character-creation checks do not require leveling. Record the build with any missing option rather than treating it as a final restriction.

1. Open character creation in the current build and write down the combinations you can actually select.
2. Record the build version, ruleset and date with any confirmations or contradictions.
3. Submit observations that contradict this matrix through the contribution flow with the page URL and build details.

KEEP GOING

Your next step.