In-game observedActive
Reproduced by this site's assigned gameplay tester in the last 24–48 hours with a visible success response.
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
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
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
- 01
Confirm the exact Roblox place
Reject similarly named Roblox experiences and the older mobile game.
- 02
Record account and server state
Capture date, timezone, level, device, server, and whether the account used the code before.
- 03
Enter the exact text once
Preserve spaces and capitalization; do not loop a disputed code.
- 04
Capture the full response
Success, invalid, expired, and already-used responses support different conclusions.
- 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 type | What it establishes |
|---|---|
| Official announcement | What the developer publicly announced, with its date and scope |
| Dated successful redemption | What the documented account received at the recorded time |
| Historical site record | What was previously recorded; not a fresh verification when the original material cannot be reopened |
| Publisher report | What 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
- Published six code statuses, reproduction steps, and reader-report rules.Codes verification workflow