Fighting Game · Balance & tuning

V2 Cross-Character Timeline

beats, Side Story events, Arcade ending canonicity per branch, post-credits scene hooks, and DLC future events.

4sections1 minread
Markdown source
On this page

Master Cross-Character Timeline#

timeline.csv is the canonical index for pre-Story event chains, Story major beats, Side Story events, Arcade ending canonicity per branch, post-credits scene hooks, and DLC future events. Each row uses a stable event_id so Hathor compiled lore, Bellona cooked assets, and V2 profile UI can agree on the same timeline reference without moving authored Story source into Unreal.

Per-Event References#

Each event must carry at least one lore page, Side Story reference, audio diary, and codec entry. Those references give codex pages, intro banter, audio diary playback, and profile history panels a stable back-link to the same event. Arcade branches and DLC hooks are optional on individual rows, but every launch-era timeline export must include at least one Arcade ending branch, one post-credits hook, and one DLC future event.

Per-Fighter Timeline View#

The fighter profile Timeline View filters timeline.csv by participants, groups events by era, and highlights canonical events before branch-canon or what-if entries. Profile cards show the event title, canonical status, linked lore page, related Side Story, and whether the event feeds Arcade endings, post-credits cinematics, or DLC future hooks.

Authoring Rules#

  • Hathor owns the narrative source and emits compiled timeline artifacts.
  • V2 owns roster ids, profile presentation, and the immutable event reference ids consumed by gameplay-facing UI.
  • Published canon events are append-only for a given Hathor worldId and versionHash.
  • Cross-franchise or post-launch-crossover entries must keep their canon scope explicit so Story Theater and codex pages do not overstate canonicity.