HomeSources & Update Policy
Editorial policy

Sources & Update Policy

This wiki separates official facts, dated community reports, and site-maintained judgment. A fast answer is useful only when its evidence is clear.

Last verified

July 27, 2026

Snapshot

Update 80

Status

Monitoring

Official activity

August 3, 2026

Codes checked

July 27, 2026

Update 80 remains the last community-verified gameplay snapshot. The official Roblox listing changed on August 3, but no public patch breakdown, codes, or balance details are confirmed here yet.

Source register

Official Discord announcements

Official

Used for: Named updates, codes, events, and developer corrections.

Rule: Takes precedence over every community report.

Open source

Roblox game page

Official

Used for: Game availability, public description changes, and release signals.

Rule: Useful for confirmation, but not treated as a complete patch note archive.

Open source

Public player references

Community

Used for: Working-code reports, return windows, role fit, and patch observations.

Rule: Must be dated and corroborated before it becomes a community-verified snapshot.

Wiki planning data

Site-maintained

Used for: Tier ranks, build suggestions, calculator assumptions, and comparisons.

Rule: Explains assumptions and never presents editorial judgment as a developer fact.

Update-day checklist

  1. 1Record the official announcement URL or mark the item as community-reported.
  2. 2Test new codes in-game when possible; otherwise leave them in Needs verification.
  3. 3Update the current game snapshot and the affected update, entity, tier, build, and value pages.
  4. 4Set each relevant last-checked date only after the page content actually changed.
  5. 5Add new entities to their directory, detail page, homepage path, and related-page links.
  6. 6Run the content freshness check, lint, and build before publishing.

Maintenance cadence

Update day

Refresh the tracker first, then codes, entities, tier/build guidance, and affected internal links.

Weekly

Recheck code validity, time-sensitive tier claims, banner availability, and source labels.

Monthly

Review Search Console queries and legacy-route performance before creating, redirecting, noindexing, or removing pages.

Report a correction through the contact page. A correction remains labeled as unverified until its source is reviewed.

Legacy URL policy

Older URLs are only redirected when there is a truthful replacement. Pages without an equivalent return 404 instead of being sent to unrelated content. Search Console performance and external links are reviewed before any future removal decision.

/fighting-styles

Permanent redirect

Legacy terminology now maps directly to the real Styles directory.

Review: Keep unless Search Console shows a distinct intent that needs its own real page.

/sub-abilities

Permanent redirect

Legacy terminology now maps directly to the real Abilities directory.

Review: Keep unless Search Console shows a distinct intent that needs its own real page.

/vault

Permanent redirect

The old destination is replaced by the real tool directory and remains non-indexable.

Review: Keep unless an external link requires a more specific replacement.

/stands

404

There is no equivalent Volleyball Legends content, so a redirect would be misleading.

Review: Only create a replacement if Search Console or user demand proves a real game-specific intent.