Find a rule or record a route
For the point arithmetic, use the budget table below. For a named node, inspect its rank cap and prerequisites in your game. To keep an ordered Mage or Warlock allocation, open the checked planner →. It starts from a blank draft or one of two editable 31-point examples.

Read a tree before spending
- Hover the intended milestone or capstone. Read its tree-spend requirement, any earlier talent requirement and exclusive choices.
- Count points already spent in that tree. Rows unlock at five-point intervals; major nodes sit after 10, 20 and 30 spent points and still need their own point.
- Spend only the points the class has earned. A 30-point gate is not an effect that works on a fresh character.
- After changing a starter-altering talent, inspect the picker’s opening spell before the next run.
A fresh 0-point Shaman screenshot is used here to show the real gates, not an allocated or tested build. Three spec slots appear on the current menu; we have not tested switching saved allocations across all versions.[1]
10, 20, 30 and 51 points: a gate is not a purchase
| Total budget available | What that permits | What still needs checking |
|---|---|---|
| 10 points | Ten points spent in one tree can meet its first major-node gate. | The node itself needs another point. A 10-point total budget cannot buy an additional gated node. |
| 20 points | Twenty spent in that tree can meet its next major gate. | Points spent in another tree do not meet this threshold; prerequisites may add restrictions. |
| 30 points | Thirty spent in the tree can meet the capstone gate. | With no spare point, the capstone is still unallocated. |
| 31–51 points | A 31-point total may reach a capstone if its path is legal. | 51 is the total cap, not 51 per tree. Check rank limits, earlier nodes and exclusive choices. |
For example, 30 points in a tree plus its one-point capstone uses 31 of the 51-point maximum and leaves up to 20 points for other choices. This arithmetic does not verify a particular allocation. Use the actual game tree to confirm every spend; the planner supplies two rule-checked 31-point examples, not a verified optimal 51-point recipe.[1]
Talent XP, reward points and marks
| Progress | What it changes | Where to inspect |
|---|---|---|
| Class talent experience | Earned by survival, kills, bosses and wins; harder zones pay more. It supplies that class’s talent points. | Talents |
| Account achievement points | Buys eligible reward perks and unlocks. | Achievements / Rewards |
| Class marks | Pays displayed gear-star upgrade costs after the cap is unlocked. | Collection / piece details |
If a milestone is unavailable, repeating the wrong currency purchase does not help. Check the precise missing requirement first.[1]
A useful respec experiment
- Export if you want a safety copy of your current progress.
- Record the current starter, allocated milestone and the failure you want to solve.
- Right-click to take points back or use the talent Reset control; inspect requirements as you rebuild.
- Change one engine, then compare the same class, zone and difficulty at similar permanent gear.
- Judge whether the specific failure improved. One dense-wave damage spike is not proof of a higher boss clear rate.
No price is charged for talent respecs in the inspected text. The limited Reset perks counter in Rewards is not this operation. Read the reward reset boundary →[1]
Apply the gate checks to a build
- Choose the spell interaction you want, then inspect its named milestone in the game.
- Record your earned budget, points already in that tree, node rank and any predecessor.
- Check whether allocating it changes the starter. Read the picker again before entering.
- For Warlock summons, inspect exclusive pet choices before counting their benefits together.
- Use the remaining choices to fix the failure you actually see, rather than adding every school.
Sources & checks
Warcraft artwork © Blizzard Entertainment.
- Aethus · original v0.130.0 ↗ (external website, opens in a new tab) · Point gates and talent descriptions, v0.130.0 snapshot 30 Oct, re-read 1 Nov 2026.