Purpose
(TODO)
Responsibilities
- (TODO)
Data & interfaces
(TODO)
Dependencies
- Inbound: (TODO)
- Outbound: (TODO)
Debugging & tooling
(TODO)
Constraints
- (TODO)
Sources
- (TODO; keep aligned with frontmatter)
Missing / conflicting information:
- Content sections are stubbed with TODOs; needs canonical text from project sources.
- No chat decisions recorded; prioritize future chat resolutions over documents if conflicts arise.
- Media not provided in drop-in; add references or uploads when available.
Media placeholder: pending upload.
Summary (placeholder)
Pending canonical content. Replace with a concise overview sourced from project documents or chat decisions.
Details to add
- Fill in core sections with vetted information.
- Add references to sources (docs, commits, chats) in Sources.
- Include tables or graphics if available; otherwise keep the media placeholder.
Link opportunities
- Cross-link to data contracts, runtime systems, and editor tooling.
- Call out where universe concepts drive mechanics.
- Propose new subcategories: Networking/Multiplayer, Rendering & Performance, Build/Deployment, Testing/QA, Telemetry/Observability, Modding/Plugins.
- Link to database schemas, editor, pipelines; add ERDs.
Open questions / conflicts
- List conflicting notes here; resolve with chat decisions first, then documents.
- Track pending media/table additions.
Media placeholder: pending upload.
Source excerpts
● Leverage modular design to reduce dependency bottlenecks. ● Prioritize reusable tools and pipelines. ● Maintain morale through regular creative reviews and open contribution. --- Scope This reference focuses exclusively on runtime systems and their integration hierarchy. It does not cover art pipelines, content creation, or narrative writing, except where those elements directly interact with core systems (for example, dialogue or quest triggers linked to Actors). --- transitions, and cooldowns. Behavior Authoring Guidelines ● Single Responsibility: Each State Unit should handle one behavioural concern only.
Open questions / conflicts
Open: hierarchy between time rifts and anomalies not locked; naming conventions (full vs given names) not fully locked. Time travel remains non-player-controlled; chat canon overrides docs.