RIVALS Code Methodology

Registered sources

Manual research stays distinct from automation

Every source is registered with permitted fields, its collection mode, and a dated access-policy review. The Roblox game-details API can be collected automatically; the eight editorial and community sources below use manual review.

Listing a publisher records research provenance. It is not an endorsement by that publisher, and it does not mean every listed page is automatically scraped.

Public labels

Evidence determines the status

Active

A current Code needs support from at least two independent research publishers or a controlled in-game check.

In-game verified

This narrower badge requires dated game evidence, including an approved screenshot-backed result.

Needs recheck

Single-source, stale, invalid, or conflicting evidence stays out of Active until the uncertainty is resolved.

Copied stays on this browser

Copied records successful clipboard use in local browser storage. It does not mean the Code was Used or Redeemed.

Freshness and conflicts

Review age changes what we can claim

An Active Code enters a freshness warning after 72 hours. After 168 hours, it leaves Active for Needs recheck until newer approved evidence is available.

Competing redeemable or expired claims are quarantined as Conflict instead of letting one source silently win. One failed attempt is not enough to prove global expiry.

Archive labels

History preserves uncertainty

Active and Joke describe current supported entries. Needs recheck and Conflict expose unresolved review states. Expired requires stronger evidence than an old report; Archived means the catalog retains a Code without treating missing proof as expiry.

Corrections are welcome at contact@rivalscodes.net. Include the Code, what appears wrong, and a source we can review.

Research register

Editorial and community sources