Sources and Verification Method

This wiki uses a simple standard: every factual claim should be traceable to a source that can actually support it. An official API is strong evidence for a Roblox identifier or badge description. It is not automatically evidence for an undocumented control, exact reaction time, or universal strategy.

The current research snapshot was checked on July 30, 2026. Time-sensitive claims keep that date so readers can distinguish a verified snapshot from a permanent rule.

Source hierarchy

Sources are grouped by what they can reliably establish.

First-party Roblox and developer sources

The highest-authority set includes:

• the official Death Order: Simon Says experience page;
• the Roblox place-to-universe resolver;
• the Roblox Games API;
• the Roblox Badges API;
• the Roblox Game Passes API;
• the official Voxq Enterprises group endpoint;
• the Roblox experience thumbnail endpoint.

These sources support the official title, creator, IDs, description, recorded creation time, classifications, server capacity snapshot, enabled badge inventory, pass records, and creator-selected media.

Even first-party sources have limits. An API field can be missing, anonymous access can omit readable details, and a live value can change. The pass API proves record data but did not expose reliable readable perk descriptions in the checked response.

Community cross-checks

Four public guides were compared for code reporting:

• Pro Game Guides;
• Try Hard Guides;
• PCGamesN;
• MrGuider.

All four supported at least part of the reported redemption information, and the set consistently reported TERRVR, YOUKI, DRAKE, RELEASE, JUNE, FARTS, and FRAGMENTS as 1,000 Cash codes. Multiple-source agreement raises confidence, but it does not make the report first-party.

The codes were not redeemed in a Roblox account during this verification. Their status is therefore described as reported by checked trackers, not personally tested or guaranteed active.

Player videos

Three public YouTube pages were selected as demonstrations:

• Jayingee’s gameplay overview;
• VendoPlus’s full gameplay guide;
• Roblox Master Guides’ walkthrough.

Videos can show the interface, pace, and situations from a recorded session. They are not treated as official rules, patch notes, or proof that a mechanic remains unchanged. A clip cannot establish the complete Event roster or every accepted command.

How a claim is verified

Each claim passes through five questions:

1. What exactly is being claimed? A narrow claim is easier to support than a broad one.
2. Which source owns that information? Roblox owns the place mapping; community guides report code observations.
3. Does the source text actually state it? A product name does not state its perks.
4. Can the value change? Capacity, prices, sale state, badges, codes, and platform metrics need dates.
5. What remains unknown? Missing information stays missing until stronger evidence appears.

For example, the game profile and FAQ states that place 18666738837 maps to universe 6324644175 because the official resolver returned that mapping. It does not derive the universe ID from a fan page.

The badges and lore catalog uses developer-authored badge descriptions for Wren, Marlow, The Free Man, Obby Champion, and First Blood. It does not expand those descriptions into hidden conditions or a complete Event list.

The cosmetics and game passes guide uses the official pass API for record data and two community guides for reported Cash cosmetic categories. It keeps those evidence levels visibly separate.

Confidence and time sensitivity

High confidence means a claim is directly supported by a relevant first-party source, or that the limitation itself is clearly established by the checked record.

Medium confidence usually means multiple reputable community pages agree, but the claim was not confirmed through a first-party publication or direct account test.

Time-sensitive means a value may change. A server capacity, badge count, pass price, code status, or engagement metric should never appear without a check date when readers might mistake it for permanent.

Stable identifiers can still be rechecked, but they are less likely to change than live counters or store state.

Media provenance

The official Roblox thumbnail endpoint returned ten creator-selected experience images. Local copies are labeled official promotional artwork. They are not called gameplay screenshots because the endpoint and visual format do not establish that they are captures of live play.

Generated brand decoration, when used, must also be labeled separately from official game media. A visual’s source label prevents design assets from becoming accidental gameplay evidence.

Claims this wiki refuses to invent

The checked public record did not establish:

• a complete dictionary of command phrases and inputs;
• exact reaction windows;
• a complete current Event roster and official solution list;
• a permanent safe zone or immunity area;
• the exact function of the Expert Predictor pass;
• a complete Cash cosmetic catalog with current item prices;
• a distinct system specifically named Trinkets;
• first-party active or expiration status for the reported codes.

The correct editorial response is not to guess. Articles either narrow the wording, label the detail unknown, or explain how to verify the current live state.

How corrections should work

A correction needs a source that matches the claim. For a pass perk, provide a current first-party product description. For a code status, include a dated developer statement or clearly documented redemption result. For an Event mechanic, prefer developer documentation or a reproducible live observation with date and version context.

New evidence should update the check date, source record, affected article, and any confidence label. It should not silently overwrite provenance.

This method keeps the site useful even when the live game changes: stable facts remain traceable, snapshots remain dated, and unknowns remain visible until they can be resolved.