Game codes are not stable facts. A Roblox code can be posted in a Discord channel at noon and be dead by evening, and the code trackers that report them frequently disagree with each other. This page explains exactly what our labels claim, so you can judge a row for yourself instead of trusting a green tick.
What Each Status Label Means
| Label | What we are claiming | What we are not claiming |
|---|---|---|
| New source-listed signal | This code appeared recently on at least one tracker we check, and it was not on our page at the previous check. | That it currently works. New codes are the most likely to work and also the most likely to be reported wrongly. |
| Source-listed | A tracker we check lists this code, and no source we saw contradicts it. | That we redeemed it ourselves. |
| Caution | Something specific about this row is uncertain — a stated expiry date is close, a reward figure is unconfirmed, or only one source lists it. | That the code is broken. Caution means "read the note before spending time on it". |
| Disputed | Trackers actively contradict each other on this code — some list it active, others list it expired. The note says who says what. | That we know which side is right. We publish the disagreement rather than silently picking a winner. |
| Expired | Sources report the code as dead, or a stated expiry date has passed. | That it never worked. Expired rows stay on the page so you can tell "this code is finished" apart from "we never heard of this code". |
How We Handle Trackers That Disagree
Disagreement is the normal case, not the exception. When sources conflict, we apply these rules in order:
- Corroboration before publication. A code listed by exactly one tracker, with no date and no second source, does not get published as active. It is either omitted or carried as a caution row with the gap stated. We have left real-looking codes off pages for this reason.
- Freshness beats volume. A tracker that states when it last checked a page outranks one that publishes a long list with no dates. Large lists of "active" codes that include entries everyone else marks expired are treated as stale, however impressive the count looks.
- Show the split. When two credible trackers disagree, the row is marked disputed and the note names the dates on both sides. Guessing would be faster; it would also be the thing that makes a codes page worthless.
- Reward figures are treated separately from code strings. Trackers often agree that a code exists but report different rewards for it. Where that happens we say so and treat the numbers as approximate.
- Impossible dates are discarded. A page claiming it was updated later than today is not evidence of anything, and we do not cite it as a freshness signal.
How Often Pages Are Re-Checked
Code pages carry two dates and they mean different things:
- "Last checked" in the page banner — the date we last ran a source sweep for that specific game.
- Dates next to each source link — when that tracker itself said it was last updated. These are often older than our check date, and that gap is information worth having.
Games do not move at the same speed, so they are not checked at the same speed. Titles that ship codes with every update — or that expire codes within hours — are swept most often. Games with no code system at all, or that have gone months without a drop, are checked far less. If a page's check date looks old to you, that usually means nothing has changed, but you should weigh it accordingly.
What We Will Not Publish
- Invented codes. If a game has no codes, the page says it has no codes. Several games on this site have pages whose entire content is "no codes exist yet, here is what does exist and where real codes would be announced".
- Codes from sources that fabricate. Some sites publish plausible-looking code strings that appear nowhere else and follow obvious keyboard patterns. We do not relay those, even when it would fill a table.
- Rewards we cannot attribute. If no source states what a code gives, the reward cell says the reward is unlisted rather than inventing a number.
- Single-use or account-bound codes. Codes tied to a physical product, a specific purchase, or one person's account are not shareable and are not republished here.
- "Confirmed working" claims. We do not use that phrasing anywhere, because we are not in a position to confirm it for your account, region and game version.
When We Get It Wrong
We will. A code that was genuinely live when a page was written can be dead an hour later, and a tracker we relied on can turn out to have been wrong. When we find that a page made a claim that did not hold up, we correct the page and say what changed rather than quietly deleting the row. Expired and disputed rows are part of the record for the same reason.
If you find a row on this site that is wrong, tell us — a report that a code failed in-game is more useful to us than another tracker's list.
Related Pages
This page covers how code rows are produced. Our broader content sourcing and liability terms are on the disclaimer page, and every code page carries its own sources and check date.
Last updated: August 11, 2026