Execution, data, and bot context

Execution wiresCopy Anchor Link

An execution wire selects the next node to run. A trigger starts the graph, and action or flow nodes continue that path through their execution outputs. A data wire alone does not mean that an action runs.

For a branch, connect the action to the appropriate True or False execution output. For a loop, distinguish the body output from the output after the loop finishes. Use the node reference for the exact port IDs of your backend baseline.

Data wiresCopy Anchor Link

A data wire supplies an input value from another node's output. The engine resolves that value as part of the workflow. Values have types such as string, number, boolean, bot, vector, list, or map.

A required input needs a compatible value. An optional input can use its declared default. The editor's inline value supplies an unconnected input, such as a chat message or interval. Do not connect an execution port to a data port.

Bot contextCopy Anchor Link

Bot event triggers carry the bot that caused the event. Downstream bot actions use that execution context unless a connected bot input overrides it. This makes the first script work with only an execution wire.

A trigger without a bot context needs an explicit bot source for bot actions. Choose or iterate the intended bots rather than assuming that a timer selects one automatically. Check the trigger's outputs and action requirements in the reference.

Branches and loopsCopy Anchor Link

Start with one branch and a known constant condition. Check both paths before connecting game state to the condition. For a loop, use a small bounded input first. Check the expected number of actions and the completion path.

A loop that sends chat, requests HTTP data, or calls an AI model can multiply work quickly. Use a delay, rate limit, and the script's quotas where the workload needs them.

Subscriptions and side effectsCopy Anchor Link

Data nodes compute values. Action nodes change the world or backend state. Keep those changes on a clear execution path. A timer, reconnect, or repeated chat event can run the same action again. Design repeated execution deliberately.

Related guidesCopy Anchor Link

Use state and persistence for values shared across events. Use debugging to inspect an unexpected execution path.