Fighting Game · Guides & deep dives

V2 Diagram Atlas

V2 is one product spine with several peer experiences.

9sections2 minread

On this page

This atlas is the visual orientation layer for V2. It condenses the product, runtime, durable records, lifecycle, module ownership, mode estate, production journey, and release order into complementary models. The focused feature and architecture pages remain authoritative for detail; current code, tests, builds, platform evidence, and operations determine support status.

Product and runtime landscape#

FlowchartFlowchart: 12 steps and 12 connections.Player surfacesMenus HUD accessibilityand inputCombat training replayevents racing and worldmodesInteger-frame deterministicsimulationGAS abilities effects andauthored frame dataRollback resimulation andreplayAnimation camera audioVFX stages and broadcastIdentity matchmakingranked tournaments andintegrityProgression storecommunity support andcompanionRoster moves balancemodes and contentversionsHashes replays receiptstelemetry and auditsCook patch platformcertification and release
Flowchart: Flowchart. Flowchart: 12 steps and 12 connections.

This picture is wider than it can be shown here. Move across it, or read it as text.

Drawn from its Mermaid source.

As text
Parts:
- Player surfaces
- Menus HUD accessibility and input
- Combat training replay events racing and world modes
- Integer-frame deterministic simulation
- GAS abilities effects and authored frame data
- Rollback resimulation and replay
- Animation camera audio VFX stages and broadcast
- Identity matchmaking ranked tournaments and integrity
- Progression store community support and companion
- Roster moves balance modes and content versions (data)
- Hashes replays receipts telemetry and audits (data)
- Cook patch platform certification and release

Connections:
- Player surfaces to Menus HUD accessibility and input
- Menus HUD accessibility and input to Combat training replay events racing and world modes
- Combat training replay events racing and world modes to Integer-frame deterministic simulation
- Integer-frame deterministic simulation to GAS abilities effects and authored frame data
- Integer-frame deterministic simulation to Rollback resimulation and replay
- Combat training replay events racing and world modes to Animation camera audio VFX stages and broadcast
- Combat training replay events racing and world modes to Identity matchmaking ranked tournaments and integrity
- Identity matchmaking ranked tournaments and integrity to Progression store community support and companion
- GAS abilities effects and authored frame data to Roster moves balance modes and content versions
- Rollback resimulation and replay to Hashes replays receipts telemetry and audits
- Progression store community support and companion to Hashes replays receipts telemetry and audits
- Animation camera audio VFX stages and broadcast to Cook patch platform certification and release
Show source
flowchart TB
  Player[Player surfaces] --> Shell[Menus HUD accessibility and input]
  Shell --> Modes[Combat training replay events racing and world modes]
  Modes --> Sim[Integer-frame deterministic simulation]
  Sim --> GAS[GAS abilities effects and authored frame data]
  Sim --> Rollback[Rollback resimulation and replay]
  Modes --> Presentation[Animation camera audio VFX stages and broadcast]
  Modes --> Online[Identity matchmaking ranked tournaments and integrity]
  Online --> Services[Progression store community support and companion]
  GAS --> Data[(Roster moves balance modes and content versions)]
  Rollback --> Evidence[(Hashes replays receipts telemetry and audits)]
  Services --> Evidence
  Presentation --> Build[Cook patch platform certification and release]

V2 is one product spine with several peer experiences. The racing and open-world paths are not decorative side modes, but they still share identity, entitlements, content/version, telemetry, accessibility, and release controls with combat.

Authoritative online match sequence#

sequenceDiagram actor P1 as Player one actor P2 as Player two participant Client as V2 client participant Online as Online services participant Server as Authority or peer coordinator participant Integrity as Integrity and replay P1->>Client: Queue with ruleset roster and region Client->>Online: Auth entitlement build and preferences P2->>Online: Compatible queue request Online->>Server: Allocate match and signed configuration Server-->>Client: Seed frame zero peers and policy loop Every simulation frame Client->>Server: Bounded input frame Server-->>Client: Confirmed frame and corrections Client->>Client: Predict rollback and resimulate end Server->>Integrity: Result hash replay and anomaly evidence Integrity-->>Online: Accepted held or disputed result Online-->>P1: Ranked progression and replay reference Online-->>P2: Ranked progression and replay reference

The exact authority model varies by mode. The invariant is that compatible content, signed configuration, deterministic input, result evidence, and idempotent progression are established before a competitive result is final.

Durable competitive records#

Entity-relationship diagramEntity-relationship diagram: 14 entities and 13 relationships.ownsprogressesearnsgroupsconfigurespinsincludescontrolsrecordsverifiesproducessettlesemitsACCOUNTPLATFORM_LINKFIGHTER_PROFILERANKED_ENTRYSEASONRULESETMATCHCONTENT_VERSIONPARTICIPANTREPLAYFRAME_HASHINTEGRITY_SIGNALRESULT_RECEIPTPROGRESSION_EVENT
Entity-relationship diagram: Entity-relationship diagram. Entity-relationship diagram: 14 entities and 13 relationships.

This picture is wider than it can be shown here. Move across it, or read it as text.

Drawn from its Mermaid source.

As text
Parts:
- ACCOUNT
- PLATFORM_LINK
- FIGHTER_PROFILE
- RANKED_ENTRY
- SEASON
- RULESET
- MATCH
- CONTENT_VERSION
- PARTICIPANT
- REPLAY
- FRAME_HASH
- INTEGRITY_SIGNAL
- RESULT_RECEIPT
- PROGRESSION_EVENT

Connections:
- ACCOUNT to PLATFORM_LINK (one to zero or many): owns
- ACCOUNT to FIGHTER_PROFILE (one to zero or many): progresses
- ACCOUNT to RANKED_ENTRY (one to zero or many): earns
- SEASON to RANKED_ENTRY (one to zero or many): groups
- RULESET to MATCH (one to zero or many): configures
- CONTENT_VERSION to MATCH (one to zero or many): pins
- MATCH to PARTICIPANT (one to one or many): includes
- ACCOUNT to PARTICIPANT (one to zero or many): controls
- MATCH to REPLAY (one to one): records
- REPLAY to FRAME_HASH (one to zero or many): verifies
- MATCH to INTEGRITY_SIGNAL (one to zero or many): produces
- MATCH to RESULT_RECEIPT (one to zero or many): settles
- RESULT_RECEIPT to PROGRESSION_EVENT (one to zero or many): emits
Show source
erDiagram
  ACCOUNT ||--o{ PLATFORM_LINK : owns
  ACCOUNT ||--o{ FIGHTER_PROFILE : progresses
  ACCOUNT ||--o{ RANKED_ENTRY : earns
  SEASON ||--o{ RANKED_ENTRY : groups
  RULESET ||--o{ MATCH : configures
  CONTENT_VERSION ||--o{ MATCH : pins
  MATCH ||--|{ PARTICIPANT : includes
  ACCOUNT ||--o{ PARTICIPANT : controls
  MATCH ||--|| REPLAY : records
  REPLAY ||--o{ FRAME_HASH : verifies
  MATCH ||--o{ INTEGRITY_SIGNAL : produces
  MATCH ||--o{ RESULT_RECEIPT : settles
  RESULT_RECEIPT ||--o{ PROGRESSION_EVENT : emits

Account, fighter progression, season/rank, match participant, replay, integrity, and settlement identities remain separate. A replay can verify a match without being the progression ledger, and a provider receipt cannot be replaced by a client result screen.

Match lifecycle#

State diagramState diagram: 14 states and 19 transitions.compatible build content and policyall required participants acceptdecline timeout or incompatibilityframe zero and authority establishedasset network or platform failuregoverned local or tournament pausedisconnect or authority migrationbounded rejoin succeedsrecovery budget expiresterminal game statereplay hashes and integrity checksresult accepted idempotentlyanomaly or version mismatchAssemblingReadyCheckLoadingCancelledActivePausedRecoveringAbandonedCompletedVerifyingSettledDisputed
State machine: State diagram. State diagram: 14 states and 19 transitions.

This picture is wider than it can be shown here. Move across it, or read it as text.

Drawn from its Mermaid source.

As text
Parts:
- Start (initial)
- Assembling
- ReadyCheck
- Loading
- Cancelled
- Active
- Paused
- Recovering
- Abandoned
- Completed
- Verifying
- Settled
- Disputed
- End (final)

Connections:
- Start to Assembling
- Assembling to ReadyCheck: compatible build content and policy
- ReadyCheck to Loading: all required participants accept
- ReadyCheck to Cancelled: decline timeout or incompatibility
- Loading to Active: frame zero and authority established
- Loading to Cancelled: asset network or platform failure
- Active to Paused: governed local or tournament pause
- Paused to Active
- Active to Recovering: disconnect or authority migration
- Recovering to Active: bounded rejoin succeeds
- Recovering to Abandoned: recovery budget expires
- Active to Completed: terminal game state
- Completed to Verifying: replay hashes and integrity checks
- Verifying to Settled: result accepted idempotently
- Verifying to Disputed: anomaly or version mismatch
- Settled to End
- Disputed to End
- Cancelled to End
- Abandoned to End
Show source
stateDiagram-v2
  [*] --> Assembling
  Assembling --> ReadyCheck: compatible build content and policy
  ReadyCheck --> Loading: all required participants accept
  ReadyCheck --> Cancelled: decline timeout or incompatibility
  Loading --> Active: frame zero and authority established
  Loading --> Cancelled: asset network or platform failure
  Active --> Paused: governed local or tournament pause
  Paused --> Active
  Active --> Recovering: disconnect or authority migration
  Recovering --> Active: bounded rejoin succeeds
  Recovering --> Abandoned: recovery budget expires
  Active --> Completed: terminal game state
  Completed --> Verifying: replay hashes and integrity checks
  Verifying --> Settled: result accepted idempotently
  Verifying --> Disputed: anomaly or version mismatch
  Settled --> [*]
  Disputed --> [*]
  Cancelled --> [*]
  Abandoned --> [*]

Lifecycle state must be durable enough to distinguish cancellation, abandonment, dispute, and settlement. Retry or reconnect cannot double-apply rank, rewards, challenge, or commerce effects.

Shared and specialized module composition#

classDiagram class V2GameHost { activateMode() pinContentVersion() } class CombatSimulation { fixedFrame seed stepInputs() } class RulesetPlugin { rosterPolicy tagPolicy damagePolicy } class RacingSimulation { vehicleModel trackRules } class OnlineBoundary { authorize() allocate() settle() } class EvidenceEnvelope { replayRef hashRef auditRef } V2GameHost --> RulesetPlugin : activates V2GameHost --> CombatSimulation : hosts V2GameHost --> RacingSimulation : may host CombatSimulation --> OnlineBoundary : bounded by RacingSimulation --> OnlineBoundary : bounded by OnlineBoundary --> EvidenceEnvelope : emits

Shared hosting and evidence do not flatten ruleset or vehicle specialization. The host owns activation/version boundaries; each simulation owns its deterministic rules; the online boundary owns admission and settlement.

Mode and surface estate#

V2 estateMind map: 21 ideas.V2 estateCombatVersus and rankedTag and assistTraining and replaySignature eventsRacingVehicles and tracksOnline racingFighter-driver crossoverOpen-world activitiesCommunityTournaments and esportsSpectator and broadcastCreator suiteCompanion and supportPlatformAccessibility andlocalizationStore progression andentitlementsTelemetry and integrityBuild certification and liveoperations
Mind map: V2 estate. Mind map: 21 ideas.

Drawn from its Mermaid source.

As text
Tree:
- V2 estate
  - Combat
    - Versus and ranked
    - Tag and assist
    - Training and replay
    - Signature events
  - Racing
    - Vehicles and tracks
    - Online racing
    - Fighter-driver crossover
    - Open-world activities
  - Community
    - Tournaments and esports
    - Spectator and broadcast
    - Creator suite
    - Companion and support
  - Platform
    - Accessibility and localization
    - Store progression and entitlements
    - Telemetry and integrity
    - Build certification and live operations
Show source
mindmap
  root((V2 estate))
    Combat
      Versus and ranked
      Tag and assist
      Training and replay
      Signature events
    Racing
      Vehicles and tracks
      Online racing
      Fighter-driver crossover
      Open-world activities
    Community
      Tournaments and esports
      Spectator and broadcast
      Creator suite
      Companion and support
    Platform
      Accessibility and localization
      Store progression and entitlements
      Telemetry and integrity
      Build certification and live operations

Use the estate to find the owning focused page; use the runtime landscape to trace shared dependencies. A feature may appear in several branches while still having one canonical data and authority owner.

Production journey#

From V2 design change to supported releaseUser journey: 8 stages.1Specify player contract ruleset and platformsDefine. Design, Product. Score 5 of 5.2Update canonical data and compatibility rulesDefine. Design, Engineering. Score 5 of 5.3Change simulation presentation services and toolsImplement. Engineering. Score 4 of 5.4Add telemetry accessibility and recovery behaviorImplement. Engineering. Score 5 of 5.5Run determinism rollback balance and journey testsVerify. QA. Score 5 of 5.6Validate performance cook security and certificationVerify. Release, QA. Score 5 of 5.7Stage cohort inspect evidence and roll back safelyOperate. SRE, Release. Score 5 of 5.8Publish docs patch notes and support guidanceOperate. Owners. Score 5 of 5.
User journey: From V2 design change to supported release. User journey: 8 stages.

Drawn from its Mermaid source.

As text
Steps:
- 1. Specify player contract ruleset and platforms (good). Define. Design, Product. Score 5 of 5.
- 2. Update canonical data and compatibility rules (good). Define. Design, Engineering. Score 5 of 5.
- 3. Change simulation presentation services and tools (good). Implement. Engineering. Score 4 of 5.
- 4. Add telemetry accessibility and recovery behavior (good). Implement. Engineering. Score 5 of 5.
- 5. Run determinism rollback balance and journey tests (good). Verify. QA. Score 5 of 5.
- 6. Validate performance cook security and certification (good). Verify. Release, QA. Score 5 of 5.
- 7. Stage cohort inspect evidence and roll back safely (good). Operate. SRE, Release. Score 5 of 5.
- 8. Publish docs patch notes and support guidance (good). Operate. Owners. Score 5 of 5.
Show source
journey
  title From V2 design change to supported release
  section Define
    Specify player contract ruleset and platforms: 5: Design, Product
    Update canonical data and compatibility rules: 5: Design, Engineering
  section Implement
    Change simulation presentation services and tools: 4: Engineering
    Add telemetry accessibility and recovery behavior: 5: Engineering
  section Verify
    Run determinism rollback balance and journey tests: 5: QA
    Validate performance cook security and certification: 5: Release, QA
  section Operate
    Stage cohort inspect evidence and roll back safely: 5: SRE, Release
    Publish docs patch notes and support guidance: 5: Owners

No one test substitutes for this journey. In particular, deterministic combat, online settlement, presentation, platform packaging, accessibility, and live operations have different evidence owners.

Release evidence order#

timeline title V2 evidence progression Contract : Player promise and compatibility policy : Canonical authored data and schema Runtime : Deterministic simulation and presentation : Online authority persistence and providers Verification : Unit integration replay and end-to-end journeys : Performance accessibility security and balance evidence Candidate : Cook patch certification and support readiness : Staged rollout observability and rollback proof Supported : Named platforms modes regions and content versions : Current operational and regression evidence

The timeline is an ordering of evidence, not a calendar. A later artifact never retroactively supplies missing proof from an earlier boundary.

How to use this atlas#

Start with the landscape and estate, follow a match through the sequence and state machine, use the ER and class models for data/contract reviews, and use the production journey and evidence order during release review. Continue to the V2 guide, feature index, and architecture index. The generated gallery links every additional diagram to its source page and heading.