Rune Planner & Atlas
This page expands the homepage rune tree ideas into a fuller planner and atlas. It is organized around route judgment first, then icon groups and lane comparisons.
The current page organizes rune icons, categories, and progression directions into five working groups: combat, economy, chest, offline, and utility. It can expand further without breaking the route-first reading flow.
How To Read Runes
The easiest way to misbuild runes is to treat every node as something that will 'eventually be useful.' A better approach is to decide whether you are currently missing survival, efficiency, boss killing, or offline recovery.
Do not touch too many fancy routes at the start. Build EXP, baseline damage, and armor first, then look at skill slots and utility picks.
This is the phase where players most often spread points too thin. A better method is to connect Gold, Chest, and speed nodes into one route instead of leveling every value node evenly.
Boss-related nodes are not something you default into for everyday play. First decide whether the wall is survivability, damage, or rhythm, then add Attack %, Armor %, or boss chest lines.
If your play rhythm is already offline-heavy, do not use online speed-farm routes as the standard. Close the offline reward loop first, then return to comfort and efficiency.
Field Notes
Players usually lose more value by mixing too many half-built lanes than by choosing the wrong single rune. This page now leans harder into the idea that a rune plan should serve one route at a time.
The rune tree only becomes clear when you stop asking whether each node is "good" in the abstract and start asking what your account actually needs more right now: safer clearing, better return per run, cleaner boss pressure, or stronger offline recovery.
`Additional Gold`, chest drops, and speed lines become much easier to evaluate once the same map can already be cleared for a long time without manual rescue.
Attack %, armor %, and pressure-map nodes are strong, but only when the account is clearly solving a wall instead of doing ordinary farming.
Skill slots, stash pages, offline unlocks, and comfort nodes matter most after the account already knows what its main route is trying to optimize.
Rune Explorer
This section is designed to answer two practical questions first: which type of rune should I level first, and who is this node best for? Filter by category, then by lane, then by hero focus instead of mixing the entire rune pool together.
Planner Lanes
This section extends the homepage idea of the rune planner. Instead of drawing every node into a tree first, it uses lane cards to answer the four questions players ask most: what to level first for starter play, what to level for farming, what to add before bosses, and when offline or utility nodes start to matter.
Rune Atlas
The different rune icon groups are placed together here so players can build quick visual memory for what each category actually does. When the full database arrives, this area can expand into a paginated categorized icon atlas.
Expansion Notes
The current `Runes` page solves presentation and filtering first. To turn it into a mature database, the next additions should center on node relationships, unlock costs, and hero-build linkages.
Node Graph
Build Pairing
Progression Math
