I am trying to make a game-data discussion useful without turning a catalog record into a promise about a player's next run.

The evidence chain I would keep together is:

- the exact obtainable Gear variant, including rarity or level when the record distinguishes it

- the named box or chest source

- the stage route and difficulty label

- the scenario attached to the published value: Base, Hunter, Slayer, or combined

- the release or date scope used when the catalog record was checked

Player observations should stay in a separate layer: clear time, build, party, route preference, and what happened in a small sample of runs. A catalog relationship can show where an item is listed as a drop, but it cannot identify one universally best farm for every account, and a displayed percentage is not a guarantee. drop chance calculator

For a game wiki or tool discussion, which fields make a drop-route note auditable enough to reuse: exact variant, named box, stage, difficulty, scenario, release scope, source screenshot, or a personally tested route?

The catalog may be incomplete, delayed, or wrong, so I would rather expose the source chain and uncertainty than hide them behind a single ranking.