How to read the farming results
Use this page to build a practical farming shortlist. The optimizer compares stages from the current stage dataset, then estimates EXP or Gold per hour from your hero level and your own clear-time samples.
How to use
Start with the hero level you are farming today. Time stage 1-1 and the highest route you can clear with the same hero, gear, pet, rune, and skill setup. Record three clean clears for each route and use the median time. With those two timings, you give the optimizer a speed curve and avoid treating a late route and an early route as equal.
Choose EXP when you need the next hero level, unlock, or route band. Choose Gold when you need upgrade income. Read the first few results as a testing list. Open the top routes, compare reward rate, penalty, and clear time, then run a short in-game sample before a long session.
Example
A level 32 hero may clear 1-1 in 9 seconds and a high route in 52 seconds. The late route can still lose to a faster middle route once boss durability and over-level EXP penalty enter the estimate. In that case, the safer middle route can earn more progress per hour even though the reward per clear looks smaller.
Keep two notes if the best EXP and Gold routes split. Use the EXP route during active play, then use the Gold route when you want upgrade income with less attention. After a weapon upgrade, pet swap, or rune change, retime the high route. Old timings can point the optimizer at the wrong target.
Limitations
The optimizer cannot see your exact damage cycle, missed attacks, disconnects, event bonuses, temporary buffs, chest RNG, or server reward changes. It also cannot promise any stage box drop. Read the estimate as local game data plus your entered clear times; an awkward enemy mix can feel worse than the number suggests.
Treat routes within 5-10 percent of each other as candidates, not a verdict. Pick the route that you can repeat with fewer failures and less boss delay. A route with a lower estimate can still be the better farm when it protects the session from resets.
Update notes
Maintainers reviewed this guide on June 20, 2026. They use the generated stage manifest for the route count, difficulty list, max level, and source version above. After a stage-data rebuild, keep the same workflow and recheck rewards, penalties, and route counts against the new generated files.
Send corrections through the contact page with the stage, hero level, median clear time, game version, and visible reward result. Add route fixes to the stage data pipeline so the optimizer, stage pages, and sitemap-backed core pages stay aligned after the next rebuild.