Corrections over guesses

Contact & Corrections

Send enough context for another player to understand and reproduce the claim.

What to include

  1. The exact page URL and sentence, table row, or value that needs review.
  2. The source type: official public page, your own live-server test, third-party screenshot, or community report.
  3. The update title, capture date, device, and server context visible when practical.
  4. The exact before state, action, result, and any error or redemption message.

Redact usernames, chat, account identifiers, purchase details, and other private information before sharing a screenshot. Do not send passwords, Roblox cookies, account recovery codes, or payment details.

Prepare a clean evidence report

The evidence form creates a text report locally in your browser; it does not upload the fields or images. For a more complete capture, use the tester checklist first.

Contact channelEmail channel not yet configured

Until a receiving mailbox is configured, download the local report and keep it with the original screenshots. The site does not claim that an unconfigured address is monitored.

How corrections are handled

An official-source mismatch can update a public fact after the source is rechecked. A dated live-server result is labeled as an observation. A single third-party claim remains attributed and does not become “verified” without stronger evidence. Conflicting sources stay visible until a live result or creator-owned statement resolves them.