Skip to content
LDloadoutdex

Method · Provenance

Where every number came from

This is the ledger behind the site. Each published figure gets a source, an observation date and a confidence level, and anything still resting on one community page stays flagged as such. When a figure cannot be sourced, the page that wanted it says so instead of inventing one.

Updated 15 cited figures7 open verificationsNo unattributed claims

Cited figures

primary
Read from the rights holder or its own published document.
cross-checked
Two independent origins agree.
single tracker
One community page states it. Treat as reported, not settled.
single source
One page states it. Treat as reported, not settled.
editorial
Our own rule, not a fact about the game.
derived
Computed here from figures above it.
retracted
We published this and could not defend it. The row stays, because the mistake is the useful part.

How current each dataset is

Every dataset carries its own expiry rule, evaluated when the site builds. A page never goes dark over it and a build never fails over it: the dataset says on the page that it has aged. Tool pages show this badge themselves once a dataset leaves current.

Detection of the drift this table describes does not run here: the repository is the schedule, and a snapshot is refreshed by pnpm snapshot plus a commit, so every change to a published figure is reviewable. pnpm verify re-reads the live mirror and reports the gap without writing anything.

What we deliberately do not store

The Fortnite snapshot is fetched from a community mirror of Epic's own game data, then reduced to facts before it is committed. Four categories are dropped on purpose:

Epic item renders and icons
Copyrighted artwork. Not stored, not served, not reproduced.
Item descriptions
Epic-written copy, and the only field a text page would otherwise lean on for flavour.
Shop rotation
The endpoint that served it now returns 410 Gone, so no page here claims what is in the shop today.
Variants and styles
Upstream data quality varies by year; including them would make the score look finer than it is.

Open verifications

These are recorded inside the dataset files, not in a doc nobody reads. Until an item is closed, the figure it guards keeps its lower confidence label on the page.

  1. 1Read the seven rates from Epic's in-game odds screen directly, rather than from @FortniteStatus reprints — no page here can show an Epic screenshot yet.
  2. 2Confirm whether the Treasure Hours multiplier is fixed per window or recalculated each time, and publish the window that is live at build time instead of Epic's 2026-11-07 example.
  3. 3Re-check the chest-type list once Week 3 reveals whether buried and sprite chests still both roll the table.
  4. 4Settle whether Sukono and Rebel Fighter (Sukuna) are the same unit; until then the SS consensus pick is provisional and Rebel Fighter (Gauntlet) must not be merged with either.
  5. 5Diff source C against A and B once its Top 8 names can be matched to tier letters, and read source D's table from a rendered page.
  6. 6Confirm the 15.5 changelog contents from a rendered page — only the heading and date were readable, so no unit or balance claim is attached to that version yet.
  7. 7The grail probe now passes at 15 of 15, but that is 15 names against 16,838 rows. A second catalogue source is still the only way to learn what this mirror is missing outside a published list.

Snapshots are files, not vibes

Each dataset is a JSON file in the repository with its fetch timestamp inside it, so “when did we last look” is answerable from the artefact itself, and the git history is the changelog. Page lastmod values come from those commits rather than a build timestamp, which would reset every deploy.

Requests and corrections

If a figure here is wrong, the fix is a smaller dataset and a rebuilt page — and the correction is visible in the file's history. Rights holders: the site holds no Epic or Roblox artwork, sells no in-game items, quotes no prices, and links to no account markets or cheat tools, per Epic's fan content policy. To flag an error, use the contact address on the about page.