Skip to content

Learn Building

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

Building focuses on reusable building placement and construction behavior.

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

Building owns:

  • placement state
  • preview placement flow
  • rotation behavior
  • generic placement validation
  • placement result events

It does not own:

  • inventory costs
  • economy balance
  • unlock rules
  • building meshes or art direction
  • project-specific UI

Building should be usable by itself. When other Dynaros products are installed, integrations can make workflows smoother without turning unrelated products into hidden requirements.

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

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