Fighting Game · Guides & deep dives

V2 Launch Go/No-Go Checklist

steps, rollback triggers, and the day-one patch staging window.

5sections1 minread
Markdown source
On this page

LaunchReadiness.V2 owns the Section 138 General Availability decision record. The checklist is complete only when the launch director, engineering lead, production lead, QA lead, compliance lead, live-ops lead, and customer support lead have signed the same readiness packet.

Required Approvals#

  • General Availability approval is captured under Approval.GeneralAvailability.V2.
  • The rollout plan Plan.Rollout.CanaryDayOnePatch defines canary percentage steps, rollback triggers, and the day-one patch staging window.
  • The rollback plan Plan.Rollback.PlatformBackend covers every platform build and every backend service dependency.
  • Canary analysis is enabled through Canary.OnlineServices.Analysis.

Pre-Launch Evidence#

  • Internal dogfood runs for at least 60 days across all modes and launch platforms.
  • Closed beta metrics cover concurrent peak, matchmaking time, rollback frame distribution, crash rate, and anti-cheat false-positive rate.
  • Beta-blocking issues are remediated and signed off.
  • TRC, XR, and lotcheck are passed on every shipping platform.
  • Network stress testing passes at 5x launch-estimated concurrency.

Dashboards#

Post-deploy monitoring dashboards must be live before approval:

  • crash rate
  • server health
  • matchmaking p99
  • rollback frame distribution
  • rage-quit rate

Critical Journeys#

The launch-readiness automation matrix must include first boot tutorial, arcade ladder per ruleset, story branches, career arcs, management/card modes, towers, Battle Hub, World Tour, Tekken Force, Devil Within, Chronicles of the Sword, Def Jam Story, online ranked, crew-vs-crew, tag-team 2v2, Royal Rumble online fill, custom content publish/download/moderation, a 30-minute accessibility verifier, and cross-play plus cross-progression smoke coverage.

Exit Criteria#

No-go is required if any exit criterion fails: ruleset feel external playtest, 100 ms rollback validation with 30 ms local-feel reference, launch mode completeness, no visible coming-soon panels, 60 fighters, 30 stages, training mode SOTA review, replay/spectator/photo/ghost coverage, tournament and streamer tooling, display tech, adaptive controllers, production, UX, compliance, reliability, or locale signoff.