Skip to content
DynarosDynaros Docs

Learn Save

Use this page to understand what Save is responsible for before you look up exact API details.

Core Idea

Section titled “Core Idea”

Save focuses on persistence orchestration, serialization, restoration, versioning, and migration.

It should answer its own responsibility clearly without taking over nearby systems.

Responsibility Boundary

Section titled “Responsibility Boundary”

Save owns:

  • save orchestration
  • serialization contracts
  • restore flow
  • version handling
  • migration hooks

It does not own:

  • the meaning of inventory items
  • quest rules
  • skill calculations
  • world-state decisions
  • project save-slot UI

How It Fits

Section titled “How It Fits”

Save 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
        v
Save plugin behavior
        v
Save validation / state / result
        v
Owning project or related system responds

What To Learn Next

Section titled “What To Learn Next”

Start with the overview if you are still deciding whether Save owns your problem. Use Guides for workflows, Recipes for focused examples, and Reference for exact symbols or settings.