What the official Mayhem page supports
2K describes Mayhem as additional challenge in exchange for better loot and says weapon stats improve at higher levels. That supports using Mayhem as relevant context. It does not support a universal legendary multiplier, boss-specific rate, anointment pool size, or route time, so this hub does not publish those as facts.
Minimum evidence for a useful scenario
- Name the exact target, source, game mode, Mayhem setting, event/hotfix state, platform, and date.
- Attach a public source or a clearly labeled personal sample to the probability input.
- Separate “any copy” from a conditional part or roll target.
- Measure a complete repeatable cycle rather than boss combat alone.
- Compare routes with the same target definition and source quality.
Keep probability evidence separate from route timing
A published or extracted probability describes the loot event; your stopwatch describes how quickly your build repeats it. Store both with the scenario instead of calling one route universally best. A patch, event, difficulty setting, party state, or target definition can invalidate the probability while a build or hardware change can invalidate the timing.
Compare effective targets per hour
For the same target definition, compare 3600 × effective_target_chance / full_cycle_seconds. If a desired part or roll is conditional on the item dropping, multiply only after documenting that conditional chance. When a rate comes from a personal sample, keep successes and eligible attempts beside the point estimate; a small sample should not be presented with false precision.