WoW Classic Talent Calculator – Plan Your Vanilla Build

The tier ladder

Every tier after the first needs 5 more points in the same tree. Points in your other trees never count toward a tier.

Related tools

How it works

Understand the result

Budget, tiers, and the 31-point shape

Classic talent points follow one rule: your budget is your level minus 9. You earn your first talent point at level 10, and one more at every level after that, so at level 60 the budget is 60 minus 9, which is 51 points. At level 40 the same rule gives 31 points, and at level 50 it gives 41 points. That budget is the whole game of Classic talent planning, because it is smaller than the trees are deep: no single tree can be filled, and no two trees can both be taken to their capstones, so every build is a choice about what to give up.

The default build on this page is the famous shape that makes that choice most sharply: Druid 31 / 20 / 0 at level 60. Points spent are 51, the budget is 51, and points remaining are 0. The deepest tier reached is Tier 7 in Balance, and the 31-point talent reads as Balance: taken. That shape is popular precisely because it takes a capstone and still reaches a useful depth in a second tree. The build code, Druid 31/20/0 (Level 60), records the shape in a form that can be shared and rebuilt, and the calculator’s result panel reports spent, budget, remaining, deepest tier and capstone status beside it, so that any build can be checked at a glance.

The tier rule governs what those points unlock. Each tier after the first needs 5 more points in the same tree: tier 2 needs 5 points, tier 3 needs 10, tier 4 needs 15, and so on up to tier 7, which needs 30. The rule counts all points in the tree, not points in one row, so ten points all spent in tier 1 unlock tier 3 just as well as five in tier 1 and five in tier 2. That is why the base guide asks why tier 3 needs 10 points rather than 5 in tier 2: the count is cumulative across the tree, and misunderstanding it is the most common tier error. Points in your other trees do not count toward a tree’s tiers, so a 20-point second tree does nothing for the first tree’s tiers, however deep it is.

The pairing arithmetic follows directly from the budget. Two 31-point talents would need 62 points, which is more than the 51 available, so they are impossible. A 31-point talent plus a 21-point talent would need 52 points, which is also more than 51, so that pairing is impossible too. The strongest second-tree talent you can pair with a 31-point talent costs 20 points, which is exactly the default 31 / 20 / 0 split: 31 plus 20 is 51, the whole budget, with nothing left over. Any build that claims a 31-point talent and more than 20 points elsewhere has miscounted, and the calculator’s remaining-points line will show it as a negative number, which is the planner’s way of refusing the build.

Every figure in that table is a displayed result from this page’s own calculator, using its preset buttons. The middle row is the instructive one: 17 / 17 / 17 spends the same 51 points as the other two builds, but reaches only Tier 4 in each tree, with the 31-point talent locked everywhere, because no tree holds the 30 points tier 7 requires. Breadth and depth trade against each other point for point, and the table shows the trade in its starkest form: the same budget, three shapes, and only the shapes that concentrate 31 points in one tree take a capstone.

Switching class, levelling, and what the planner does not check

Switching class changes the trees, and the planner handles that change by resetting the points. Probing that behaviour shows it directly: switch the default Druid build to Mage, and the trees become Arcane, Fire and Frost, with points spent falling to 0 and points remaining rising to the full budget. Set the level to 50 after that switch, and the remaining points read 41, which is the level-50 budget of 50 minus 9. The reset is worth knowing about before you switch, because a build typed for one class does not carry over to another: the trees are different, the points are different, and the planner starts you clean rather than guessing a mapping that would be wrong.

Levelling works the same way in reverse: raise the level and the budget grows by one point per level, while lowering it shrinks the budget and can push a finished build over budget. A 31 / 20 / 0 build that exactly spends its 51 points at level 60 would be 10 points over budget at level 50, where only 41 points exist. The planner reports that as a negative remaining figure, not as a silent trim, because silently trimming would hide which tree lost the points. If you plan a build for a lower level, build it at that level from the start, rather than building at 60 and lowering the level afterwards, because the over-budget display is a warning, not a plan.

One limit must be kept in mind throughout, because it defines what this tool is. This planner checks points and tiers only, at tree level. It does not check individual talent prerequisites, such as a talent that needs another talent fully ranked first, and it does not list individual talents at all. The tree names follow the Classic 1.12 trees, and the build code is a points plan, not a talent list. Treat the code as the shape of the build, then pick the exact talents in-game or in a patch 1.12 reference, checking prerequisites there. A points plan that passes this planner can still fail in-game if its talents violate a prerequisite chain, and the planner will not warn you, because prerequisites are outside its frame.

The patch note matters for the same reason. Patch 1.12 is the final patch of vanilla World of Warcraft, and the version Classic servers use as their talent reference. The point budget, the tier rules, and the tree names on this page follow that patch. The Burning Crusade trees are deliberately not mixed in here: at level 70 the budget is 61 points, not 51, and the trees differ, so a Classic build and a TBC build are never interchangeable. The related TBC planner on this site uses the 61-point budget, and confusing the two planners is the easiest way to produce a build that is valid nowhere: 61 points in a Classic frame, or 51 points in a TBC frame, both look plausible until the budget line is checked.

Depth against breadth: how to choose a shape

Every Classic build answers one question: how much depth in one tree is worth giving up breadth elsewhere? The 31 / 20 / 0 shape answers it with maximum depth in one tree and useful depth in a second, at the cost of nothing in the third. The 51 / 0 / 0 shape answers it with everything in one tree, at the cost of both other trees. The 17 / 17 / 17 shape answers it with even breadth and no depth, reaching Tier 4 everywhere and a capstone nowhere. None of those shapes is right in general; each is right for a different purpose, and the purpose should come before the points, not after them.

Ask what the build must do, then find the cheapest shape that does it. If the purpose needs a capstone, the shape must concentrate 31 points in one tree, and the remaining 20 points are the whole of the flexibility: they can take a second tree to Tier 5, which needs exactly 20 points, or they can be spread thinly, but they cannot buy a second capstone or a 21-point talent. If the purpose needs two mid-tier talents from different trees, the shape must split accordingly, and the capstone must be given up, because the budget cannot buy both. If the purpose needs a little of everything, the even split is honest, but it should be chosen knowingly, with the capstone locked everywhere, rather than discovered afterwards as a disappointment.

Finally, keep the build code with the reasoning, not just the numbers. A code like Druid 31/20/0 (Level 60) is compact, but it does not say why the 20 points sit in the second tree rather than the third, or which talents those points buy. Note the purpose beside the code, and the prerequisite checks you still owe in-game, so that the build can be rebuilt and defended later. A points plan without its reasoning is easy to misremember, and a misremembered build is how a valid plan becomes an invalid one.

Levelling up: the budget at every stage, and the tier ladder

The budget grows by one point per level, from the first point at level 10, so the budget at any level is that level minus 9. At level 10 the budget is 1 point. At level 20 it is 11 points. At level 30 it is 21 points. At level 40 it is 31 points, the budget the base guide names, and the first level at which a capstone becomes reachable, because a capstone needs 31 points in one tree. At level 50 the budget is 41 points, as the class-switch probe confirms, and at level 60 it is 51 points, the full Classic budget. Planning a build for a level below 60 means planning within that level’s budget, not within 51 points: a build that spends 51 points is not a level-50 build, however good it looks, and the planner will show it as over budget at level 50.

The tier ladder climbs five points at a time. Tier 1 needs 0 points in the tree, since it is open from the start. Tier 2 needs 5 points. Tier 3 needs 10 points. Tier 4 needs 15 points. Tier 5 needs 20 points. Tier 6 needs 25 points. Tier 7 needs 30 points, and the 31-point talent itself sits in tier 7, needing one more point beyond the 30 that unlock the tier. That last step is worth stating, because it is easy to confuse the tier requirement with the talent cost: 30 points unlock tier 7, but the capstone talent costs a 31st point, so a tree with exactly 30 points has tier 7 open but its capstone untaken. The default build’s 31 points in Balance are what take the capstone, not the 30 that open its tier.

That table is the level-minus-9 rule applied at each level, with the tier ladder applied alongside it. The level-40 row is the base guide’s own figure, and the level-50 row matches the probed class-switch result of 41 points remaining. The level-60 row is the default build’s budget. Read the spare-points column as the shape of the choice at each level: at 40, a capstone costs everything, and there is no second tree at all. At 50, a capstone leaves 10 points, enough for tier 3 elsewhere. At 60, a capstone leaves 20 points, enough for tier 5 elsewhere. Levelling does not just add points: it changes what a capstone build can also do, and a build planned at 60 should not be judged at 40, where its second tree cannot exist.

Sharing a build code, and checking one someone else shared

A build code like Druid 31/20/0 (Level 60) is made to be shared, and sharing it well means sharing the reasoning with it. The code alone says where the points sit, but it does not say why the 20 points sit in the second tree rather than the third, which talents those points buy, or which prerequisites still need checking in-game, since this planner checks points and tiers only. When you share a code, add one line for its purpose, such as which role or activity it serves, and one line for the checks you still owe, such as the prerequisite chains in the trees you used. A code with its reasoning can be rebuilt and defended. A code without it is easy to misremember, and a misremembered build is how a valid plan becomes an invalid one.

Checking a shared code takes one minute and three readings. First, read the points spent against the budget: at level 60 the budget is 51, so a code whose three numbers add to more than 51 is over budget, and a code whose numbers add to less than 51 has points unspent, which may be deliberate or may be a mistyped number. Second, read the deepest tier: a code claiming a capstone must have 31 points in that tree, and a code with 30 points in a tree has tier 7 open but its capstone untaken, which is a different build from the one claimed. Third, read the level: a code built at level 60 cannot be used at level 50, where the budget is only 41, without dropping 10 points, and the dropped points should come from a deliberate choice, not from silently trimming the second tree. A code that passes all three readings is a sound points plan, subject to the in-game prerequisite check that this planner does not perform.

When a shared code does not fit your level, rebuild it at your level rather than using it over budget. At level 50, a 31-point capstone leaves 10 points, enough for tier 3 in a second tree, and the honest level-50 version of a 31 / 20 / 0 build is therefore 31 / 10 / 0, not 31 / 20 / 0 with 10 points silently dropped. At level 40, a capstone leaves nothing, so the honest level-40 version is 31 / 0 / 0, and any second-tree depth must wait for levelling. Rebuilding at your level keeps the code’s purpose, the capstone, while adapting its shape to the budget you actually have, and the planner’s remaining-points line confirms the adaptation: it should read 0 for a finished build, not a negative number.

Checking a build at a glance

Every build on this page can be checked in three readings: points spent against the budget, deepest tier against the capstone claim, and level against the budget it allows. A build that passes all three is a sound points plan, subject to the in-game prerequisite check that this planner does not perform. A build that fails any one of them is not a build yet, however good it looks, and the planner’s remaining-points line will say so, as a negative number for an over-budget build, or as unspent points for an unfinished one. Read those three lines before sharing any code, and the codes you share will be the ones worth sharing.

New guide: WoW Classic Talent Builds Explained: Trees, Leveling, and Classic-Era Mechanics

World of Warcraft Classic uses the talent system the game launched with: points earned level by level, spent in three trees per class, with deeper tiers unlocked by investing in the tree.

One talent point per level from level 10 to level 60, for 51 points in total. A level-60 character has 51 points to spend, and no more; every build is a 51-point allocation across three trees. The full guide, WoW Classic Talent Builds Explained: Trees, Leveling, and Classic-Era Mechanics, works through the method in detail, with worked examples and the cases that most often go wrong.

Frequently asked questions

More calculators