Start on Heroes when a build feels unclear. Gear, runes, pets, and farming routes all depend on what the hero is trying to do. A hero with reliable area damage wants different support from a hero that wins through single-target burst, and a hero with fragile early clears may need safer routing before raw damage becomes the priority.

Read the hero page like a build checklist. Skill shape points you toward gear, passive value points you toward route tests, and stat needs tell you whether runes or pets should come next. Pick the next farming decision from that chain.

Read skill shape before item lists

A hero's active skill shape changes how you should read every other page. A skill that hits wide groups can value clear speed and cooldown support more than pure single-hit damage. A skill that excels at bosses may want routes where boss time is the bottleneck. If you start with gear before understanding the skill, you may chase stats that look strong but do not solve the hero's real problem.

Use hero records to decide whether the build needs damage, uptime, survival, or route control. Once that need is clear, you can open Gear, Runes, Pets, and Farm with a signal in mind instead of browsing every possible upgrade.

Passive nodes are route decisions

Passive nodes are often read as small bonuses, but they can change route choice. A passive that improves consistency may be worth more than a larger number if it turns a failing route into a stable farm. A passive that only improves already-easy content may look efficient while doing little for the next progression wall.

When comparing passives, connect them to a concrete test. Does this node reduce clear time on the current EXP route? Does it make a Gold route safer? Does it help the hero survive a stage box route that contains better gear sources? If the answer is not tied to a route, the upgrade may be less urgent than it appears.

  • Use hero pages to define the build problem.
  • Use gear, runes, and pets to solve that problem.
  • Use the farming optimizer to test whether the solution changed route speed.

Choose support pages in the right order

Start on Heroes, move to Gear for the weak slot, check Runes for permanent support, check Pets for companion value, then return to Farm and retest the route. Use each page for one build question. Reading them in that order keeps you from chasing upgrades that do not move the route.

Do not be afraid to stop early. If the hero's current issue is survival, it may be wasteful to spend a session comparing damage gear. If the issue is boss time, a pet or rune that improves boss handling may outperform a general farming stat. Keep the hero context beside the choice so the upgrade stays tied to the route.

Use one hero page as the anchor when the rest of the account feels noisy. Pick the hero you are actively pushing, identify the route that hero is supposed to improve, and then open only the support pages that answer that route problem. This reduces false priorities. A rune that helps a future hero, a pet that looks rare, or a weapon with a larger number can all be valid later while still being distractions from the hero you are actually farming with today.

Limitations and update checks

Hero records can describe skills, passives, and stats, but they cannot know your exact timing, input comfort, or tolerance for risky routes. A hero that looks strong in data can still feel bad if your route, gear, or pet support does not match the skill pattern. Treat the page as a structured starting point, then validate the build in the route you actually farm.

Checked against site data on June 19, 2026. Report outdated hero skills, passives, or stat displays with the hero name, visible value, game version, and the live change you saw. A good correction updates the hero data source, so detail pages and build guidance stay aligned after rebuilds.

For practical use, revisit the hero page after every major support change. A new pet, rune, or weapon can move the hero from survival-limited to speed-limited, which means the next correct page may change. The page is most useful as a recurring planning checkpoint, not a one-time lookup before copying a build. If the build feels different, update the route test too.

Keep that note next to the hero name so future checks start from the same build and route.

Add the last farm target to the note.