Sources & verification method

Every factual claim on this site traces to one of the sources below, with a checked date on the page where it is used. When two kinds of sources disagree, the hierarchy decides; when sources of the same kind disagree, both sides are printed. Site-wide reference check: 2026-10-30.

Checked

Source hierarchy

  1. 1. Official Roblox APIs & pages — Identity, description, update notes, votes, badges, group facts. Highest trust — this is the developer's own surface. The description doubles as the news feed, so its rotation (AA2026 → 10KCCU) is tracked like patch notes.
  2. 2. Official game art — Icon and thumbnails we inspected directly (not hot-linked), used for visual facts like the +67 per-shot gun example and the robot enemy designs. Dated to the inspection.
  3. 3. Multi-source community trackers — Codes are listed as confirmed only when independent trackers agree — currently KodeGG/RoCodes.gg, urgametips, GameRant and Dexerto on the core working codes (10KCCU included since the 2026-10-13 check; re-read 2026-10-30), with Roblox Den read through KodeGG's cross-check after its direct fetch failed this run. Destructoid and Sportskeeda are read as additional opinions whose reward labels and code sets differ (both print 5KCCU at 100,000 Damage).
  4. 4. Reported — Community-documented steps we did not run ourselves; always labeled “Reported”, like the in-game redeem flow.
  5. 5. Unknown — Anything without a source stays labeled unknown with the check method named. We never estimate player-facing numbers.

Source register

Checked

How same-level conflicts are handled

Trackers of the same tier sometimes contradict each other. The site's rule is to show both entries with their dates instead of quietly choosing one. Two live examples from the 2026-10-30 check:

The description as the official news channel

The developer publishes update notes only in the Roblox description — no Discord, Trello or patch site is verified (see the status page). So the description is re-read at every site update and its changes are logged:

Verification log

Checked

How live stats work

The homepage status numbers come from the official Roblox API. At each site build we refresh the snapshot and stamp the exact check time; between builds the page shows the last snapshot with its date, never a made-up “live” number.

Known limits

+1 DMG FPS's developer publishes everything through the Roblox game page: the description doubles as the news feed, and there is no official stat table, Discord or patch-note site. This site therefore treats the official APIs and the description as the top source, lists community code claims only when trackers corroborate them, attaches a checked date to every table, and prints conflicting tracker claims both ways (as with the 5KCCU dispute) instead of quietly picking a winner. Anything the game itself does not reveal — rebirth formulas, medal rates, the full gun list — stays labeled unknown rather than filled with guesses.

Where these sources are used next

The tracker reads on this page feed the verified +1 DMG FPS codes list directly; the official-API facts behind the identity checks surface in the two-games comparison.