> For the complete documentation index, see [llms.txt](https://mindcodeinteractive.gitbook.io/easy-build-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mindcodeinteractive.gitbook.io/easy-build-system/integrations/playmaker.md).

# PlayMaker

This integration connects the building system with [PlayMaker](https://assetstore.unity.com/packages/tools/visual-scripting/playmaker-368).\
Control building actions through FSM states and actions without code.

***

### How It Works

The integration adds custom FSM Actions to [PlayMaker's](https://assetstore.unity.com/packages/tools/visual-scripting/playmaker-368) Action Browser under **Easy Build System**. Control building modes, select parts, place, destroy, adjust, upgrade, save, and query.\
Every action includes **Success Event** and **Failure Event** outputs for FSM branching.

***

### Requirements

* [PlayMaker](https://assetstore.unity.com/packages/tools/visual-scripting/playmaker-368) (v1.9.9+) by Hutong Games

***

### Installation

{% stepper %}
{% step %}

### Install PlayMaker Integration

Make sure **Easy Build System** and [PlayMaker](https://assetstore.unity.com/packages/tools/visual-scripting/playmaker-368) are both imported in your project.

Open the Hub at: \
`Tools > Mind Code Interactive > Easy Build System > Hub > Integrations`.

<figure><img src="/files/ylfBhPToMXKTrcCq6HS2" alt="" width="563"><figcaption></figcaption></figure>

Search for the [PlayMaker](https://assetstore.unity.com/packages/tools/visual-scripting/playmaker-368) integration and click **Install Integration**.\
The integration will be imported and the project will recompile. Wait for it to finish.
{% endstep %}

{% step %}

### Check Actions

Create a new FSM on any GameObject.\
Open the Action Browser and look under the **Easy Build System** category.\
All building actions should appear.

<figure><img src="/files/SieuRU1aZe7D9hj1dtFy" alt="" width="270"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

***

### Using Actions

[PlayMaker](https://assetstore.unity.com/packages/tools/visual-scripting/playmaker-368) uses Finite State Machines (FSM) with States, Actions, and Events.\
The integration adds custom Actions under the **Easy Build System** category in the Action Browser.

The core workflow:

1. Add a **PlayMakerFSM** component to a GameObject.
2. Create States and add transitions between them.
3. In each State, open the **Action Browser** and look under **Easy Build System**.
4. Add the action you need.\
   Every action has **Success Event** and **Failure Event** outputs for FSM branching.

***

### Available Actions

**Mode & Selection:** SetBuildingMode, SelectBuildingPart, SelectBuildingPartByIndex.

**Building Actions:** PlaceBuildingPart, DestroyBuildingPart, DestroyBuildingPartByUniqueId, DestroyAllPlacedParts, AdjustBuildingPart, UpgradeBuildingPart.

**Controller Actions:** ValidateAction, CancelAction, RotatePreview.

**Queries:** GetSelectedPart, GetPartByUniqueId, GetPartByPrefabId, GetPartCount.

**Mode Checks:** IsPlacementMode, IsDestructionMode, IsAdjustmentMode.

**Persistence:** SaveBuildings, LoadBuildings, DeleteSave, HasSaveData.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mindcodeinteractive.gitbook.io/easy-build-system/integrations/playmaker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.