Runes are easy to misread because they often look like permanent value. Permanent does not automatically mean urgent. A rune should be prioritized when it changes the route you can farm, the hero pattern you can support, or the consistency of a build you already use. Otherwise it may be a good upgrade that is still not the next upgrade.

Use the Rune page as a priority board. Match the effect to your hero problem, test the route impact, and spend resources on the rune that changes the next session.

Match rune type to the current bottleneck

Start by naming the bottleneck. If a route is slow because enemies survive too long, damage support can matter. If the route fails because the hero is fragile, survival or consistency can matter more. If the hero clears normal waves quickly but loses time at bosses, a rune that improves boss handling may be better than a general farming bonus.

Use the Rune page to separate effects into records you can test. Pair those records with hero pages and farming results. One rune may support a hero you are not using. Another may add a smaller effect to today's target route and deserve the next upgrade slot.

Separate account value from immediate value

Some runes are good because they help many future builds. Others are good because they solve a problem immediately. Both are valid, but they answer different questions. Account-value runes are excellent when you are between progression walls. Immediate-value runes are better when one current route is blocking your next level, material, or gear source.

Ask whether the rune changes your next hour of play with the current build, then test it on that route before spending. If it does, it is a short-term priority. If it does not, decide whether you are intentionally investing in long-term account strength. What hurts progression is pretending a long-term upgrade will fix an immediate route problem when it will not.

  • Immediate value: changes the current farm or boss route.
  • Account value: supports several future heroes or routes.
  • Low priority: looks strong but does not affect any planned route.

Use runes with pets and gear, not in isolation

Support pieces change rune value. Gear can solve the same problem and make a rune redundant. A pet can strengthen the hero pattern the rune supports. Check Heroes, Gear, Pets, and Farm before you lock a rune priority.

When a rune looks close to another option, test it against a concrete route. If the route's clear time, failure rate, or boss phase does not improve, the rune may be a future upgrade rather than a present priority. Use route outcome as the tie-breaker; it turns vague effect text into a result you can compare.

Check overlap when a rune has attractive wording but shares the same job as gear or pet support. If gear already fixes survival, a defensive rune may add little to the next farm. If a pet already smooths boss timing, a rune that helps normal waves may become the better complement. Read the rune as one piece of a support stack, then return to clear-time data. The right priority is the combination that moves the route, not the isolated effect that sounds strongest.

Limitations and update notes

Rune records describe effects, but they cannot fully predict build feel. Small wording differences can matter in live play, and patches can change values or interactions. Use the page as a structured reference, then confirm with the hero and route you actually use.

Checked against site data on June 19, 2026. Send rune corrections with the rune name, visible effect text, hero, tested route, game version, and the difference you saw. Those details separate a data issue from a build expectation and give future generated pages a cleaner source.

Do not update rune priority every time a wording line feels interesting. Update it when a route, hero, or account goal changes. That rhythm keeps permanent upgrades from crowding out immediate needs. If the same rune remains on the list for several sessions without affecting a tested route, label it as long-term value and choose a more active bottleneck for the next farm. Permanent value is still valuable, but it should not hide the current constraint or replace a route test. Use that label to protect focused farming time from attractive but inactive upgrades.

For expensive rune upgrades, write the runner-up in the same note. If the chosen rune fails to improve the route, you already know which effect to test next and why. That record also stops you from reopening the same comparison after every small farm. Add the hero and route beside it.