About DMG FPS Wiki

DMG FPS Wiki is run by one independent Roblox guide editor. The editor tracks +1 DMG FPS through the channels the game actually feeds: the official Roblox game page and its public APIs (games, votes, badges, groups), the official description — which doubles as the developer's news feed — official game art, and four independent code trackers (Roblox Den, KodeGG, urgametips, GameRant). Creator videos are used for coverage context and are always named. The site-wide reference check is dated 2026-10-30; at that check the game sat at 13,525,152 visits, 517,822 favorites and a 96.2% like ratio across 125,061 votes, and the developer's group Mappy Tappy counted 2,653,826 members.

Snapshot source: official Roblox APIs, 2026-10-30 (site update). Badge fact: the game's only badge, Defender of Earth (“Destroy your first robot”), had been awarded 5,884,921 times by the 2026-10-30 check.

The working rhythm is simple: every content pass re-reads the game description first (because that is where the developer announces updates and codes), then re-runs the four public APIs for the identity and snapshot numbers, then walks the four code trackers and records any disagreement instead of averaging it. Claims that survive that pipeline get printed with their source; claims that depend on something the game keeps internal get a named unknown with the check method — the guide's unknowns list is the running tally.

• Official first. Game facts come from Roblox' official APIs, the official game description and official art whenever they exist, always with a checked date. The description is treated as the news channel it is: its code callout rotation (AA2026 → 10KCCU) is documented on the codes page.
• Unknowns stay unknown. When the game does not publish a number (rebirth requirements, medal rates, the full gun list), we label it unknown, state the check method, and name what would fill the gap — we never estimate player-facing numbers.
• Multi-source claims. Codes are listed as confirmed only when independent trackers agree; the developer's own callout is listed separately and labeled as an announcement.
• Conflicts are shown, not averaged. When trackers disagree — KodeGG's current BUDDY/RELEASE reward labels, or GameRant listing 5KCCU while Roblox Den omits it — both sides and their dates appear on the page.
• Reported is labeled reported. Steps we took from community documentation but did not run ourselves (e.g. the exact redeem flow) carry a “Reported” label.
• No exploits, ever. We do not link or explain scripts, auto-farms or account-risking tools, and we say why on the guide.

The full verification method and the source register live on the Sources page.

• Codes

  Six tracker-confirmed codes (10KCCU now included), a per-source status table, and the KodeGG reward-label conflict printed both ways (checked 2026-10-30).

• Damage calculator

  Session-damage math built only on the official +1-per-hit rule, with worked +1 → +67 examples and rebirth as an explicit input.

• How to play

  The shoot-to-grow loop, medals, rebirth, buddies and stage bosses — official facts first, unknowns labeled.

• Gun framework

  A damage-order framework for gun upgrades, honest about the fact that no full gun list is public yet.

• Source status

  The Trello/Discord/wiki check record: what was searched, when, and where news actually surfaces.

• Which game?

  +1 DMG FPS vs +1 DMG Per Revive, identified by developer and place ID — never by name alone.

The site rebuilds against live official APIs: the prebuild step snapshots playing counts, visits, favorites and votes, and the homepage stamps the exact snapshot time — between builds it shows the last snapshot, never a made-up “live” number. Codes are re-verified on the trackers at every content update, and the description is re-read for a new callout or version note. Data tables (code status, source register, update log) get their checked date refreshed only when a real re-check happened, which is why older dates survive on visual-fact rows: the +1 and +67 per-shot gun examples were last re-inspected on official art dated 2026-09-16 and stay dated to that inspection.

• 2026-09-16 — launch. The site opened against the V1.2 game: the loop guide, the +1/+67 gun examples from official art, and the first identity check separating the game from +1 DMG Per Revive.
• 2026-09-24 → 2026-09-27 — update coverage. The V1.3 notes and the AA2026 callout were captured from the description; the five-code list was locked in with two independent trackers and re-verified.
• 2026-10-20 — depth pass. Every page re-grounded against the live APIs ([W2] title, 10KCCU callout, 9.3M visits snapshot), tracker conflicts added and shown both ways, and the source register expanded to the full named list.
• 2026-10-30 — [W3] recheck. The game shipped its [W3] update (2026-10-29): title tag, official snapshot, the codes tables (5KCCU re-listed active) and the source register (Sportskeeda added) were re-verified.

Spotted a wrong or stale fact? Contact us with the page URL, the claim as you see it, and what you observed in-game. Corrections that check out are applied and the page's checked date is refreshed. If a code fails for you, that is useful evidence too — failed-code reports are exactly how the 5KCCU-style disputes get settled.

Launched 2026-09-16 · domain dmgfps.wiki · not affiliated with Roblox Corporation or Mappy Tappy. The site identifies the game it covers by creator and place ID — +1 DMG FPS by Mappy Tappy, place 100753254401525 — because a similarly named game by a different studio shares its search results. The interactive damage calculator computes only from the game's official +1-per-hit rule and user-supplied values.