Build planners
Talents, Weapon Branches, and Prerequisites Explained
Understand current talent-tree membership, weapon-specific branches, point gates, prerequisites, and mutually exclusive choices without creating an illegal plan.
Updated 2026-08-017 min readThe tree is a rule graph
A talent tree is not a flat list of bonuses. Nodes can require earlier nodes, a character level, a point threshold, or membership in a particular branch. Some choices are mutually exclusive. Read the connection lines and lock states before judging an isolated description; a powerful endpoint may require several choices that change the total cost and the rest of the build.
The current talent interface contains 241 selectable nodes across 84 branch layouts. Other talent names may still appear in old posts or screenshots, but a name alone does not prove that the choice is available now. Build only with nodes that appear in the current class tree.
Begin with the weapon you will actually equip
Current gameplay shows class trees organized around weapon and archetype branches. A Mercenary using Hammer should not plan as if Sword and Shield nodes automatically apply, and a Withered Knight should distinguish Greatsword from Polearm and Shield. First select the weapon family, then trace the talents whose wording and prerequisites match that family.
Do not infer that owning two weapon families means every branch can operate simultaneously in a raid. Player discussions conflict about switching and cross-branch behavior. Until the current build is reproduced in-game, use only combinations the talent interface accepts and avoid publishing a shared plan that relies on an unconfirmed swap rule.
Spend in dependency order
Start at the desired endpoint and work backward through every prerequisite. Add the required nodes and ranks before counting optional points. Then check level and point gates. This reverse walk prevents a common planning error: spending the displayed budget on attractive endpoints while omitting the nodes that make them legal.
When two branches or nodes are marked as mutually exclusive, treat that relationship as a hard constraint, not a suggestion. Resetting choices in the interface may be allowed, but a planner should never restore a saved state that contains both sides. Reversible choices still need to be valid at every moment they are applied.
Evaluate the talent in a real action loop
Translate each chosen talent into an action: the skill it changes, the condition that activates it, and the moment it matters. A conditional benefit that never occurs in your route is not free power. Compare talents by how often you can create their condition without exposing yourself, not only by the strongest possible outcome.
Be careful with descriptions whose values change by rank or condition. Do not replace a value you cannot confirm with a guess. Check the number shown in the current game and test the actual result before treating it as an exact final statistic.
Keep a legal fallback plan
Save one core path that uses only confirmed prerequisites and the weapon you consistently carry. Use remaining points to test a single branch change. This produces a stable comparison and makes it easier to notice whether a result came from the new talent, different equipment, or a changed route.
After a patch, re-open the in-game tree before reusing a shared build. A node may move, change its requirement, or leave the current tree even while an old description still circulates online. The selectable interface and a repeatable gameplay result take priority over an older guide.