Make 21 baseline talent points answer one question.

At level 30, the baseline calculator gives you 21 points. Start with the outcome you want to test, then decide which earlier choices support it.

Open your class at level 30

These links open empty, level-30 plans. They are not recommended builds. All nine classes have their existing three-tree calculator, real talent icons, hover details and shareable links.

Understand the baseline budget

The model grants one point at each level from 10 onward, so level 30 has 30 minus 9: 21 points. The first row has no earlier-tier requirement. Later rows need five more points in earlier rows of the same tree for each tier. A linked prerequisite must also be fully ranked.

For a fifth-row talent, the model needs 20 earlier points in its tree before the next point can reach that row. Spending early points in another tree changes what is reachable with the remaining budget. This is a structural planning constraint, not a claim that every fifth-row talent is the best choice.

Compare two plans around one problem

1. Write the activity you care about: solo questing, a group role or a specific comparison.
2. Read the talents that could affect that activity, including ranks and prerequisites.
3. Save a focused plan and a second plan with one deliberate tradeoff.
4. Test under comparable conditions and note what became easier or harder.

If the first plan reaches deeper into one tree, ask what you give up in the others. If the second spreads points, ask whether those early benefits matter often enough in your actual session. Without observations, the two links are hypotheses rather than evidence.

Check the dataset before trusting a tooltip

The calculator's community dataset is version 1.60.1.70235, collected October 7. It predates the October 8 patch. Changes such as Druid Natural Instinct and Warrior Deep Wounds prerequisites mean the snapshot can differ from the current client. Confirm affected names, effects and links in-game before allocating live points.

We keep the snapshot date visible rather than relabeling old data as a fully revalidated build. The official class change log is the current patch reference. A successful saved link shows that a plan is valid for our model, not that the client has been checked against it.

Legacy can change the available budget

The baseline calculator does not model Legacy talent-point timing. Include your actual Legacy setup when sharing a test, and use the Legacy worksheet to keep the two systems separate. Do not compare a baseline plan with a Legacy-enabled character and attribute every difference to class balance.

A useful build note fits beside the link

Add your level, role, dataset or patch date, Legacy choices and the reason for the tradeoff. “I wanted fewer recovery stops during solo objectives” gives another player a testable context. “Best build” without a method does not.

The session planner opens the same calculator at your chosen level. Save both plans before testing; keeping an unchanged reference makes the next comparison easier.