Learn Achievement

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

Core Idea

Achievement focuses on persistent achievements, challenges, and milestone goals that observe gameplay events.

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

Responsibility Boundary

Achievement owns:

• achievement identity
• achievement progress
• challenge state
• completion events
• persistent achievement data

It does not own:

• quest logic
• platform SDK behavior
• inventory rewards
• gameplay actions
• achievement UI style

How It Fits

Achievement 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

Project or gameplay event
        v
Achievement plugin behavior
        v
Achievement validation / state / result
        v
Owning project or related system responds

What To Learn Next

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