Learn Ability

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

Core Idea

Ability focuses on a possible lightweight ability plugin for projects that do not need full GAS.

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

Responsibility Boundary

Ability owns:

• candidate ability definitions
• candidate activation flow
• candidate cooldown or cost hooks
• candidate extension contracts

It does not own:

• full GAS replacement behavior
• large-scale effect stacking before scope is proven
• project-specific combat design
• animation logic
• input ownership

How It Fits

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

What To Learn Next

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