Use stage box tables to turn loot questions into visible lists. Read them carefully. Seeing a target in a table does not prove the route is efficient, and missing a target in one box does not prove the item has no other source. Good route planning starts with the table claim, then checks whether that claim changes the decision.

Bad farms start from repeatable habits: you ignore the level band, chase a rare target in a wide pool, compare raw drops without clear time, or read fan-maintained data like a live server feed. Fix those habits before you commit to a route.

Mistake one: reading presence as efficiency

Read a drop table as a source claim: the wiki currently associates a reward with a source. You still have to decide whether that source is the best farm. A stage box may contain the target, but it can also contain many irrelevant rewards, require a slow route, or sit in a level band where your current hero suffers a penalty. Presence is only the start of the comparison.

Before choosing a route, write down your clear count per hour and the secondary rewards you will keep. A box with a strong target and useless side drops can waste time. A cleaner box with a lower target rate can beat it once you count clear speed and side rewards.

Mistake two: ignoring level band and clear speed

A later box usually looks attractive because its reward names or levels feel stronger. That does not mean it should be farmed now. If the stage takes much longer, fails more often, or triggers an EXP penalty pattern that makes the session less efficient, the later box may be a progression target rather than a current farm.

Use stage boxes together with the farming optimizer. List candidate sources from the table, then check whether your clear time supports them. This two-step workflow is safer than starting from a rare item name and forcing the hardest listed source into your plan.

  • Use the table for source discovery.
  • Use clear time for route ranking.
  • Use secondary rewards to break close ties.

Mistake three: overreacting to small samples

Rare rewards are noisy. A player can run a stage many times and still see streaks that feel unfair. That does not automatically mean the table is wrong. It means the table should be used for planning expectations, not for judging a short session emotionally. If a reward is rare, track enough clears before drawing a conclusion.

A correction report works better when it includes the exact box, stage, target item, number of clears, visible game version, and whether the route was run before or after a patch. This lets maintainers compare a possible data issue with ordinary randomness.

Write the sample purpose before you start. A short sample checks comfort; it cannot prove a rare drop rate. A longer sample shows whether side rewards help your account, but it still may miss a rare item. Decide whether you are testing comfort, source presence, side reward quality, or data drift. Each question needs a different sample size.

Use a small log for any target you plan to farm beyond a quick test: route, box, hero, clear time, keepable side drops, and reason for stopping. Ten messy clears with changed builds teach less than five clean clears with the same setup. If the route feels bad, mark the exact cause: boss delay, wave density, failure risk, or empty side drops. That note lets you compare the box with another source later without rebuilding the whole decision from memory. Keep the log beside the farming optimizer numbers, because reward tables and clear-time tests answer different parts of the same route question.

Write the box name before testing.

Patch-sensitive rewards need extra caution

Chest rules, accessory probabilities, market behavior, and invalid-item cleanup have all appeared in recent official update contexts. A drop table can be structurally correct while the live service is temporarily changing how rewards are delivered or verified. During those windows, read the table with the update notes in mind.

Separate stable database facts from live-service timing. Use the wiki to narrow possible sources, then use current game behavior to decide whether today is the right day to farm that source for a long session.

After an update changes chest timing or server validation, use the table to identify box membership and wait for fresh clears before you judge efficiency. Compare nearby sources during that window. Keep a short note for any route you leave on the list, then revisit it after the next update note or a clean sample batch.