How to plan a WoW Forever talent build
Choose a class, inspect the talent requirements, allocate your points and keep a copy you can reopen.
How many talent points can I spend?
This planner uses the standard budget of character level minus nine, from level 10 to level 60. Level 10 has one point, level 30 has 21, and level 60 has 51. All three trees share that budget; the displayed split records points spent in each tree, not three separate allowances.
The Legacy Talented perk can change when points begin to arrive. Select an unlocked rank from 0 to 5 in the calculator to apply its earlier point timing. The examples here use rank 0; all settings remain capped at 51 total points.
Unlocking rows
Each deeper row requires five more points in earlier rows of the same tree. The second row needs five; the third needs ten; the fourth needs fifteen. The point you spend on a fourth-row talent makes it at least a 16-point commitment. Points in another tree do not unlock that row.
Following prerequisite arrows
A named prerequisite must be at its maximum rank before the dependent talent can be learned. Satisfying the row gate alone is not enough. The inspector explains the next unmet condition; the text reference lists the prerequisite beside the talent.
How do I add or refund points?
- Choose a class. Open its page and set the level before allocating.
- Inspect a talent. Read its rank effect, required points and any prerequisite. On desktop, hovering or focusing a node shows details.
- Add a point. On desktop, click the node. On a touchscreen, tap to inspect it, then use the + button.
- Refund a point. Right-click on desktop, or use the − button in the inspector. Keyboard users can focus a node and press + or −.
- Review the allocation. The selected-talents list shows the learned ranks and the tree counters show how the shared budget is split.
On a small screen, use the tree tabs to move between trees. Close the inspector with its × button to return to browsing. You can read or search all rank descriptions below the calculator, including talents that are still locked.
How do saving and sharing work?
Save build stores the class, level, points, snapshot and save time in this browser. Give a build a name before saving. The site keeps up to 100 distinct saved allocations and never silently evicts an older save. Use Import / Export to keep a portable backup. Per-class drafts are saved automatically as you edit. A save is not an account backup: it does not sync to another device, and clearing site storage removes it.
Share build reveals a portable link and tries to copy it. If copying is unavailable, select the link field and copy manually. Anyone with the link can inspect the allocation. Editing a newly opened build does not change the original link.
Links include the data snapshot so the same point encoding is not silently applied to a different tree. A link from an incompatible snapshot is preserved and explained rather than imported. Open Build updates to inspect the original and preview migration. Removed talents and points that fail current prerequisites are refunded; nothing is spent on a replacement automatically.
Why won’t the planner accept my change?
The talent is locked.
Check three things: remaining points, points in earlier rows of that same tree, and a fully ranked named prerequisite. A talent can be inspected before it is available to learn.
I cannot refund an earlier point.
The refund would invalidate a deeper row or dependent talent. Remove the dependent points first, or reset that tree. The whole-build Reset clears the current allocation while leaving saved builds intact.
I cannot lower my character level.
The current allocation spends more points than the lower level permits. Refund enough points first. The planner does not decide which choices to remove for you.
My save is missing on another device.
Local saves belong to a particular browser and device. Use a share link to move an allocation. If browser storage is blocked, keep the share link instead of relying on a local save.
The displayed value differs from the game.
The imported snapshot can lag beta tuning, and tooltip values can depend on spell rank or character scaling. Check the source date and the full condition in the reference. A legal allocation is not a guarantee of current in-game performance.
Choose, compare and update a build
Build guides cover all nine classes and 27 trees with complete allocations, conditions and point-by-point routes. Compare builds accepts two same-class links and shows exact rank differences. Build updates shows how an archived allocation maps to the current snapshot before you choose to migrate.
Choose the next page for your task
Choose a class and open its guide, compare snapshot changes, or check how the data is sourced.