Skip to content
DynarosDynaros Docs

Learn Quest

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

Core Idea

Section titled “Core Idea”

Quest focuses on quest definitions, quest state, objective coordination, completion, and failure.

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

Responsibility Boundary

Section titled “Responsibility Boundary”

Quest owns:

  • quest identity
  • quest definitions
  • runtime quest state
  • objective coordination
  • quest lifecycle events

It does not own:

  • dialogue writing
  • inventory storage
  • combat logic
  • gathering rules
  • project narrative UI

How It Fits

Section titled “How It Fits”

Quest 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
Quest plugin behavior
        v
Quest 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 Quest owns your problem. Use Guides for workflows, Recipes for focused examples, and Reference for exact symbols or settings.