What you get
Tour the Explorer, canvas, authoring tools, Compile flow and layout files, with examples from the Platformer sample used across this site.
On this page
Round Trip gives you one Unity editor window for building gameplay without writing C# and for understanding C# that already exists, whether you, an assistant, or a stranger wrote it. Pick a class on the left, work on its method in the center, and inspect the selected thing on the right.
The Explorer
Section titled “The Explorer”The left rail indexes C# classes from the folders you choose. Open a class to see methods grouped by access, plus its variables, properties, events and other members. Selecting a method opens a diagram drawn from that method’s source.
Learn the class and member model in Explorer, then practice on unfamiliar code in Read a class you did not write.
The canvas
Section titled “The canvas”The center canvas turns a method body into nodes, pins and wires. White execution wires show order. Typed data wires show where values come from. GET reads can collapse into compact pills, while literals sit directly on unwired pins. The visual language is inspired by Unreal Engine Blueprint and goes further: because a visual script is plain C#, a method can be a Unity coroutine or an async method, with its yields and awaits drawn on the canvas.
Learn the visual language in Canvas and its control-flow shapes in Flow.
Authoring
Section titled “Authoring”You can create classes, methods, variables, defaults, lifecycle methods and enums. Inside a method, the action menu and pin gestures build calls, branches, loops, switches, assignments and supported expressions. Most of these changes begin as drafts, visible before they touch the file. A few write at once: creating a class writes its new script file, and adding a lifecycle method adds the empty callback to the script.
Learn the creation tools in Authoring, or build something immediately in Your first class.
Compile
Section titled “Compile”Compile is the explicit step that writes a draft into the real C# file in your project. Round Trip plans the narrowest source edit it can, replaces the file in one operation, asks Unity to import the change, then parses the file again. If it cannot represent a construct faithfully, it refuses and leaves the method unchanged. That care is not a way back: commit before you edit, as Protect your game files shows.
Learn that loop in Compile and try it end to end in Build it visually, then Compile.
Layout and configuration files
Section titled “Layout and configuration files”Files ending in .rt.json store the diagram’s layout and display choices: node positions, viewport, wire knots, collapse state and comment popup placement. They are never a second source language. Choose local storage under <Project>/UserSettings/RoundTrip or shared storage under <Project>/RoundTrip.
Learn what belongs in each scope in Layout and configuration files.
The Platformer sample
Section titled “The Platformer sample”The Platformer sample is a separate, optional package (Round Trip Sample - Platformer), a small playable 2D level whose scripts are the examples used across this site. Install it into an empty test project to learn with, and keep it out of your real game. Platformer explains how to get it, and the Platformer visual script tour walks through its showcase methods.
What it does not do
Section titled “What it does not do”Round Trip can parse more C# than it can safely write. Unsupported statements appear as gray placeholder nodes, and some declaration shapes are refused by name. Read what it does not do yet before planning a large conversion; the page pairs each current edge with the C# route you can use today.
- C# is the truth: understand the source and configuration boundary.
- Three ways in: build without code, check an AI’s edit, or bring in existing scripts.
- Platformer: how to get the Platformer sample and open its showcase visual scripts.


