Fighting Game · Guides & deep dives

Launch Readiness

The pre-launch drill gate requires a 60-day internal dogfood, all-mode and all-platform coverage, closed beta metric targets, beta-blocking issue remediation, platform cert signoff, and 5x network stress.

4sections2 minread

On this page

LaunchReadiness.V2 is the Section 138 catalog for proving that V2 is ready for General Availability. It bridges the Unreal test harness, balance launch data, go/no-go documentation, CI checks, and the TODO checklist.

Drill Gates#

The pre-launch drill gate requires a 60-day internal dogfood, all-mode and all-platform coverage, closed beta metric targets, beta-blocking issue remediation, platform cert signoff, and 5x network stress.

Closed beta metrics are concurrent peak, matchmaking time, rollback frame distribution, crash rate, and anti-cheat false-positive rate.

Go/No-Go Gates#

V2/docs/launch/go-no-go.md is the launch decision record. It requires General Availability approval, rollout approval, rollback approval, live monitoring dashboards, and online-services canary analysis automation.

The required dashboards track crash rate, server health, matchmaking p99, rollback frame distribution, and rage-quit rate.

Critical Journeys#

The critical journey matrix keeps first-boot tutorial under 25 minutes and covers arcade ladder, story branches, WWE Universe, MyCAREER WWE, UFC GOAT career, MyGM, MyFACTION, MyRISE, Royal Rumble, towers, Survivor, Tournament, Battle Hub, World Tour, Tekken Force, Devil Within, Chronicles of the Sword, Def Jam Story, online ranked promotion, crew-vs-crew, tag-team 2v2, Royal Rumble online fill, custom content, accessibility, and cross-progression smoke tests.

The feature gate matrix covers tournament and streamer tooling, Battle Pass and challenges, display tech, adaptive AI, adaptive controllers, photosensitivity, ratings, profile and match history, quick rematch, championships, anti-cheat, creator programs, Kameo, production, UX, nostalgia modes, locale depth, reliability, esports, compliance, stage lore, relationship timelines, live service calendar, damage staging, cosmetic rarity, setplay theory, projectile tagging, audio diaries, disconnect policy, voice and tactile onboarding, segmentation, and telemetry HMAC replay determinism.

Exit Criteria#

Exit criteria require external ruleset feel playtests, rollback at 100 ms RTT against a 30 ms local-feel reference, complete launch-day modes, no coming-soon panels, at least 60 fighters, at least 30 stages, SOTA training review, combat trial and mission completeness, replay/spectator/photo/ghost coverage, character presentation, tag-team online, tournament/streamer/speedrun and coach modes, transparent monetization without real-money loot boxes, display tech, adaptive controllers, security, observability, production, UX, engineering reliability, locale depth, and rating-board approvals.