1. Identify the exact reward opportunity
Write down the target, activity, encounter, date, character, and what the current in-game reward state says. Do not assume that every completion can award the target. Rotations, quest steps, checkpoints, and reward lockouts can change which clears are eligible.
2. Separate sourced mechanics from a scenario
A public source may confirm that protection exists without disclosing its numeric curve. Bungie's Eyes of Tomorrow explanation is a useful example: weekly account clears build protection and the design can reach a guarantee, but the article does not publish a base rate or increment. Entering “+2% per clear” would therefore be a hypothetical input, not a quote from that source.
Bungie: Eyes of Tomorrow bad-luck protection
3. Choose fixed or progressive math
- Fixed: use one rate for every confirmed future eligible attempt.
- Progressive: supply a base rate, increase timing, and cap as a clearly labeled scenario.
- Guaranteed: only add a hard boundary when a source establishes that boundary for the target.
Do not borrow Eyes of Tomorrow's documented protection concept for Vex Mythoclast or another target unless a source specifically supports the transfer.
4. Keep an eligible-attempt log
date,target,activity,encounter,character,eligible,result,source,note YYYY-MM-DD,target name,raid name,final encounter,Hunter,true,no drop,source URL,confirmed weekly chance YYYY-MM-DD,target name,raid name,checkpoint,Titan,unknown,no drop,,keep outside confirmed count
This is a blank schema, not claimed player data. An unknown row stays outside the confirmed count until the current activity rules establish eligibility.
5. Treat checkpoint and Spoils timing as personal measurements
Team formation, wipes, loading, checkpoint transfer, and encounter strategy can dominate time per attempt. Record your own start-to-ready-again duration instead of relying on a universal “Spoils per hour” or boss-clear benchmark. A simple time budget is planned attempts × measured minutes per attempt plus a buffer for group formation and failed runs.
6. Read the result conditionally
The calculator answers “what follows if these inputs are true?” It cannot answer “what is my hidden account chance?” A high cumulative number still permits a no-drop outcome unless the sourced mechanic includes a hard guarantee.
Use the scenario calculator
Enter the sourced or hypothetical values in the Destiny 2 Drop-Rate Scenario Calculator and save the generated URL beside your source note.