1. Start with the official boundary
2K's Mayhem 2.0 overview establishes a qualitative relationship: higher challenge provides better loot, and higher Mayhem improves dropped weapon stats. It also describes level-gated legendary weapons in that update. It does not publish a universal boss/drop multiplier or per-item probability table.
2. Define the target before collecting a rate
“A legendary,” “one named item,” and “that item with a desired part or roll” are different events. Record:
- item and variant definition;
- enemy, chest, mission, event, or route;
- Normal/TVHM, Mayhem setting, platform, DLC and active event/hotfix state;
- date and source URL or personal-session identifier.
3. Grade the probability input
- Published mechanic or table: quote its exact scope and date.
- Extracted game data: identify the project, file/version, extraction method, and mapping from record to target.
- Observed sample: report successes, eligible attempts, exclusions, collection window, and uncertainty.
- What-if value: label it as a scenario; do not describe it as the game's rate.
A claim of “community verified” without a public dataset, version, and selection rule is not evidence.
4. Separate the target drop from its conditional variant
If a target item drops with chance p and a desired part or roll appears with conditional chancev, the combined chance is p × v only when those inputs and their conditioning are valid. Do not divide by an assumed pool size unless the outcomes and weights are actually established.
5. Measure the repeatable cycle
Start the timer when one attempt begins and stop when the next attempt is ready. Include combat, immune phases, travel, loading, looting, menus, save/quit or reset steps, and failed attempts. Use a median for a “typical” route comparison and keep the raw times if you want to examine variability.
6. Compare like with like
Expected targets per hour are 3600 × p / seconds_per_cycle. A higher Mayhem label does not win by itself; a route wins the stated scenario only when its supported effective target probability per unit time is higher. Compare URLs built from the same target definition and evidence standard.
7. Keep a real session log
date,platform,mode,mayhem,target,source,attempts,target_drops,cycle_seconds,event_state,source_url,notes YYYY-MM-DD,PC,TVHM,11,item and variant,enemy or route,0,0,0,none,URL or personal sample,record actual observations
This is an empty schema, not claimed player data. Do not seed it with invented rows to make the site look tested.
Use the calculator
Enter the supported rate and your measured cycle in the Borderlands 3 Drop Scenario Calculator, then save its URL beside the evidence note.