Open-World Narrative · Guides & deep dives

V5 Documentation Guide

The documentation uses three cell counts deliberately: six product ruleset cells, a smaller set with substantial implementation, and plugin shells or planned content where the backlog has not yet earned a stronger claim.

6sections4 minread1table
Markdown source
On this page

This guide is the curated front door to V5, the largest Unreal Engine 5 open-world narrative-action product: six ruleset cells—urban crime, period drama, frontier, monster hunter, galactic squad, and hard vacuum—composed with a shared engine and the cross-cell Mind Palace investigation layer. It connects the product promise to the 74-module runtime, authored case/content systems, online services, production, rights, compliance, and release evidence.

Documentation map#

mindmap root((V5 documentation)) Six cells Urban crime Period drama Frontier Monster hunter Galactic squad Hard vacuum Cross-cell experience Mind Palace and evidence Morality perception and crowds Combat vehicles mounts and ships Modes multiplayer and progression Creation and delivery Case authoring and workshop Authored corpus and balance Live service companion and cross-play Build content telemetry and release Delivery truth V5 backlog and dependencies Product review and remediation Research rights and compliance Tests performance and operational evidence

The documentation uses three cell counts deliberately: six product ruleset cells, a smaller set with substantial implementation, and plugin shells or planned content where the backlog has not yet earned a stronger claim. The focused pages name those distinctions; do not turn the product count into an implementation claim.

Start with the question#

Question Canonical starting point What it covers
What does the six-cell universe promise? Feature hub, feature index, and product promise Player-facing cell identity, shared systems, modes, creation, platform, and launch scope.
How do the cells share one runtime? Architecture hub, topology/module split, and promise/glossary Module ownership, plugin shells, shared contracts, and honest cell maturity.
How does an investigation work? Mind Palace feature, creator/Mind Palace architecture, and interrogation/heist systems Cases, evidence, deductions, dialogue, authored truth, and player consequence.
Which systems cross every cell? Shared cross-cell systems, GAS/animation/input, and perception/crowd/morality Reused gameplay foundations and specialization boundaries.
How do worlds, vehicles, ships, and multiplayer compose? Modes/multiplayer, streaming/procgen, netcode, and vehicles/ships Authority, determinism, streaming, movement models, persistence, and cross-play.
What is actually implemented or release-ready? V5 backlog, product review, current code/assets/tests/builds, and release evidence Conservative status by cell, shared system, surface, platform, and content path.
What external systems are required? Dependency registry Shared/platform dependencies, versions, ownership, and fallback posture.
Where are the visuals? V5 diagram atlas and the global diagram gallery Curated cell/case/runtime/data/release models and all authored diagrams.

Truth model#

stateDiagram-v2 [*] --> Designed Designed --> Authored: contracts data or content records exist Authored --> Implemented: runtime consumes the authored truth Implemented --> Integrated: cell shared systems services and persistence compose Integrated --> Verified: gameplay authority content and quality evidence passes Verified --> ReleaseReady: cook platform operations and rollback pass Authored --> ShellOnly: plugin or dataset exists without the full journey Integrated --> CellLimited: supported only in named ruleset cells Verified --> Regressed: current evidence fails Regressed --> Implemented: repair returns below release readiness

Use the narrowest truthful cell and surface scope. A plugin shell is not a playable cell; research notes are not licensed content; an authored case is not a verified investigation; a vehicle base class is not every movement model; a server adapter is not production cross-play; and a successful cook does not prove gameplay, accessibility, safety, or live operations.

journey title From V5 narrative idea to supported release section Orient Choose cell shared system or investigation path: 5: Product, Design Pair feature contract with module ownership: 5: Architecture section Author Build canonical data case content and rights record: 5: Content, Engineering Integrate gameplay world presentation and services: 4: Engineering section Verify Test authored truth player paths and authority: 5: QA Validate performance accessibility compliance and cook: 5: QA, Release section Operate Prove telemetry compatibility rollback and support: 5: SRE, Release Update docs diagrams backlog and evidence: 5: Owners

Product, narrative, and cell design#

Start with the feature index. Read the target cell plus Mind Palace, shared systems, modes/multiplayer, creator tools, online/live service, and platform/compliance pages that constrain it. Keep authored truth, player inference, presentation, and mutable world state distinct.

Engineering, tools, and content production#

Start with the architecture index. Trace module and plugin ownership, authored schemas/corpus, GAS/animation/input, AI and morality, authority/determinism, world streaming, persistence, presentation, telemetry, build/cook, and tests. Verify compatibility and migration for cases, saves, workshop packages, and live-service content.

QA, rights, accessibility, and operations#

Test incomplete/contradictory evidence, interrogation branches, save/load, world transition, disconnect/rejoin, content-version mismatch, creator denial, rights withdrawal, assistive controls, sensory alternatives, localization, platform loss, and rollback. Current runtime, licensed assets, deployment, and provider receipts decide status—not an ambitious feature inventory alone.

Page-set organization#

  • Feature index — 18 focused topics spanning six cells, Mind Palace/shared systems, multiplayer/creation/services/live operations, platform/compliance, production, world, and launch.
  • Architecture index — 16 focused topics spanning topology, shared gameplay, world/netcode, services/presentation/data/live operations, quality, and signature cell systems.
  • V5 diagram atlas — cell topology, investigation flow, evidence data, content state, module composition, production, and release.
  • Root backlog/dependency/review/remediation documents plus authored-case-corpus/, balance/, loc/, legal/, release/, and operational records — canonical details and evidence at the appropriate granularity.

Documentation quality contract#

Every canonical feature and architecture page remains substantial, indexed exactly once, explicit about the six-cell product scope versus implementation maturity, and visually explains its principal relationship. Behavior changes update contracts, corpus/assets, migrations, tests, backlog/evidence, rights, and runbooks where applicable. Docs Center generation, integrity, freshness, search, diagram gallery, and desktop/mobile rendering must pass.