How to use monster data for route decisions
Use the monster index after you know the reward or route you want to test. Check whether a stage stays comfortable across repeat clears, then verify the reward table.
How to use
Start from the route you are considering, then search the enemies that appear there. Compare HP, attack, role, boss appearances, and reward lines. A route with strong loot can still waste time if the enemy mix slows your main skill, forces movement, or creates failures that the farming optimizer cannot see from clear time alone.
Use the filters to split normal monsters from bosses. Normal waves affect speed and attention cost. Boss routes affect failure risk and late-run delay. Open the best farm route link for a monster when you need to understand why a stage feels slow even after your gear looks strong enough on paper.
Example
If a target box points you toward a stage with a boss that causes long delays for your hero, check whether another stage offers the same box or a nearby reward pool. A slower boss phase can erase a drop-rate edge. The better route may be the one with fewer stalls, even if the loot table looks less impressive.
For a ranged build, compare enemies that close distance with enemies that stay in predictable positions. For a melee build, compare enemy HP and attack pressure. Write down the specific reason for a failed sample run: boss delay, wave spread, survival pressure, or bad side rewards.
Limitations
Use the monster page to check extracted stats and route relationships. You still need in-game tests for map layout, animation timing, projectile misses, crowd behavior, and your hero control. Some live patches may also change enemy behavior before the public data files get refreshed.
Read HP, attack, rewards, and role together before you choose a long farm. A boss-heavy route can still be correct when the target reward is unique or when you plan a short test, but a long farm needs clear-time proof.
Update notes
Maintainers reviewed this guide on June 20, 2026. The current English manifest records 61 monsters, 494 normal stage appearances, and 120 boss appearances from source version 1.00.05. You first see the static index, then the browser can fetch the larger monster dataset for search and filtering.
Report stale enemy data with the monster name, route, observed stat or behavior, and game version. Update the generated monster files so the monster browser, farm routing, and related stage pages stay consistent.