Our standard: a code is “verified” only when a dated in-game check confirms a response or resource change. Seeing the same text on other websites is discovery evidence, not gameplay verification.
Four evidence states
The current game description or another first-party source names the code. The reward may still be unstated or disputed.
Found in a named, dated public source. It still needs an in-game test.
Tested in game with the check date and result recorded.
A reproducible failure or first-party notice supports the status.
Test protocol
- 01Capture the game build and date.
Freshness is part of the result.
- 02Record resources before submission.
This gives us a measurable baseline.
- 03Paste the exact code once.
We preserve capitalization and spacing.
- 04Record the message and resource change.
Both signals are stored in the editorial log.
Conflicting rewards stay unresolved
If two sources report different rewards, we do not pick the more exciting claim. The tracker keeps the item unverified, adds a conflict note, and waits for a current in-game check.
Corrections
Send the exact code, the date and timezone, the visible game response, and—if safe—a cropped screenshot with personal information removed. We do not publish usernames or account identifiers.