Flow nodes
Read the nodes that start a method, choose paths, repeat work, handle errors, and mark code you need to edit in C#.
On this page
Flow nodes answer the question that matters when reading a method: what can run next? Follow the white exec wire first, then inspect the colored data wires that decide or feed each step.
The C# under each entry comes from the Platformer sample unless it says otherwise.
Entry and return
Section titled “Entry and return”Purpose. Entry is the start of a method. Parameters leave it as data outputs. Return ends that path and can carry the method’s result. On the canvas a return is titled EXIT. Place one from the return row in the flow-control actions; it comes with a value pin of the method’s return type, or none in a void method.
| Pin | Direction | Type |
|---|---|---|
| exec | Entry output | exec |
| each parameter | Entry output | Declared parameter type |
| exec | Return input | exec |
| value | Return input | Declared return type, omitted for void |
This snippet is a short illustration written for this page.
Guide: Return and throw.
Branch
Section titled “Branch”Purpose. Branch chooses the true path or false path from a Boolean condition. The node is titled BRANCH and is placed from the branch row. An else if chain appears as branches connected through false paths.
| Pin | Direction | Type |
|---|---|---|
| exec | Input | exec |
| condition | Input | bool |
| true | Output | exec |
| false | Output | exec |
This snippet is a short illustration written for this page, using the sample’s Coin type.
Guide: Branch.
Start with From to. A for node counts through positions with first index, last index and step inputs, plus the current index output. This compact view makes the common “repeat for these numbers” case easy without writing a condition or update expression. A bound can be a literal or a wired value such as collision.contactCount.
Select the node and use Loop > Loop type in the right rail.
Advanced: C-Style. This view exposes the general C# for structure: initializer, Condition when present, and iterator. It exists so the simple counting UI does not restrict more complex C# loops, such as a compound stop condition or multiple loop variables. Recognized ranges offer both views; other source loops offer only C-Style.
Other loop nodes. foreach visits a collection’s items; while checks before each pass; do while checks after the body and therefore runs at least once.
| Pin | Direction | Type |
|---|---|---|
| exec | Input | exec |
| condition, first index, last index, step, or array | Input | bool, numeric, or collection type |
| loop body | Output | exec |
| initializer / iterator | Output | exec, C-Style for only |
| completed | Output | exec |
| index or item | Output | Loop variable type, when the loop declares one |
Guide: Loops.
Switch
Section titled “Switch”Purpose. Switch routes one value into labeled arms. A switch statement is titled by its selector with SWITCH on the right; it continues through the chosen case and then leaves through the completed path. A switch expression produces a value instead and lists its arms as rows of a decision table.
| Pin | Direction | Type |
|---|---|---|
| exec | Input | exec, statement switch only |
| selection | Input | Switched value type |
| each case, and default | Output | exec, statement switch only |
| completed | Output | exec, statement switch only |
| result | Output | Inferred result type, switch expression only |
Guide: Switch.
Try catch
Section titled “Try catch”Purpose. Try catch keeps normal work, one or more exception handlers, an optional finally, and the continuation visible as one scope. Catch filters add a Boolean gate to a handler.
| Pin | Direction | Type |
|---|---|---|
| exec | Input | exec |
| try | Output | exec |
| each catch | Output | exec |
| exception | Output | Declared exception type, when named |
| finally | Output | exec, when present |
| completed | Output | exec |
This snippet is a short illustration written for this page, using the variables of the sample’s PlayerController.
Guide: Try, catch, and using.
Purpose. Using marks a using statement that owns a disposable resource for one scope. The node shows the resource input and output, a body path, and an exit path for flow after the scope.
| Pin | Direction | Type |
|---|---|---|
| exec | Input | exec |
| Body / Exit | Output | exec, for the scope body and the statement after it |
| resource | Input and output | the disposable resource, named for its declared variable |
This snippet is a short illustration written for this page, using the logger of the sample’s PlayerController.
Guide: Try, catch, and using.
Placeholder
Section titled “Placeholder”Purpose. Placeholder marks a statement or expression the parser cannot represent safely. It is gray and keeps the source text or diagnostic visible. It is a stop sign, not an approximation.
| Pin | Direction | Type |
|---|---|---|
| exec | Input | exec, when the unsupported shape is a statement |
| exec | Output | exec, when flow can continue visibly |
| diagnostic value | Varies | wildcard when no safe type is known |
This snippet is a short illustration written for this page, placed on the sample’s ScoreCounter.
A method with a non-design placeholder refuses Compile. Fix the marked construct in C#, then press the reload icon in the top rail (tooltip: “Re-run the Round Trip parse, adapter, and render pipeline for the active method.”) and continue only after the placeholder is gone.
Guide: When it refuses.