Source policy

Source Policy

This page explains where we get our information, how we rate sources, and how our automated and manual verification processes work. We believe transparency about data origins helps readers trust what they find here.

Source Categories

Every piece of information on this site is traced to one of the following source categories. The category determines how we handle, label, and present the data.

Category
Description
Examples
In-game
Confirmed by testing the game directly — the gold standard
Codes redeemed and verified working; mechanics observed in live gameplay
Code trackers
Dedicated code tracking sites with reliable update histories
Roonby, GamesRadar, Pro Game Guides
Community wiki
Fan-maintained knowledge bases with broad contributor bases
Volleyball Legends Wiki (vl.fandom.com), VL Guide (vlguide.com)
Visual evidence
Screenshots and video footage used to confirm mechanics visually
YouTube gameplay videos, Roblox experience pages
Community reports
Player discussions and crowdsourced observations
Reddit threads, Discord discussions, Trello boards
Official
Directly from the game developers or Roblox Corporation
Official Roblox group posts, game patch notes, developer social media

Automated Data Collection

We run automated scanners that check multiple external sources on a regular cadence. These scanners collect candidate data that then goes through a verification step before publication.

Scan cadence

Data type
Scan frequency
What happens after scan
Game codes
Every 6 hours
New candidates are flagged for manual confirmation before appearing as active codes
Update signals
Every 6 hours
Patch notes and version changes are logged and cross-referenced
Trending topics
Daily
Keyword and search trend data is reviewed for content planning

The last automated scan completed at: Jul 15, 2026, 08:00 AM GMT+8. Scans run via GitHub Actions and results are logged for audit.

Manual Verification Process

Automated collection gives us candidates. Manual verification determines what gets published. Our verification process follows these steps:

  1. Candidate collected — An automated scanner detects a potential new code, update, or data point from a tracked source.
  2. Source checked — The original source is reviewed for credibility. A code appearing on multiple trackers carries more weight than one appearing on a single, unknown site.
  3. Cross-referenced — Where possible, information is checked against at least one additional independent source.
  4. In-game verification (where possible) — For codes, we attempt to redeem them in-game. For mechanics, we test them. Items confirmed this way are labelled "verified in-game."
  5. Published or held — Confirmed items are published. Unverifiable items are held in a candidate queue for re-check.

Source Trust Framework

We assign every source a trust rating based on its track record, transparency, and update reliability. These ratings determine how much weight we give to information from that source.

Rating
Criteria
Sources at this level
High
Consistent accuracy history, transparent about updates, no pattern of publishing unverified claims
Roonby, GamesRadar, in-game confirmation
Medium
Generally reliable but occasionally includes speculation or delayed updates
Community wikis, VL Guide, Pro Game Guides
Low (facts)
Useful for discovery and trends but not authoritative for factual claims
YouTube creators, individual social media posts
Authoritative
Official source — any information from this level overrides all others
Official Roblox group, developer announcements

Data Provenance Tracking

For every published data point, we maintain provenance information that answers three questions:

  • Where did this come from? — The original source URL, source category, and date first observed.
  • How was it verified? — The verification method used (cross-reference, in-game test, official confirmation).
  • When was it last confirmed? — The most recent date the information was re-checked and still found to be accurate.

This provenance data is stored in our content management pipeline and used to automatically flag items that have not been re-confirmed within their expected validity window.

Source Lifecycle Management

Sources are not static. We continuously monitor the sources we rely on and adjust their trust ratings as their reliability changes.

Source onboarding

New sources go through a probationary period where their output is compared against verified data before being assigned a trust rating.

Source review

Every tracked source is reviewed monthly. If a source's accuracy drops or its update cadence becomes unreliable, its trust rating is adjusted accordingly.

Source retirement

Sources that go offline, stop updating, or demonstrate a pattern of inaccuracy are retired. Retired sources are removed from our scanning pipeline but their historical data may remain in provenance logs.

Transparency & Accountability

We maintain a log of every source we track, its trust rating, and any rating changes over time. This log is available upon request through the contact methods listed on our About page.

If you believe a source is misrepresented or if you have information about a source's reliability that we should consider, please let us know. We take source integrity seriously and investigate every report.

For more detail on how we handle evidence levels and corrections, see our Editorial Policy.