Choose your class and the job you want to do
Choose a class below for a full three-tree deep dive: 27 illustrated maps across all nine classes, selected talent tooltips, level-20 example allocations and group-planning advice. These guides use the 17 September beta-derived data export and distinguish early playable choices from later-tree theorycraft.
| Class guide | Decisions covered |
|---|---|
| Warrior talents | Arms, Fury, Protection |
| Paladin talents | Holy, Protection, Retribution |
| Hunter talents | Beast Mastery, Marksmanship, Survival |
| Rogue talents | Assassination, Combat, Subtlety |
| Priest talents | Discipline, Holy, Shadow |
| Shaman talents | Elemental, Enhancement, Restoration |
| Mage talents | Arcane, Fire, Frost |
| Warlock talents | Affliction, Demonology, Destruction |
| Druid talents | Balance, Feral Combat, Restoration |
How to turn a talent guide into a build
First choose the role and activity: solo levelling, a dungeon tanking session, healing practice or damage in a coordinated group. Next select the interaction you want to reach, and use the Wowhead Forever calculator to check the earlier rows and prerequisites. Save the finished link with the date and the purpose of the build.
A final-row talent is a destination, not a full allocation. The points spent on the way can change resource use, control or survivability. Compare those choices explicitly before copying a route from someone whose equipment and activity differ from yours.
Keep the point budget visible
The calculator displays a 51-point maximum. A 31-point investment leaves 20 points for the other trees; it cannot include a second talent that requires 21 points in its own tree. At lower levels, plan the next meaningful unlock rather than pretending the level-60 allocation is already available.
Our route tables deliberately identify talents to investigate rather than publish untested numerical damage rankings. If the client differs from the snapshot, use the client for that session and record the discrepancy with the build number.
Record selected utility alongside the role
A class name is not a complete list of what a player brings. Power Infusion, Trueshot Aura and Mana Tide, for example, are talent choices in the snapshot. A Druid’s Feral label also needs Cat or Bear intent; a Hunter may be planning melee Survival or a petless setup.
For a guild sheet, record character, intended role, calculator link, optional group utility and last-reviewed date. Confirm changes before assigning an encounter job. These are suggested planning fields, not a claim that RaidMuster automatically imports calculator builds.
Beta data, diagrams and how to read this guide
Talent positions, ranks and descriptions here use the 17 September Talents Forever export. Its current website identifies the source as beta client build 1.60.1.69876, and all 468 exported class talents are marked beta-derived. The export’s introductory readme still refers to demo transcription; this guide uses the per-talent beta records, not the older spellbook material. This is attributed community extraction, not RaidMuster gameplay testing or confirmation of final tuning.
Data credit: Chris Baldwin / Talents Forever, licensed CC BY 4.0. We have reorganised the data, drawn the reference maps and added analysis. Icons and game tooltip text belong to Blizzard Entertainment. The three illustrations are diagrams made from that data, not screenshots taken inside the beta.
Each tree below has a full illustrated map, selected talent details, practical trade-offs and an example allocation. The detail tables show the exported text at the talent’s maximum rank. Ability damage and healing numbers can refer to an exported spell rank; they are not level-60 performance predictions. “Changed” in a diagram includes wording or position changes, not necessarily a balance buff.
Rows require 0, 5, 10, 15, 20, 25 and 30 points already spent in that tree. An arrow also requires its named talent at maximum rank. With one point per level from 10, the opening level-20 cap gives 11 points: enough to enter row 3, not to reach row 4. Our example allocations are checked against these exported rules; validate them against your client before spending.