WoW TBC Talent Calculator – Plan Your Burning Crusade 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

Reading your build: budget, spent, remaining, tiers, and code

This planner answers four questions about a talent build, and the result panel shows all four together, so that a build can be checked at a glance. How many points have you spent? How many does your level allow? How many are left, or over? Which tiers have you unlocked, and is the 41-point talent taken? The build code then compresses the whole plan into one line for sharing. The default build is a Druid at level 70 with 41 points in Balance, 20 points in Feral Combat, and 0 points in Restoration. The budget at level 70 is 61 points, because points are earned from level 10 onward, one per level, so the budget is level minus 9: 70 minus 9 is 61. Points spent are 41 plus 20 plus 0, which is 61, points remaining are 0, and the build code is Druid 41/20/0 (Level 70). The deepest tier reached is Tier 9 in Balance, and the 41-point talent is shown as taken in Balance, because 41 points in a tree reaches tier 9 and spends the 41st point on its talent. Feral Combat, with 20 points, reaches Tier 5, and Restoration, with 0 points, leaves only Tier 1 open. Every line on the panel follows from those few numbers, and every line can be checked from them by hand.

The second row is the most instructive, because it spends the same 61 points and reaches a completely different shape. A 21 / 20 / 20 split spends 21 plus 20 plus 20, which is 61, with 0 remaining, exactly like the default, but its deepest tier is only Tier 5 in Balance, and its 41-point talent is None yet, because no tree reaches 40 points. The 21 points in Balance reach Tier 5, since tier 5 needs 20 points in the tree, and the 20 points in each of the other trees also reach Tier 5 in those trees, but no tree approaches the 40 points needed for Tier 9. The trade-off is therefore visible in the table without any further explanation: the default buys depth, a 41-point talent in one tree and a Tier 5 second tree, at the cost of abandoning the third tree entirely, while the even split buys breadth, Tier 5 in all three trees, at the cost of no 41-point talent anywhere. Neither shape is better in the abstract; the choice depends on which talents the player wants, and the planner’s job is to make the cost of each shape visible before points are spent in the game.

The fourth row shows the budget check doing its job. Lowering the level from 70 to 60, with the split unchanged at 41 / 20 / 0, lowers the budget from 61 to 51, because 60 minus 9 is 51, while points spent stay at 61. Points remaining become -10, and the page reports 10 points over budget, telling you how many points must be removed or how much the level must rise before the build is legal. The tier lines do not change in that row, because tiers depend on points per tree, not on level, and 41 points in Balance still reaches Tier 9 even when the build as a whole is over budget. That separation is important: a build can have legal tiers and an illegal total at the same time, and the page reports both, so that fixing the total does not require rethinking the tiers, only removing 10 points from somewhere, or raising the level by 10, until spent equals or falls below budget. The page’s own guidance for an over-budget build states exactly that remedy: lower the points in a tree, or raise the level, until points spent are equal to or below the budget.

The tier rule, stated until it cannot be misunderstood

The tier rule is the most misunderstood rule on this page, and the page states it three times in different forms because it is so often misread. Here it is once more, in the form that prevents every common misreading. A tier unlocks when you have 5 points in that tree for each tier above it: tier 2 needs 5 points, tier 3 needs 10, tier 4 needs 15, tier 5 needs 20, tier 6 needs 25, tier 7 needs 30, tier 8 needs 35, and tier 9 needs 40, all counted in the same tree. Points in your other trees never count toward a tree’s tiers. The rule counts all points in the tree, not points in one row: tier 3 needs 10 points anywhere in the tree above it, and ten points all spent in tier 1 unlock tier 3 just as well as five in tier 1 and five in tier 2, as the page’s own guidance explains. The same rule runs up the tree: tier 9 needs 40 points anywhere in the tree, and the 41-point talent is the talent at the bottom of the tree, in tier 9, which takes the 41st point spent in that tree to take.

The page’s own tier ladder table makes the rule concrete, and it is worth reproducing in words because it is the reference for every build. With 0 to 4 points in a tree, only Tier 1, the top row, is open. With 5 to 9 points, Tier 2 opens. With 10 to 14, Tier 3 opens. With 15 to 19, Tier 4 opens. With 20 to 24, Tier 5 opens. With 25 to 29, Tier 6 opens. With 30 to 34, Tier 7 opens. With 35 to 39, Tier 8 opens. With 40 or more points, Tier 9 opens, and the 41-point talent row opens with it. The default build shows the ladder in action, as the page states: 41 points in Balance reaches tier 9, 20 points in Feral Combat reaches tier 5, and 0 points in Restoration leaves tier 1 open only. The even-split probe shows the ladder from the other side: 21 points in Balance reach Tier 5, because 21 falls in the 20 to 24 band, and the same holds for the other trees. A build’s tier line for each tree is therefore read directly from that ladder, from the points in that tree alone, and any tier claim that adds points across trees, or that counts only points in a single row, is wrong by the rule as stated.

Two consequences of the ladder deserve emphasis, because they shape every build decision. The first is that the 41-point talent is expensive in a precise sense: it costs 41 points in one tree, which is more than two-thirds of the 61-point budget at level 70, leaving only 20 points for everything else. That is why the default 41 / 20 / 0 split is exactly at the budget, and why the page’s own guidance states that the strongest second-tree talent you can pair with a 41-point talent costs 20 points. The second consequence is that a 41-point talent cannot be paired with a 21-point talent, because 41 plus 21 is 62, which exceeds the 61-point budget, and two 41-point talents would need 82 points, which is further still beyond it. Those impossibilities are arithmetic, not opinion, and the planner enforces them through the budget line: any split that attempts them will show negative remaining points, and the remedy is to remove points until the total fits, which necessarily means abandoning either the second 41-point talent or the 21-point second-tree plan. Planning with the ladder and the budget together, rather than with either alone, is what stops a build from looking good on tiers and failing on points, or looking good on points and failing on tiers.

Levels, budgets, and the 71-point trap

At level 70 you have 61 points, not 71, and the page states why in a sentence that corrects a persistent confusion: the number 71 belongs to the next expansion, where the cap is level 80, while in The Burning Crusade the cap is level 70, the first point comes at level 10, and one point per level after that gives 61. The budget rule, level minus 9, gives the same result at every level in the planner’s range of 10 to 70: at level 60 it gives 51 points, as the probed over-budget case shows, at level 70 it gives 61, and at level 10 it gives 1, the first point itself. A build planned with 71 points at level 70 is therefore over budget by 10 before it starts, and the planner will show that overage plainly, just as the level-60 probe shows -10 remaining for a 61-point split. The trap is easy to fall into because 71 is a memorable number from a later expansion, and because a build that spends 71 points can look complete and balanced while being illegal in TBC. Check the budget line first, before admiring the tiers, because a build that exceeds its budget is not a build at all, whatever its tiers say.

Levelling builds need the same discipline in reverse. A build planned for level 70 cannot simply be played at level 60 by spending the same split, because the budget at 60 is 10 points smaller, and the planner’s over-budget display is the warning that the split must be trimmed. The natural way to trim is to remove points from the lowest-priority tree first, preserving the tiers that matter most, and to re-check the tier lines after trimming, because removing points from a tree can drop it a tier, and a tier drop can lock a talent that the build depended on. Conversely, a build planned at a lower level can be grown toward 70 by adding points, but the additions should follow the ladder: add points to reach the next tier in the tree that needs it, rather than spreading them thinly across trees, because a point that does not reach a tier threshold buys no new row, while a point that crosses a threshold opens a whole row. Plan by level, check budget and tiers together at each level, and treat the build code as a snapshot for one level, not as a plan that holds at every level.

What the planner does not check, and why the build code is not a finished build

This planner checks points and tiers only, and its own guidance states the limit twice, because it is the limit most likely to be forgotten in excitement. 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. A build code such as Druid 41/20/0 (Level 70) is therefore a points plan, not a finished build: it says how many points go into each tree, which tiers those points unlock, and whether the total fits the budget, but it does not say which talents those points buy, in which order, or whether any chosen talent requires another talent that the plan has not bought. Treat the build code as the skeleton of a build, then pick the exact talents in-game or in a patch 2.4.3 reference, as the page advises, and check each talent’s prerequisites against the plan before spending points. A plan that passes the planner and fails a prerequisite in-game is not a planner error; it is a plan that was never checked against the talents themselves.

Patch version is the second limit, and it is stated on the page with the same care. Points and tier rules follow patch 2.4.3 references, patch 2.4.3 is the final patch of The Burning Crusade, and it is the version most TBC Classic servers and private servers use, as the page states. If you play on a server with changed rules, check its own talent rules before you spend points, because a server that changes the budget, the tier thresholds, or the tree contents will make a plan built for 2.4.3 wrong in ways the planner cannot detect, since the planner encodes 2.4.3. The tree names on the page follow that patch, and the default build’s trees, Balance, Feral Combat, and Restoration for the Druid, are the 2.4.3 trees for that class as displayed. Other classes have their own three trees on the page, and the same budget and tier rules apply to them, but the talent contents of those trees are not listed here, and no talent from any tree is named in the new sections above, because this planner does not list individual talents and no unverified talent combination is quoted.

Scope note, stated plainly: this is a fan-made planning tool, not affiliated with Blizzard Entertainment, as the page’s own disclaimer states. World of Warcraft and The Burning Crusade are trademarks of Blizzard Entertainment. Points and tier rules follow patch 2.4.3 references; individual talents are not listed here, so confirm exact talents in-game or in a patch 2.4.3 reference before spending points. Every build figure in the new sections above comes from this page’s own planner, quoted exactly as displayed for the splits and levels probed, and no talent, rank, or prerequisite beyond those the page itself states is claimed. The planner is a tool for shaping a points plan; the game itself is where the plan becomes a build, and the game’s own talent display is the final authority on whether a talent can be taken.

A checklist before you spend points in-game

Work through this checklist in-game, with the build code in hand, because the planner’s checks end where the game’s checks begin. First, confirm the class and level on the planner match the character you will play, because a build code for one class at one level does not transfer to another. Second, confirm the budget line: points spent equal to or below level minus 9, with remaining points at zero or above, never negative. Third, confirm each tree’s tier line against the ladder: the points in that tree alone, not points across trees, must reach the tier whose talents you intend to take. Fourth, confirm the 41-point talent line if your build claims one: 41 points in that tree, no more and no less as a minimum, and a total that still fits the budget with the other trees’ points included. Fifth, take the plan into the game or a patch 2.4.3 reference and check every individual talent’s prerequisites and ranks against the points the plan allocates, because the planner does not check them. Sixth, if you play on a server with changed rules, check that server’s rules against the plan before spending anything. A plan that passes all six checks is ready to spend; a plan that fails any one of them should be revised on the planner first, because points spent in-game are harder to revise than points moved on a planner.

Depth against breadth: choosing a shape, not just a split

Every TBC build is a choice between depth and breadth, and the planner’s three probed shapes make the choice visible in numbers rather than in slogans. Depth, the 41 / 20 / 0 shape, buys the bottom row of one tree and a respectable second tree, at the cost of nothing in the third. Breadth, the 21 / 20 / 20 shape, buys the fifth row of every tree, at the cost of no bottom row anywhere. Total commitment, the 61 / 0 / 0 shape, buys everything one tree can offer, including its 41-point talent, at the cost of nothing anywhere else. The three shapes spend the same 61 points, leave the same 0 remaining, and are all legal, yet they play differently in every way that matters, because the talents in the rows they unlock differ. The planner cannot tell you which shape suits a role, a group, or a play style, because it does not list talents, and that is not a gap to be filled by guessing: it is the boundary between a points planner and a talent guide, and the choice of shape should be made with a talent reference open beside the planner, not from the planner alone.

Within any shape, the order in which points are spent while levelling matters as much as the final split, because tiers gate rows progressively. A final split of 41 / 20 / 0 cannot be played at level 30, when the budget is only 21 points, and a levelling path that spends early points in a tree whose later rows are the goal will reach those rows sooner than a path that spreads points evenly from the start. Plan the final split on the planner, then plan a levelling path toward it, adding points to the tree whose next tier matters most at each stage, and re-checking the budget at each level, because a path that looks efficient at 70 can be unplayable at 40 if it assumes tiers that the lower budget cannot yet reach. The planner’s level control exists for exactly that exercise: set the level, set the points affordable at that level, and watch the tiers and the remaining points together, level by level, until the final split is reached.

New guide: WoW TBC Talent Builds Explained: Burning Crusade Trees and Leveling

The Burning Crusade changed the talent system without replacing it.

One talent point per level from level 10 to level 70, for 61 points in total. A level-70 character has 61 points; a character at level 61, fresh from Classic content, has 52. The full guide, WoW TBC Talent Builds Explained: Burning Crusade Trees and Leveling, works through the method in detail, with worked examples and the cases that most often go wrong.

Frequently asked questions

More calculators