Trust page for source-backed wiki content.

Source Methodology

Official Roblox and developer-linked sources can support facts. Search results, videos and community posts are treated as leads until checked.

StatusReady for players

Last checked June 29, 2026. Claims stay tied to official or source-labeled evidence.

Source tiers

  • Tier 1: official Roblox game page, creator page and official linked sources.
  • Tier 2: Roblox public APIs for IDs, thumbnails and public metadata.
  • Tier 3: developer-linked DevForum context.
  • Tier 4: YouTube, Google SERP and community posts as search-intent leads only.
  • Tier 5: competitor pages as keyword-gap references only.

Claims this wiki will not publish as fact

  • Working codes without official or in-game proof.
  • Final weapon stats while the game is in early testing.
  • Discord invites not linked by official sources.
  • Acquisition, ownership or sale claims; the official page says the game is not available for acquisition.

Daily refresh checklist

Roblox pageTitle, description, thumbnail and compatibility

Highest source tier.

CodesOfficial post or in-game proof only

Reject copied lists.

Video leadsUse for questions and screenshots

Do not copy claims as facts.

SitemapOnly useful pages stay indexable

No thin watchlist pages.

How leads become guide content

  • A repeated search question can become a FAQ answer if the safe answer is clear.
  • A video can create a watch item, but it cannot create final stats by itself.
  • A gameplay observation needs date, build context and normal-player reproducibility.
  • A mature page should answer what to do now, what to avoid and what is still unverified.

Source boundary

Evidence cards behind the wiki

Official facts, API snapshots, developer context and search-intent leads are labeled separately so readers can see what each page depends on.