Canvas

The canvas is C# arranged as a path you can trace. White wires carry execution from one statement to the next. Colored wires carry typed values. Cards do work; compact pills read values; inline literals hold values that have no wire yet.

The visual language is inspired by Unreal Engine Blueprint, widely regarded as the best visual scripting language in games, so the white exec wire, typed data wires and pin colors will feel familiar if you have used it. Round Trip takes it further. Blueprint graphs run largely on one thread; a Round Trip graph is plain C#, so a method can be a Unity coroutine or an async method, and the canvas draws its yield and await statements beside everything else. Those statements stay typed in C# today; everything around them is edited on the canvas.

Learn it in layers

• Nodes, pins, and wires: read card anatomy and execution flow, then learn data flow and the color vocabulary.
• Pills and literals: understand compact GET reads and consolidated consumers, along with inline values and object references.
• Variables: create GET and SET nodes from the Variables rail or by dragging a row.
• Layout, reroutes, and comments: arrange and align a graph without changing behavior while keeping source comments visible.
• Shortcuts: use the keyboard and pointer gestures across the Explorer and canvas.

Read before you rearrange

Start at the entry node and follow exec wires. At each card, pause only long enough to read the data wires entering it. A pure node has no exec pins, so trace its colored output toward the statement that consumes it. That rhythm keeps a large graph from turning into a wall of cards.

Layout changes and viewport state belong in .rt.json graph configuration files. Those files also hold reroute knots and split reads. Comment popup sizes stay there too. C# remains the source of behavior.

Next

• Nodes, pins, and wires: learn the canvas alphabet.
• Pills and literals: see where values come from.
• Flow: trace decisions and repetition.