CURRENT DATA BOUNDARY
Atlas tracks v1.00.28. The current official hotfix does not publish a revised Rune Tree or node values, so this page provides a repeatable planning method rather than a fabricated universal tree.
Start with three answers
What ends the run?Wave time, a hard target, or a survival failure?
What stays fixed?Use the same stage and build for the comparison.
What changes once?Move a relevant point before changing unrelated gear.
What proves it?Clear time, completion rate or an exact failure point.
Goal-first route map
| IF THE WALL IS… | FIRST PRIORITY | MEASURE WITH |
|---|---|---|
| Slow repeated clears | Repeatable wave-clear value | Several complete clear times on the same route |
| A boss check | Single-target reliability | Completion plus time, not one peak hit |
| Late-run deaths | Survival at the actual failure point | Stable completion rate |
| Resource shortfall | Only a verified effect tied to the needed resource | Resource per timed session |
Route record template
- Version: record the client patch, currently v1.00.28.
- Target: name the stage, difficulty and activity.
- Setup: note the party, key gear assumptions and the Rune change.
- Result: record more than one clear, then say whether the route solved the stated wall.
Source and connected tests
Rune Tree FAQ
Is there one best Rune Tree?
No. The best path changes when the active bottleneck changes. A screenshot without a version, stage and result is not enough context to copy.
When should I reset or change a route?
Revisit it after a patch, a meaningful gear change, a new stage wall or a measured result that shows the previous goal is solved.