The bar for listing a code
A code appears in a verified table only after it has been entered on our own account and someone watched what happened. Each verified row carries three things: the exact string, the reward it paid, and the balance before and after. No receipt, no row.
What our labels mean
- Verified — we entered it and it paid us. The row shows the balance change.
- Accepted but unpaid — the game took the code without giving us anything (usually "already claimed"). We quote what the game said.
- Reported — someone else lists it and we have not confirmed it. The reward figure is theirs, not ours, and we label it that way.
- Expired — it worked once and no longer does. We keep it, struck through, because knowing a code is dead saves you the same time as knowing one is live.
We publish what we did not test
Every game page has a "what we have not tested" section. It is the part most code sites would delete, and it is the part that tells you how much to trust the rest. If we did not try lower-case codes, or never entered a wrong string to see the error, that goes on the page.
When we re-check
Roblox codes usually arrive with updates and die on the developer's schedule, not ours. So updates are our trigger: we read each game's update timestamp from the public Roblox API and re-check its codes when the game ships one. Today that check is something we run by hand rather than a system that runs itself — when a row is waiting on a re-check, the page says so instead of pretending an older check still stands.
Where we look for codes
Codes come from the people who make the game. We read the experience description and the developer's Roblox group shout directly. Coverage of most games also points to a community server as where drops are announced first; where we have not checked that channel ourselves, the game's page says so in its untested list. Strings that circulate on other code lists without an origin we can point at do not get promoted — the same generic string often turns up across unrelated games, real in one and unverifiable in the rest.
When we get it wrong
We will. When it happens, the fix goes on the page with the date, rather than being quietly edited away. Spot something wrong? Tell us — a correction is worth more to this site than a page view.