Project index
What each supplied Unity sample is for and which one to import first.
On this page
Four playable samples ship inside the UPM package and are imported from Package Manager.
| Project | What it is for |
|---|---|
| Platformer | GameObject agents, a first tree and state machine, list and struct values, variable-length arguments. |
| DungeonHeist | One guard that reacts to changing facts, gives up its running work, and takes a value you edit mid-game. |
| HordeSurvival | Entity agents by the crowd, plus a director graph choosing what the next wave looks like. |
| RacingLine | A decision graph bound to a vehicle simulation that was written before the graph existed. |
Each game chapter names its own scene, the object to select, and the graph files that scene runs. Start with Platformer.
Path layout
Section titled “Path layout”The repository test hosts use the standalone layout you see in the engineering source:
Assets/Platformer/... for Platformer and Assets/_Project/... for the other three. Package
Manager imports each declared sample beneath
Assets/Samples/Behavior Trees and State Machines/<version>/<sample>/; Graph, Core, Command, and
Tile remain UPM dependencies rather than being copied into the sample.
Take the behavior, leave the plumbing
Section titled “Take the behavior, leave the plumbing”A sample graph calls the sample game’s real methods and holds references to its real scene objects. That is deliberate, and it means a graph file copied on its own into your project will bind nothing. Keep the set together while you are learning from it: the graph, the host component, the generated provider, and the game capability the graph calls. Then swap that contract for yours one member at a time.
GameObject integration covers the agent on a prefab. Entity integration covers the same job in a World. Sample games is the course order itself, four chapters starting with Platformer.