Status admission rules

Code Verification Policy

Quick answer: a code is Active only after this site's assigned gameplay tester reproduces it within 24–48 hours. A dated video success is Video-confirmed, not Active. When credible current sources disagree, the status is Conflicting and the recommendation is limited to one safe attempt.

6 public statuses24–48h Active windowNo active claim without reproduction
Researched by
IMGG Research Editor
Gameplay evidence
Public recording review — no first-person gameplay tester assigned
Published
Last updated
Last gameplay check
Evidence
Official · video-confirmed · calculator-derived
Status dictionary

What every code label means

In-game observedActive

Reproduced by this site's assigned gameplay tester in the last 24–48 hours with a visible success response.

Video-confirmedVideo-confirmed

A current dated public recording visibly shows the full successful result.

Community-reportedCommunity-confirmed

Multiple recent independent player reports agree and include sufficient result context.

Community-reportedConflicting

Credible recent sources disagree about availability or result.

UnverifiedExpired

A previously supported code now shows stable current failure evidence.

UnverifiedUnverified

Only a text report or rumor exists; no publishable success evidence is available.

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.

Update history

What was rechecked

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