Name the resource blocking your next upgrade, then time two nearby stages with the same party. Enter average run time, success rate, and target yield; keep the route with higher stable target returns per hour.
Start with the blocked upgrade
Write the next purchase in one line, then the one missing resource. Total loot is noise if it does not move that purchase closer.
Run a controlled two-stage test
- Keep party and settings fixed.
- Include reset time in average run time.
- Record a complete, stable sample.
- Compare target units per hour, not loot per clear.
How to use the 420-second experiment window
Player discussion inspired a standardized 420-second test, but this is not an official chest mechanic or drop guarantee. It only gives both stages the same observation window; current-client samples remain decisive.
When to retest
Retest after a meaningful damage upgrade, survival milestone, party change, or patch. Farming efficiency is contextual; an old result is not permanent.
Official information and cross-checked community guidance. We avoid unsupported percentages and mark exact data as pending when it has not been independently verified.
See our source method →Turn this guide into three next steps.
Share your goal and bottleneck. The planner will rank a route and show why it fits.
Build my plan →