Learn Spawn
Use this page to understand what Spawn is responsible for before you look up exact API details.
Core Idea
Section titled “Core Idea”Spawn focuses on spawn policies, eligibility, population rules, and lifecycle coordination.
It should answer its own responsibility clearly without taking over nearby systems.
Responsibility Boundary
Section titled “Responsibility Boundary”Spawn owns:
- spawn policies
- eligibility checks
- population rules
- spawn lifecycle events
- PCG-compatible spawn contracts
It does not own:
- enemy AI
- harvesting logic
- terrain generation
- loot generation
- actor-specific behavior
How It Fits
Section titled “How It Fits”Spawn 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 vSpawn plugin behavior vSpawn validation / state / result vOwning project or related system respondsWhat To Learn Next
Section titled “What To Learn Next”Start with the overview if you are still deciding whether Spawn owns your problem. Use Guides for workflows, Recipes for focused examples, and Reference for exact symbols or settings.