Confirmed
Redeemed in-game or directly supported by a first-party source during the recorded check.
Trust standard
Our goal is to help players make a decision without hiding uncertainty. A checked date describes the evidence boundary of a page; it is never generated automatically just to make content look fresh.
Redeemed in-game or directly supported by a first-party source during the recorded check.
Supported by current evidence and treated as working, but the page should still show its last check boundary.
Published by one or more current sources but not independently redeemed by RobloxCalc.
Current sources or test results disagree. The page must show the conflict instead of choosing a convenient claim.
Known to have stopped working or moved into the historical archive.
There is not enough reliable evidence to assign a stronger state.
In-game UI, official Roblox experience, developer announcement, official Discord or official Trello.
Repeatable gameplay capture or a test result with a recorded date and game version.
Multiple current sources that independently agree and can be traced to the same game entity.
One current guide, video or community post. Useful as a lead, not enough for a confirmed claim.
A transparent estimate or editorial judgment. It must be labelled and must not be presented as official math.
A calculator should identify its inputs, source model, assumptions, limitations and verification date. When a formula is inferred, the page must say so and avoid false precision.
Factual fields remain separate from editorial ranking. Rankings should state their task—such as PVE, PVP or farming—and explain when community evidence conflicts.
Roblox games change quickly. If a code, formula, ranking or game status is wrong, send the affected URL, the observed result, and any first-party evidence. We review corrections by evidence strength rather than publication order.