Two different questions
A game page answers two questions that do not use the same evidence. The first is what the experience is: its name, creator, description, player count, visits, favorites, votes, and the date Roblox last updated it. The second is whether a particular code token should be shown as active. Roblox's public games API answers the first question. It does not publish promo-code tokens, so it cannot answer the second.
The snapshot used for the saved descriptions was fetched at 2026-10-20T12:41:20.544Z. Player counts on a code page are requested again from the games API when the page renders, and the page says so. If that request fails, the page shows the saved counts and the snapshot time instead of hiding the gap.
What the Roblox APIs supply
For each covered experience we store a universe ID and read games.roblox.com/v1/games. That response supplies the official name, description, creator, playing count, visits, favorites, maximum players, creation time, and update time. Votes come from the public votes endpoint. When the creator is a Roblox group, we read groups.roblox.com/v1/groups and link the group's public community page.
Gameplay basics on a code page are limited to that official description and, where it adds a concrete fact, the group description. A mechanic that is not in those texts is left out. The description shown on the page is the text from the saved snapshot, so a developer edit is reviewed before it replaces the paragraph.
The unauthenticated social-links list returned HTTP 401. Discord, X, and Trello URLs are omitted unless the official experience or group description contains an https link. The refresh records the HTTP status. An https URL that the developer wrote inside the experience or group description is shown. A link that only appears on a code roundup is not relabeled as the developer's channel.
How a code becomes active
An active row still needs the exact token, including capitalization, on two current independent pages, or a documented in-game redemption. None of the rows in this repository use an in-game redemption record. The pages that supply the token text are code roundups. They are the cross-check for the string and the reward name those roundups attach to it. They are not the source of the game's name, description, or live stats.
A reachable article is not enough. The token has to be visible in the active or working section, and the second source has to show the same characters. If the sources disagree, one of them cannot be read, or only one source has the token, the row moves to review and disappears from both public tables. That withhold does not create an expired date. Expired is used when the stored sources place that exact token in their expired sections, and the date we record is the date of that evidence, not a guess about the minute the developer turned the code off.
Dates kept on every code
- First seen is the day the token was first stored. It stays put when a later check succeeds.
- Last checked is the day the stored sources were last reviewed for that exact token. A failed or conflicting check does not move it forward.
- Status is active, expired, or review. Only active and expired rows are public.
- Expired on is filled only for an expired row, using the day that expired status was recorded.
- A short status log appends a new event when a later refresh confirms the token again or withholds it. The log does not invent checks that were not run.
The scheduled content refresh re-reads the stored source URLs and the Roblox profile endpoints. It can update a last-checked date when both sources still show the token, append a withhold event when they do not, and replace the saved Roblox profile when the official name, description, creator, or update time changes. Player-count noise alone does not rewrite the saved profile.
What a page is not claiming
A two-source match is not a statement that this site redeemed the code on a player account. A menu path copied from a code guide is labeled with the guide and the day it was read. If the experience's Roblox update time is newer than that reading, the page says the current in-game labels win. Rewards are the words stored on the row. Where no price, exchange rate, or trade value was documented, the page does not add one.
Corrections can be sent to the address on the contact page. A correction should include the token, the conflicting URLs, and the date of the observation. The about page states the same rule in shorter form.