Glossary
The words Round Trip uses for C# source, visual scripts, diagrams, controls and building blocks.
On this page
Use this glossary to connect the words in these guides with what you see in the editor. A diagram is also called a graph; a visual script is the method you read or edit through that diagram.
One of six commands, Align top, Align bottom, Align left, Align right, Align middle and Align center, that moves every selected node onto the primary node’s matching edge or center line. The primary never moves. Reachable from the node menu, the toolbar Align list, or Shift with W, S, A, D, M or C.
Backing field
Section titled “Backing field”The private field behind a property. A variable switched to Property and also Shown in the Inspector is written as a field-backed property, [SerializeField] private float _speed; and public float Speed { get => _speed; set => _speed = value; } (with Setter set to None, public float Speed => _speed;), and the Variables rail lists the pair as one variable. A variable already in the script can be switched to Property the same way. How the field is named (_speed, m_Speed, speed) is set under Naming in Project Settings > Round Trip; see Change how backing fields are named.
Baseline
Section titled “Baseline”The version-control revision the modified-classes list compares against. It is HEAD, your last commit, unless Project Settings > Round Trip sets another revision.
Blueprint
Section titled “Blueprint”Unreal Engine’s visual scripting system. Round Trip borrows its canvas vocabulary: white exec wires for order, colored data wires for values, pure nodes without exec pins. The difference is that a Round Trip diagram is a view of a C# method rather than a separate asset.
Branch
Section titled “Branch”A flow node with true and false execution outputs. It corresponds to a C# if, with an optional false path for else.
Canvas
Section titled “Canvas”The center of Round Trip graphs, where the selected method appears as nodes connected by pins and wires.
Comment popup
Section titled “Comment popup”A note opened from the comment marker on a node or pill. It shows comments from the C# source. Other node tools may call this a node comment.
Compile
Section titled “Compile”The action that checks your visual draft and writes supported changes to C#. Until you Compile, the draft stays separate from the source file.
Data pin
Section titled “Data pin”A typed input or output carrying a value. Its color follows the value type. Other node tools may call it a value port.
Diagram
Section titled “Diagram”The visual view of a method: nodes show its operations, white wires show execution order, and colored wires show the values they use. Also called a graph. See Visual script for the connection to C#.
A visual edit that has not been written to C# yet. The Previewing your changes. banner marks this state.
Entry node
Section titled “Entry node”The start of a method’s diagram. It exposes method parameters and the first exec output. Other node tools may call it a start node.
Exec pin
Section titled “Exec pin”An execution input or output that carries ordering. It does not carry a data value. Exec wires are white.
Explorer
Section titled “Explorer”The class and member browser in the left panel. It lists the classes in your chosen source folders, along with their methods and variables.
A read of a field, property, local, parameter or other value. A compact member read is usually shown as a pill.
A technical term for nodes and their connections. These guides usually call the visible view a diagram or refer to the method as a visual script. The editor window is named Round Trip graphs, and implementation names such as MethodGraph use the technical term.
Graph configuration file
Section titled “Graph configuration file”A .rt.json file containing arrangement and view choices. It records where each node sits and how the viewport is framed. It also keeps wire knots and collapse state, and where comment popups sit. It describes how the diagram looks. It does not store the C# source and does not replace the file that produces it.
Hollow pin
Section titled “Hollow pin”An unwired pin with no value yet. Other node tools may call it an unset socket.
Identity header
Section titled “Identity header”The top of the right rail. It names the selected method or member and shows metadata in the form kind · access · returns.
Include path
Section titled “Include path”A folder Round Trip indexes for C#. Classes under an include path appear in the Explorer; everything else is left alone. Set in the Setup Wizard, Assets > Round Trip > Add Folder to Round Trip, or Project Settings > Round Trip.
Input action
Section titled “Input action”A named thing the player can do, such as Jump or Move, in Unity’s Input System. Its bindings are the keys and buttons that trigger it, and it lives in an actions file, usually InputSystem_Actions. A Player Input set to Send Messages calls a method named On plus the action’s name. See Your first class.
Inspector
Section titled “Inspector”The right rail: the identity header for the selected class, method, member or node, with a card for each part: comment, inputs and outputs, guards, defaults, pending changes.
Lifecycle method
Section titled “Lifecycle method”A method Unity runs by itself at a fixed moment, found by its exact name: Awake when an object appears, Update on every frame, FixedUpdate on every physics step, OnTriggerEnter2D when another object enters this one’s trigger area. Every behavior in a game starts at one; other methods run only when something calls them. The Lifecycle section of the left rail lists them, and their names are locked. Unity’s manual calls them event functions. See Lifecycle methods.
Literal
Section titled “Literal”An inline value box on an unwired data pin. It holds a source value such as a number, Boolean, string, vector component or object reference. The box is outlined in its pin’s color. On a pin that takes any value, such as a Log call’s message, what you type decides the type: "hello" is text, 5 a whole number, 1.5 a decimal number and true a yes-or-no. A decimal number typed into a float pin is written with the f C# needs. See Pills and literals.
Modified classes
Section titled “Modified classes”The top-rail button listing classes whose files differ from the baseline. It is where you start when an assistant or a teammate changed code you want to check.
A box on the canvas with a colored header and pins, standing for a call, statement, expression or control-flow construct.
A compact GET read node for a field, property, local, this or static value. It can fan one read to several consumers. A member chain read off a call’s result, such as collision.GetContact(i).normal.y, is one pill: y, with normal in its eyebrow, on the call’s return wire.
A connection point on a node. Pins are either exec pins or typed data pins. Other node tools may call them ports or sockets.
Placeholder node
Section titled “Placeholder node”A gray node for a source construct Round Trip cannot safely represent. A non-design placeholder refuses Compile so the unsupported code is not silently lost.
Player Input
Section titled “Player Input”The Unity Input System component that connects an actions file to a GameObject. Set to Send Messages, it calls OnJump, OnMove and the other On… methods on that GameObject’s components when the player uses a control. Round Trip adds one when you add a player control, and reads the saved ones to fill the picker’s INPUT sections. See Lifecycle methods.
Primary node
Section titled “Primary node”With two or more nodes selected, the node that was added to the selection last: by a Shift-click or Cmd/Ctrl-click, or the node nearest where a selection box was started. It keeps the blue ring while the other selected nodes wear a light gray one, and the align commands measure from it.
A side panel around the canvas. The left rail contains the Explorer and members. The right rail contains the identity header and inspector cards.
Return node
Section titled “Return node”The method exit that supplies a return value when the method has one. The return row under flow control in the canvas menu places one, with a value pin of the method’s return type when the method returns a value. Other node tools may call it an exit node.
An impure node that assigns a field, property, local or member value. The variable’s name is the left label of its header and SET is the keyword on the right. Its value input pin and its passthrough output pin are both labeled Value. Only the SET for the statement that declares a local with a computed value has a quiet second line under the name, reading local and the type, such as local Vector2.
Source
Section titled “Source”The C# file Round Trip parses and writes. Source is authoritative; the diagram is a view of it. It is the real script file in your project, so a change Round Trip writes there is a change to your game.
Switch arm
Section titled “Switch arm”One case or default route of a switch statement or switch expression. Each arm holds its own match and result or execution body.
Steps back the open method’s canvas edits that have not been saved yet; Redo puts them back. The history clears when Compile saves, when you open another method, and when the window closes, so Undo is not a backup. See Protect your game files.
Visual script
Section titled “Visual script”A method you read or edit visually through nodes and wires. In Round Trip it is a view of real C#, not a separate script format. A visual edit remains a draft until Compile writes it to the source file.
A connection between pins. White exec wires show order. Data wires take the color of their type and show value flow. Other node tools may call them edges or links.
Wire knot
Section titled “Wire knot”A small square on a wire, in the wire’s color, that the wire passes through. Double-click a wire to add one, drag its ring to bend the wire, or drag from its center to branch a new wire that shares it. A knot is layout and never changes what the C# means. Other node tools may call it a reroute node or reroute point. See Wire knots.
- Nodes, pins, and wires: see the vocabulary on a real method.
- Colors: map node families and data types to their exact colors.
- C# is the truth: place source, drafts and diagram layout configuration in the full loop.


