Find the right node

Start with the job, not the color. Do you need to choose a path, call code, read or write a member, or produce a value? The reference pages group nodes by those jobs and put the corresponding C# beside each entry.

Four node families

Every card 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.

  • Branch
  • Loops
  • Switch
  • Try/catch
  • Return

• Calls

  Ask this class, another indexed class, or an external API to do work.

  • This class
  • Another class
  • External

• Data

  Read, write, create, and combine the values that travel through pins.

  • GET pill
  • SET
  • Literal
  • Operator
  • Expression

• Structure

  Mark where execution enters, returns, or reaches unsupported source.

  • Entry
  • Return
  • Placeholder

Read an entry

Every entry follows the same scan:

1. Purpose says why the node exists in a game method.
2. 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.
3. C# shows the source shape the node represents.
4. Guide links to the page that uses the shape in context.

Pure nodes omit exec pins because they produce values without owning statement order. Impure nodes take part in the white exec-wire path.

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.

Next

• Flow nodes
• Call and member nodes
• Data nodes
• Colors