# Common Patterns

These patterns help you structure networked state machines effectively.

## Player State Machine

For player-controlled characters:

```
Start Node [Run on Owner]
└─ Input Trigger [Run on Owner]
    └─ Movement Actions [RPC to All]
```

### Breakdown

| Node             | Run On     | Reason                                 |
| ---------------- | ---------- | -------------------------------------- |
| Start            | Owner      | Initialize only for controlling player |
| Input Trigger    | Owner      | Only the owner reads input             |
| Movement Actions | RPC to All | All clients see the movement           |

## AI State Machine

For server-authoritative AI:

```
Start Node [Run on Master]
└─ AI Decision [Run on Master]
    └─ AI Actions [RPC to All]
```

### Breakdown

| Node        | Run On     | Reason                        |
| ----------- | ---------- | ----------------------------- |
| Start       | Master     | AI runs on server only        |
| AI Decision | Master     | Server makes all AI decisions |
| AI Actions  | RPC to All | All clients see AI behavior   |

## Shared Game Logic

For game-wide state (lobby, match state):

```
Start Node [Run on Master]
└─ Game State Changes [RPC to All]
    └─ UI Updates [Run on All]
```

### Breakdown

| Node               | Run On     | Reason                           |
| ------------------ | ---------- | -------------------------------- |
| Start              | Master     | Server controls game flow        |
| Game State Changes | RPC to All | Sync state to all clients        |
| UI Updates         | Run on All | Each client updates their own UI |

## Hybrid Pattern

Combine local and networked behavior:

```
Trigger: On Interact [Run on Owner]
├─ Action: Play Local Sound [Run on Owner]
└─ Action: Toggle State [RPC to All]
    └─ Action: Play Animation [Run on All]
```

This pattern plays a sound only for the interacting player while syncing the actual game state change.


---

# Agent Instructions: 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:

```
GET https://docs.ninjutsugames.com/game-creator-2/state-machine-2/multiplayer/patterns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.