Reference
Data & methodology
Every value on this site has a stated origin. This page lists them, with the rules applied and the known gaps.
Sources
- Bungie Manifest
- Dungeon, variant and modifier definitions. Dungeons are identified by activity type rather than activity mode, because the Manifest's mode tags miss newer variants and include at least one raid.
- Bungie API
- Player search, profiles, per-character activity history (dungeon mode), Post Game Carnage Reports, and character activity listings (the modifiers currently applied to each dungeon variant). Requests are made server-side with a private key, cached, and retried with backoff when Bungie rate limits.
- Calculated
- Classifications, personal bests, medians and counts derived from the sources above. Sample sizes are shown alongside derived values.
- Community / reviewed
- Reserved for evidence submissions and moderator review (e.g. speedrun verification). Not yet enabled.
Run classification
- Full clear
- Completed, and the carnage report states the activity was started from the beginning. Reports without that flag are treated as unknown, never assumed fresh.
- Solo
- Full clear with exactly one Bungie account anywhere in the report.
- Flawless
- Full clear with zero deaths summed across every entry, including players who left. Missing death counts disqualify the run.
- Solo flawless
- Both of the above. A one-player report alone is not enough.
- Times
- Only full clears produce times. Checkpoint completions count as completions but never as personal bests.
Rotations
The Manifest defines activities and the modifiers they can carry, not which were active in a given week. The current week is read from the live activity listing of a public reference account, which carries each variant's applied modifiers. Bungie's public milestones were checked and do not list dungeons. Bungie offers no historical schedule, so rotation history only grows forward from when snapshots are captured. Each snapshot is stored append-only with its retrieval time.
Encounter damage
Bungie's carnage reports are activity-level: per-player kills, deaths, durations and weapon kill counts, with no encounter boundaries and no damage values. Encounter damage history, DPS and damage leaderboards therefore cannot be produced from official data. The data model and calculations (contribution share only when totals reconcile, DPS only with a known duration, comparisons only between the same encounter, variant and fireteam size) are implemented and tested, so a permitted, verifiable source could be added later without changing the rules. Until then these sections stay empty.
Known limitations
- Private Bungie.net privacy settings block activity history.
- Profiles classify the most recent completions first; very long histories are partially classified and say so.
- Activities whose hash is missing from the current Manifest are kept and shown as unmapped.
- Leaderboards and dungeon records only include runs collected from Guardian profiles viewed on this site (and their fireteams), so they are a growing sample, not every run ever played.
