Editorial and code verification policy

Where we look first

We start with the game description, developer Discord, Roblox group, social account, update log, or an in-game message. A current article or community post can help confirm a code, but it is not treated as a developer announcement.

• Check developer-controlled sources first.
• Preserve exact capitalization and punctuation.
• Save the link and the date it was checked.
• Do not invent a reward when the source names only the code.

What each label means

“Tried in game” means we entered the code and saw the result. “Developer source” means the developer published it. “Sources checked” means recent public information supported it, but we did not redeem it on our own account. A rumor is never shown as an active code.

Checked dates do not update themselves

The date changes only when someone reviews the code list or instructions. Deploying a layout change does not make an old list “updated today.”

When a code fails

One failed attempt is a clue, not automatic proof of expiry. We also check server age, spelling, group membership, account level, tutorial progress, and whether the code was already claimed. If reports still conflict, the code stays out of the active list until we know more.

Corrections and independence

We correct mistakes on the existing URL and link sources when they help with a changing fact. We don’t copy another site’s wording or screenshots. If the site later accepts sponsorships or affiliate deals, they will be disclosed and won’t buy a “working” label.