Find the right node
Start with the job you need done, then jump to the node family, pins, C# shape, and practical guide.
On this page
The reference groups nodes by what they do: choosing a path, calling code, reading or writing a member, producing a value. Each entry shows the node with its pins beside the C# it stands for.
New to the canvas? Read Nodes, pins, and wires first: it introduces the exec and data pins, the type colors, and the node shapes these entries assume.
Four node families
Every node belongs to a family. The color tells you what job the node does before you read its label.
Flow
Choose a path, repeat work, handle failure, or leave the method.
Calls
Ask this class, another indexed class, or an external API to do work.
Data
Read, write, create, and combine the values that travel through pins. A value node takes the color of the value it produces.
Structure
Mark where execution enters, returns, or reaches unsupported source.
Read an entry
Section titled “Read an entry”Every entry follows the same structure:
- Purpose says why the node exists in a game method.
- Pins lists direction and value type. Inputs enter on the left; outputs leave on the right. Exec pins carry order, while data pins carry typed values.
- C# shows the source shape the node represents. Most snippets come from the Platformer sample, and each page says which do not.
- Guide links to the page that uses the shape in context.
Pure nodes omit exec pins because they produce values without a separate step in the execution order. Impure nodes take part in the white exec-wire path.
Reference pages
Section titled “Reference pages”- Flow nodes: entry, return, branches, loops, switches, handlers, resource scopes, and placeholders.
- Call and member nodes: calls by source scope, GET pills, SET, and assignments.
- Data nodes: literals, expressions, operators, conditionals, and null-aware values.
- Colors: the exact type, family, and status palette.

