RFC Play on Roblox

How We Source and Check Information

Every gameplay sentence on this site should point at a public page or a public video. The status column says how many of those sources agree: “2 sources”, “1 source”, or “source disagreement”. A missing PC key is a dash, not a guess borrowed from Roblox’s default jump button.

What I keep, what I drop

I keep a number only with the day I read it. Visits and people-playing are a snapshot. I keep a code only when the developer’s own game text lists it. Strings that appear only on other websites stay out of the active code table. I keep a price only when the public sale record includes one.

I drop write-ups that contradict a captioned video, even if they rank well. I drop damage tiers for gloves when the pass text says cosmetic only. I drop a Discord invite that is not linked from the game. Corrections: contact. Who writes the pages: about.

Code checks are scheduled every six hours against the public game text and the pass list. A new candidate needs a developer listing and an independent public source before it is called verified; single-source candidates carry their source count. The visible checked date moves when a check actually runs.

A captioned tutorial frame used as a source
Example of a caption this site treats as a source.
A menu frame used as a source
Example of a menu frame this site treats as a source.

FAQ

What counts as two sources?

Two publishers that did not copy each other. The game page plus a player video is two. Two blogs repeating one video are not.

What if sources disagree?

Both stay in the table. The update page keeps 20 Oct and 28 Oct as separate release readings for that reason.

Do you estimate prices?

No. Off-sale passes with an empty price stay empty.

Sources

Advertisement