Fighting Game · Features

V2 — Features (Page Index)

A focused page within the Fighting Game Features documentation. The full map and every sibling page live in the Features hub.

7sections3 minread1diagram
← Back to the Features hubMarkdown source
On this page

This directory holds the V2 (UE5 competitive fighting game) feature map, decomposed from the single ../V2_features.md hub into focused, in-depth, code-grounded pages. The hub remains the canonical entry point and preserves every section heading (so existing features§"…" cross-references keep resolving); each page below expands one part of the product with far richer, code-grounded detail and an honest implemented / spec-only status. The companion architecture reference lives in ../architecture/.

Cross-reference convention. Page-to-page links are relative (./<slug>.md); a bare §N points at a section of the V2 backlog, and the architecture companion for a feature page is linked as ../architecture/<slug>.md. Platform-foundation links point at the shared platform/ space.

Feature landscape#

flowchart TB Promise[V2 competitive fighter promise] --> Combat[Combat rulesets defense tag assists and feel] Promise --> Modes[Modes training replay signature events and adventure] Promise --> Content[Roster stages relationships progression and creator suite] Promise --> Online[Matchmaking ranked tournaments esports and integrity] Promise --> Live[Store DLC battle pass community support and AI broadcast] Promise --> Racing[Racing vehicles crossover and open-world operations] Combat --> Shared[Shared identity input accessibility content and telemetry spine] Modes --> Shared Content --> Shared Online --> Shared Live --> Shared Racing --> Shared Shared --> Launch[Localization platform production wellness balance and launch]

Read the landscape from the player promise down to the shared release spine. The branches describe distinct product jobs, not isolated products: a ruleset, race, tournament, authored fighter, store entitlement, or accessibility setting still crosses common identity, version, telemetry, support, and platform boundaries.

Use this index in three passes. First choose the page that owns the visible player contract. Second pair it with the closest page in the architecture index to identify simulation, service, data, provider, and authority ownership. Third check the backlog, dependencies, dated review, current code/tests/builds, and platform evidence before assigning completion state. A focused page is deliberately comprehensive, but it is not a release ledger.

The topic list is exhaustive and non-overlapping at the documentation level: every focused feature page appears exactly once below. Cross-cutting concerns are linked from multiple pages in prose where needed, while their canonical home remains clear. Continue to the V2 documentation guide for role-based reading paths and truth vocabulary, or the diagram atlas for the product-wide mental models.

Orientation#

Combat & Game Feel#

Game Modes#

Roster, Story & Creator Suite#

Online, Esports & Live Service#

Racing, Platform & Launch#