Lesson 7 of 10 · Advanced · talent planning
Plan Talent Branches, Gates, and Prerequisites
Spend talent points in dependency order, respect weapon branches and exclusive choices, and evaluate every node through an action you really use.
Updated 2026-08-038 min readA talent tree is a rule graph
Open the talent planner and select the class and branch you actually intend to play. Lines, rank limits, level gates, point thresholds, prerequisites, and exclusive choices define whether a plan exists. Reading one endpoint in isolation hides the points needed to reach it and the alternatives it prevents.
Work backward from the important node
Choose one endpoint that changes a real action, trace every dependency back to the branch start, then spend in legal order. Count required ranks before optional bonuses. If two nodes are exclusive, treat the relationship as a hard constraint even when respec is available; a saved plan must be valid at every restored step.
Connect wording to an action you perform
For each node, name the skill, weapon action, defensive event, or resource condition it affects and how often your route creates that condition. Compare the selected talents with the active bar in the weapon skill guide. A large conditional benefit that almost never activates can be less useful than a modest node that supports the main sequence every fight.
Save a stable core and a test branch
Build one core path with confirmed requirements, then use remaining points to test a single variation in the loadout simulator. After a patch, reopen the planner rather than trusting an old screenshot: a node can move, change its gate, or disappear while the shared image still circulates. The current selectable tree and a repeatable result outrank memory.