Nodes and flow¶

ActionFlow 2 models Game Creator component roots, compatible Story Engine Rule roots, reusable asset roots, and instructions with a small set of graph shapes. Compatible Events and Instructions from installed Game Creator 2 modules use these same shapes.

Connections make the serialized hierarchy visible: you can see which root, branch, or Flow output owns an instruction without drilling through nested Inspector lists.

On Start trigger node on the ActionFlow canvas — **Trigger root**An Event starts a component-owned flow.

Log instruction node on the ActionFlow canvas — **Instruction**One input, one output, and the original Game Creator fields.

Wait instruction node on the ActionFlow canvas — **Asynchronous instruction**Continuation remains readable across a wait.

Two-way If branch node on the ActionFlow canvas — **Branch**Conditions choose between Yes and No outputs.

Sequential Flow node on the ActionFlow canvas — **Flow**Coordinate several action paths in sequence, in parallel, or in random order.

Conditions component root on the ActionFlow canvas — **Conditions root**Each serialized component branch becomes an output.

Instruction Asset root with parameters on the ActionFlow canvas — **Instruction Asset root**The reusable sequence and its public signature share one node.

Branch Asset root with Melee and Stats parameters on the ActionFlow canvas — **Branch Asset root**Typed parameters can come from installed modules.

Trigger node¶

A Trigger node represents a Game Creator Trigger component and its selected Event. It is a root: it has outputs, but no input.

Use the Event field in the node body to select or configure the trigger event. Connect the output to the first instruction, branch, or flow node.

Rule node¶

When a compatible Story Engine version is installed, a standalone Rule component appears automatically in the opened GameObject graph. The teal Rule root displays Category, Priority, and its embedded criteria. Rename the Rule with the pencil in its title bar. Its embedded instruction list continues from the output as the same editable node chain used by Trigger and Actions components. When the Story Director executes a Rule in Play Mode, highlighting starts at that root and follows the executed instruction nodes.

The Rule root has no input. When Story Engine is installed, choose Rule in the node picker to create its component; its rename pencil is available as soon as the node appears. Delete a Rule root the same way as a Trigger root. If its instruction chain remains, ActionFlow keeps that chain under an Actions component. Rule copying remains protected. The late-bound integration still lets ActionFlow compile when Story Engine is absent.

Instruction node¶

An Instruction node contains one Game Creator instruction. It normally has one input and one output, forming the main execution chain.

The node body exposes the instruction's actual serialized fields. Changing the instruction type updates the node to match the new instruction.

Branch node¶

A Branch node evaluates conditions and exposes Yes and No outputs. Use it when one decision must choose between two execution paths.

Each output can connect to its own instruction chain. A missing connection simply means that outcome has no following graph path.

Flow node¶

A Flow node organizes several action paths and determines how they run. Choose Sequential to run each path one after another, Parallel to start them together, or Random to run them in a shuffled order.

Use Flow nodes to coordinate related groups of actions while keeping every path visible in the graph.

ActionFlow asset root¶

An Instruction Asset or Branch Asset has one permanent root. It is the entry point for the reusable flow and owns the asset's typed parameter signature.

Asset nodes must be reachable from the root. The root cannot be deleted or used as a connection destination. See Reusable ActionFlow assets for authoring and call-site behavior.

Asset call nodes¶

ActionFlow 2 contributes Game Creator entries that run Instruction and Branch Assets or check a Condition Asset. They appear like other Game Creator nodes and show one call-site argument for every parameter on the referenced asset.

Asset calls may be nested. Keeping both caller and asset graphs open makes it possible to follow execution across that boundary in Play Mode.

Conditions root¶

A Conditions node represents a standalone Game Creator Conditions component. It is a root node with one output per serialized branch and no input.

This is distinct from a two-way Branch instruction: the Conditions component owns a branch list at the GameObject level.

A Conditions component graph with Quest requirement met and Fallback branches leading to separate instruction paths — A Conditions root exposes every component-owned branch at once, making fallback behavior visible without opening nested lists.

Actions root¶

A Game Creator Actions component contributes its instruction list to the graph. Its instructions appear as a connected root sequence and remain owned by that component.

Connection rules¶

Connect from an output port to a compatible input.
Trigger, Rule, and Conditions roots cannot be connection destinations.
An instruction input has a single predecessor.
Branch and Flow outputs can start independent chains.
Disconnect an input or output from the node context menu.

Module-provided nodes¶

The node picker discovers Game Creator Events and Instructions from installed modules after Unity compiles. Their original serialized fields remain embedded in the node, so a module-specific instruction is configured the same way it is in the Game Creator Inspector.

No separate ActionFlow integration is required per module. See Compatibility and modules for details and the limits of automatic discovery.

Inventory module instructions discovered in the ActionFlow 2 node picker — The same instruction shape is used for module-provided content; the picker supplies the module-specific catalog.

Game Creator remains authoritative

Graph connections describe and edit the same list and branch structure that Game Creator serializes. Removing or reconnecting a node changes that underlying structure; it is not merely a visual layout edit.