Status admission rules

Code Verification Policy

Active follows the official description or a cited working-code list. Check covers uncertain or conflicting availability. A missing site playtest, unknown reward quantity or differing reward report does not downgrade an Active code.

Active / CheckSources and rewards recorded separatelyHistorical expiry retained
Researched by
IMGG Research Editor
Evidence reviewed
Archived input record: September 2, 2026. Source, arithmetic and explanation review:
Independent gameplay reproduction
Not completed
Published
Last updated
Source basis
Historical archive · publisher reports · calculator-derived examples

Public footage can establish only what appeared on that account and date. It is not first-person gameplay testing by this site. Use the live game screen as the final check for changing values, availability, and account-specific results.

Status dictionary

What every code label means

Community-reportedActive

Listed in the official description or a cited working-code source. Reward details and account requirements are recorded separately.

Community-reportedCheck

Availability is uncertain, source reports conflict, or only an unsupported historical record exists.

Community-reportedExpired

Kept in the historical archive when the source explicitly reports expiry or the announced availability window has ended.

Reproduction sequence

How a code is checked

  1. 01

    Confirm the exact Roblox place

    Reject similarly named Roblox experiences and the older mobile game.

  2. 02

    Record account and server state

    Capture date, timezone, level, device, server, and whether the account used the code before.

  3. 03

    Enter the exact text once

    Preserve spaces and capitalization; do not loop a disputed code.

  4. 04

    Capture the full response

    Success, invalid, expired, and already-used responses support different conclusions.

  5. 05

    Update status and history

    Change reward, status, checked date, recommendation, and source references together.

Reader reports

Worked, failed, and already used are counted separately

A report must include the exact response, server date, account context, and an unedited capture. Duplicate or context-free reports are not counted. A sample size and last-feedback date appear only after reviewed reports exist.

Separate the source from current availability

A source label explains where a claim comes from. A current-status label explains what that evidence supports now. Keep them separate:

Evidence typeWhat it establishes
Official announcementWhat the developer publicly announced, with its date and scope
Dated successful redemptionWhat the documented account received at the recorded time
Historical site recordWhat was previously recorded; not a fresh verification when the original material cannot be reopened
Publisher reportWhat an article says, not automatically an independent gameplay test

An official announcement may exist without a current redemption test. A dated success may exist while today's availability remains unconfirmed. An inaccessible original video must not be relabelled as newly watched.

The absence of this site's Active badge does not prove that the game has no usable codes. Expiration requires evidence of expiration, not simply a missing tester or one negative list.

Update history

What was rechecked

  1. Published six code statuses, reproduction steps, and reader-report rules.Codes verification workflow