Learn World State
Use this page to understand what World State is responsible for before you look up exact API details.
Core Idea
Section titled “Core Idea”World State focuses on persistent world-level facts and shared state that should matter later.
It should answer its own responsibility clearly without taking over nearby systems.
Responsibility Boundary
Section titled “Responsibility Boundary”World State owns:
- world facts
- state identity
- state queries
- state updates
- persistence hooks
It does not own:
- gameplay rules that cause the state
- player-specific progression
- local actor state
- visual presentation
- save-file storage UI
How It Fits
Section titled “How It Fits”World State should be usable by itself. When other Dynaros products are installed, integrations can make workflows smoother without turning unrelated products into hidden requirements.
Working Model
Section titled “Working Model”Project or gameplay event vWorld State plugin behavior vWorld State validation / state / result vOwning project or related system respondsWhat To Learn Next
Section titled “What To Learn Next”Start with the overview if you are still deciding whether World State owns your problem. Use Guides for workflows, Recipes for focused examples, and Reference for exact symbols or settings.