Build Routes & Comparisons
This page expands the featured homepage build cards into a full route library. The layout is built for comparison first: what the team is trying to do, where it fits, and why one route is safer or faster than another.
The goal here is not to force one universal build. It is to separate starter routes, farm routes, boss routes, and cheap validation routes so players can judge them against their own account state.
How To Pick A Build
Route names can look overwhelming, but for most players the useful question is simpler: what kind of setup should I use right now? Pick by goal first, then improve Gear, Runes, and Cube around it instead of chasing one slug blindly.
`Knight + Priest + Ranger` style safe setups fit this best. Do not start by copying endgame speed-farm or pure solo routes.
Instead of only reinforcing safe-push lines, this is where `Priest + Ranger + Sorcerer` style setups start making more sense.
`Solo Ranger Budget` style validation routes fit that goal. They are not meant to cover everything, but to answer whether a specific investment was worth making.
Endgame routes are benchmarks. At this stage the question is no longer 'can it clear' but 'can it clear faster and more reliably.' That is when Torment setups start to matter.
Reading Notes
The official feature list keeps combining class roles, gears, runes, Cube, stages, and idle loops because strong builds are really cross-system answers. This page now leans more visibly into that logic.
Strong build pages do not just rank compositions. They tell you which route solves slow clears, unstable pushing, boss walls, or budget testing most cleanly, and then hand you to the right Gear, Rune, and Stage page to finish the job.
`Knight + Priest + Ranger` style teams win because they keep the account alive and readable. Comparing them directly to endgame speed routes hides their real value.
Builds built for money, chests, or materials only become truly strong when they survive long sessions with good clear rhythm and low intervention.
When a composition only exists to pass one pressure wall, it should be evaluated as a swap tool instead of as the new default account identity.
Build Library
Start with route shells that are easy to compare side by side, then read them by phase, style, and hero focus. The point is to make route tradeoffs legible, not to bury the judgment behind raw labels.
Route Ladder
Reading routes by when you should switch into them is more useful than asking which one is strongest. This section focuses on when to move from safe-push teams into farm teams, when to test boss routes, and when solo routes are actually worth trying.
Hero Matrix
This is not a class encyclopedia. It exists purely to support build choices by showing what role each hero fits best and which routes match them naturally. It can later branch into Gear, Runes, and detailed skill pages.
Toolkit Stack
This section groups the skill and passive icons that are mentioned most often across the `builds` page into one shared vocabulary layer. Later it can be split into hero skill pages or passive detail pages.
