Editorial and data policy

We prefer official Roblox experience pages and official APIs for game identity, creator, imagery, votes, and player snapshots. Developer announcements and in-game evidence take priority for mechanics and codes. Community wikis and specialist publications are secondary sources when no stable official feed exists.

A code is shown as active only when it passes the current verification workflow. When official confirmation is unavailable, we compare multiple current sources and mark disagreements as checking rather than expired. Codes may still stop working between checks.

Each structured item can carry a source URL and verification date. Currency values, types, and rarities are stored separately from our descriptions so factual fields can be updated without rewriting the page.

Tier lists are editorial, not official. Rankings can consider progression, combat, mobility, ease of use, and price-to-performance. We label the methodology and consolidate variant forms when necessary. Different builds and player skill can produce different results.

RobloxBrain does not copy full source articles. AI-assisted tools may help organize records, draft original summaries, and translate interfaces. Structured fields and publishable claims are compared with the cited sources before release. Automation does not convert an uncertain claim into a verified fact.

Verification dates describe when a record was checked, not a guarantee that nothing changed afterward. Live player counts are snapshots unless explicitly labeled live. We do not change dates merely to make old content appear new.

Readers can report errors through the contact page. Confirmed corrections receive a new verification date. Future advertising or membership relationships will not determine code status, source selection, or tier placement.