Permanent progression guide
How to plan the Pass the Fear team talent tree
The team tree turns 50 talent records into 39 visible nodes because higher ranks are merged into their parent node. It is a shared progression system, separate from the five personal upgrade choices made by each hunter.
A useful route is not simply the shortest path to an impressive endpoint. It should improve the statistics or mechanics your current build actually uses while respecting prerequisites and the limited point budget.
Keep team talents and hunter upgrades separate
Team points are spent in one connected permanent network. Hunter upgrades belong to the selected character, unlock with character level, and allow one choice per row. Planning them as two layers prevents a personal skill choice from being mistaken for a team-tree prerequisite.
- Use the team tree for shared, persistent route planning.
- Use the character profile or Build Planner for the hunter's level 2–6 choices.
Understand prerequisites, ranks, and refunds
A child becomes available after a connected parent reaches its maximum rank. A node with a second rank consumes a point for each rank, and a learned parent cannot be refunded while an active child still depends on it.
- Count every rank along the route, not only the number of visible circles.
- Remove dependent children first when revising a branch, or reset the tree to compare from a clean state.
Judge the whole route, not only its endpoint
Work backward from the build problem you want to solve, then inspect every node required to reach the target. Two endpoints can look similar while their path costs and intermediate benefits fit very different weapons or hunter skills.
- Prioritize channels your build can keep active rather than bonuses that require an unused mechanic.
- Compare complete routes with the same point budget before deciding which one is more efficient for that build.