How to plan rune upgrades without wasting resources
Use the rune page as a long-term upgrade planner. Runes cost progression resources, so the best next rune should connect to a route, hero, or account bottleneck you can test.
How to use
Start by naming the bottleneck. Choose chest runes when storage or auto-open timing slows your loop. Choose EXP and Gold runes when account growth limits the next upgrade. Choose Hero and Combat runes when damage, armor, attack speed, or movement changes the route itself. Use Slots and Offline runes for account comfort, but give them a clear job.
Use tree view when you care about prerequisites, then switch to list view for cost and effect comparison. Search by stat label when you are solving a problem. For example, search for chest capacity, EXP, Gold, attack damage, or offline reward before you read the whole tree from left to right.
Example
If stage boss chests pile up while you farm, compare chest capacity, auto-open unlocks, and auto-open timer runes before spending on raw damage. If the route fails at the boss, compare hero damage and survival support. The correct rune is the one that changes the next route test, not the one with the largest permanent-looking number.
For an expensive choice, write the runner-up beside the chosen rune. Include the hero, route, cost, and expected result. If the route does not improve after the upgrade, you already know which effect to test next and why you rejected it before.
Limitations
The rune page does not read your owned rune levels, currency balance, or current build. Duplicate rune names can appear in different branches, so read the stat label, category, prerequisite, and cost before deciding. Test the route after the upgrade if you need clear-time proof.
Permanent value can distract from the current constraint. A useful rune may belong on the long-term list if it does not affect today's hero or farm. Keep a separate note for future-value runes so they do not crowd out the next route fix.
Update notes
Maintainers reviewed this guide on June 20, 2026. The generated rune dataset records 197 runes, 8 categories, 663 total levels, and source version 1.00.05. The manifest also tracks total cost and category counts from the current extracted rune files.
Report rune issues with the rune name, category, stat label, level, cost, prerequisite, and game version. Update the generated rune data so tree view, list view, search, and future guide references read from the same source.