Skip to content
Bit Quirky Round Trip
Visual Scripting

Search documentation

All topics and APIs

Close returns focus to Search.

What are you looking for?

Try a common topic or a C# feature.

Browse the reference instead

Esc closes · Tab reaches results · Enter opens the focused link

v1.0.0
Menu

Data nodes

Read the pure expressions, literals, operators, conditionals, and null-aware values that feed statement pins.

Data nodes answer “what value?” They usually have no exec pins. Their colored wires feed branches, calls, returns, assignments, and other expressions without adding a separate step to the white execution path.

The C# under each entry comes from the Platformer sample unless it says otherwise.

Purpose. Produces a value without a separate step in the execution order. Member access, conversion, array or struct construction, tuple operations, string interpolation, and other value-producing shapes use pure nodes.

Pin Direction Type
operand or source values Input Shape-specific typed values
result Output Inferred or declared result type

Guide: Operators and expressions.

Purpose. Supplies a value directly. Eligible unwired data pins show an inline literal box; a separate literal node appears when the value is represented as its own source expression.

Pin Direction Type
value Output Literal type, such as int, float, bool, string, char, object, or struct

Guide: Pills and literals.

Purpose. Combines or transforms values. Binary operators have left and right inputs; unary operators have one input. Comparison and logical operators produce Boolean output.

Pin Direction Type
left Input Operand type, binary only
right Input Compatible operand type, binary only
value Input Operand type, unary only
result Output Operator result type

Operators cover arithmetic, logical work, comparisons, and supported casts or conversions. Each takes the color of its result, the same color as its result pin and wire: a comparison or logic node is Boolean red, whole-number math integer green. See Colors.

Guide: Operators and expressions.

Purpose. Chooses one of two values without creating statement branches. The condition input is Boolean, and both value arms must produce a compatible result.

Pin Direction Type
condition Input bool
when true Input Result-compatible type
when false Input Result-compatible type
result Output Inferred common type

Guide: Operators and expressions.

Purpose. Keeps null handling inside the value path. Null coalescing chooses a fallback value; null-conditional access stops member access when its receiver is null.

Pin Direction Type
value or target Input Nullable or reference type
fallback Input Compatible type, for ??
result Output Resolved result type

To add or change this handling, select the node or click its shield and use GUARDS in the right rail. Guards explains the null-safe and fallback choices without requiring C#.

Guide: Operators and expressions.

Purpose. Filters, sorts, reshapes or counts a collection as values on the canvas. Each operator is one node titled with its name, such as Where, Order By, Select or Count. A node with only a Result pin takes that result’s color, such as integer green for Count; one that also has an item pin, such as Where, stays Default Pure green because it has two results. The right side of the header reads LINQ for an operator that runs later, when something reads its result, and LINQ · RUNS NOW for one that runs where it stands, such as Count, To List or First. Hover the node for the full explanation.

Pin Direction Type
source Input The collection, an array or any sequence
condition, value or key Input What the operator asks of each item: bool for Where, any value for Select, the value to sort by for Order By
inner and count, among other arguments Input The second collection for Join, a number for Take or Skip
item (named after the item, such as coin) Output One element of the source, for the nodes that build the condition, value or key
result Output The new sequence, or the single value an operator that runs now returns

These snippets are short illustrations written for this page, placed on the sample’s ScoreCounter. Both spellings, the chain of calls and the from ... where ... select query, give the same nodes, and an edited query is written back in the spelling it came in. A block-bodied lambda falls back to call and lambda nodes rather than a LINQ node with a drawn body. A static expression-bodied lambda can show a gray Lambda body placeholder and block Compile; edit that lambda in C#.

Guide: Scan a list.

Full-size image