Start with the bottleneck you can observe. Focus a short route around damage, survival, gold, experience, drops, inventory, party, or movement; verify exact costs and prerequisites in the current game before committing.
What the Rune Tree changes
Community reference sets consistently describe a broad progression tree with families that support damage, survival, resources, drops, inventory, party, and movement. The important decision is which job your next route needs to do.
Pick a direction
Use the failure you can see: stable but slow runs suggest a damage test; repeated deaths suggest survival; a named purchase blocked by gold or experience suggests a resource path; interrupted long runs can make capacity relevant.
Compare two priority routes →Avoid scattered spending
Spreading investment across unrelated jobs makes results difficult to evaluate. A focused short route creates a clearer before-and-after comparison and a cleaner share link when you ask for help.
Costs and prerequisites
Exact node costs, levels, and prerequisite links require independent in-game validation. Until that dataset is complete, TBH Planner shows rune families and decision notes rather than copying another site's reconstructed database.
When to change direction
Recheck after a class change, a major item, a new skill interaction, a progression stall, or a game patch. Do not keep following a saved route just because it was once useful.
Official information and cross-checked community guidance. We avoid unsupported percentages and mark exact data as pending when it has not been independently verified.
See our source method →Turn this guide into three next steps.
Share your goal and bottleneck. The planner will rank a route and show why it fits.
Build my plan →