Home / Editorial policy

Editorial Policy

A code status on this site is a count of public pages, plus the date I read them. It is not a badge from inside the client.

The check

1. Read the Roblox description for the milestone sentence and the listing time.
2. Read IGN, Rock Paper Shotgun, and LevelGeeks for the current working set.
3. Read Beebom, shibuya.wiki, and UrGameTips as older snapshots, not as a veto by themselves.
4. If the three current lists agree, the row says Active · 3 sources.
5. If only older pages carry it, or fewer than three current lists carry it without an expired claim, the row says Reported and the count.
6. If one list says live and another says dead, the row says Disputed and both rewards stay.
7. If the expired claim is the one I can stand behind, the name moves to the archive and stays in the file.

Rewards that disagree are printed side by side. A blank reward stays blank. I do not average 30 technique rerolls and zero technique rerolls into 15. The checked date is the day of the reading, never the word “today” left to rot.

Corrections: mail [email protected]. A wrong code or a wrong reward is updated after review of a sourced note, and the row’s date moves. A screenshot of a public page is enough. I do not require a client recording to fix a citation.

Drafting help can arrange a paragraph. It cannot invent a code. If a string is not on a page I can link, it does not ship. The analytics and advertising providers used by this version are named on the privacy page. Advertising does not change code status or table order.

Sources

• All linked sources on this page were reviewed on 8 Nov 2026; dates noted beside a publisher are its own update dates.
• The six code pages linked from the code table.
• Contact for the correction desk.