What to include in a useful correction
For a page correction, include the exact URL, the sentence or field that is wrong, what you observed in the live game, and the date. For a code or pass report, include the exact capitalization, the official or developer-owned source URL, the visible reward or effect, and the response you received in the game UI. A screenshot can help, but it should be accompanied by context that can be checked later.
Do not send passwords, Roblox cookies, recovery codes, payment information, or private Discord content. This site cannot recover accounts, reverse purchases, grant rewards, or resolve moderation issues. Use Roblox support and reporting tools for those concerns.
Correction checklist
Name the page
Copy the full page URL and identify the exact claim.
Add the observation date
Include server or UI context when the value is dynamic.
Add the source
Prefer Roblox or Janitors Studios links for codes, passes, and updates.
Remove sensitive data
Never include account credentials or private tokens.
Contact FAQ
Can you verify a code for me?
Send the public source, exact code text, observation date, and the in-game response. Never send credentials; the site will not log in to a player account.
Can you update a price immediately?
Updates depend on a reproducible source and review. Dynamic values are kept dated rather than changed from an unverified message.
Can I ask for exploit help?
No. This site does not publish exploit, script, credential, or bypass instructions.