SCROOMS

Editorial policy

A fact needs an attributable source and a clear scope. A page revision date is not proof that every underlying claim was re-tested in the game that day.

Last checked · By scrooms.org editors

Evidence and scope

When the community Fandom said Tamer in Training was level 15 and three other write-ups said level 25, I kept 25 and noted the conflict. I do the same for instrument stats that disagree between tables.

Source order

S: Roblox APIs, official place and event records, and the Discord invite payload for its own destination. Developer videos are first-party media where attributed; upload metadata alone is not gameplay verification. A: scroomsofficial frequency/instrument records in our research rubric, not developer-owned data. B: community transcripts. C: secondary guide articles.

Claim scope matters more than the letter grade. A badge for level 100 confirms that milestone, not a level cap. A World INDEX item is not automatically a creature. Multiple secondary sites may copy one source and are not automatically independent corroboration.

A single secondary claim is either omitted or explicitly described as reported, with a direct article link and limits. Conflicting stat cards are shown as separate attributed claims, not merged into a synthetic range. The live game prompt is the final practical check.

Codes, patch notes, and event rewards are left empty when the source is empty. We do not fill gaps with plausible strings.

Research, media, and update limits

This is source-based desk research. No first-hand gameplay test, route screenshot, measured instrument benchmark, or tested code redemption is implied by the author voice. AI Overview and PAA answer text are not used as factual sources.

Homepage hero, cards, and the marked-stones player preview are illustrative artwork, not genuine game screenshots. Repeated Roblox promotional images were removed from article pages because no separate reuse permission was established. Optional YouTube players remain click-to-load; linked footage is attributed to its creator, not claimed as our gameplay.

Time-sensitive codes and event claims should be reviewed weekly and after a developer announcement; this is an editorial schedule, not an automated daily check. Re-reading an October 12 source on October 19 does not convert its status into a live October 19 test.

Report the page URL, exact claim, source link, and observed date to the contact address. Confirmed corrections should update the evidence note and relevant page, not only reset a date. Translation, if added, must preserve entity names and share the English source-check date.

FAQ

How do I report an error?

Email [email protected] with the URL and the source. The page date changes when the sentence changes.

Related pages

SourcesThe log behind the grades.ContactSend a correction.

Sources