Three ways in

You can start from an empty project, from a script an assistant just wrote, or from code you got from somewhere else. Round Trip supports all three without asking you to convert the codebase or learn C# punctuation first.

Build the game without writing code

Use this route when the behavior exists in your head but not in a source file yet. You will make a class and a method from the Unity menus, build the body on the canvas, and Compile ordinary C#.

1. In the Project window, select the destination folder and choose Assets > Round Trip > New Class. Name the class and choose its kind, access and parent type.

2. Select the new class and choose Assets > Round Trip > New Method. Set the method name, access, return type and parameters. Round Trip previews the source-backed method as a draft.

3. Open Tools > Round Trip > Graph View, select the class and method, then build the body on the canvas. Add calls from the action menu, wire values into their data pins and connect the white exec pins in the order they should run.

4. Read the Previewing your changes. banner, then press Compile. Round Trip writes the class and method to C#, imports the file and opens the graph parsed from that source.

Continue with Your first method for the full click-by-click exercise.

Check what the AI did

Use this route when an assistant has edited your scripts and you want to see what it did before you keep it.

Open the modified-classes button on the top rail (its tooltip reads Show modified classes.) and choose the class the assistant touched. Use Diff against HEAD on the method row to see the source change, then read the method as a graph. Guards, calls and value flow become visible without trusting the prose that came with the edit. If the method is wrong, Revert Method restores that method from the baseline.

The worked route is Check what the AI did.

Use code from anywhere

Use this route when the code already exists: a tutorial script, a forum answer, an asset you bought, or a project you inherited. Add its folder and read it as a graph before you change a thing. Once it parses, you change it on the canvas like code you built yourself.

1. In the Project window, select the folder that owns the scripts and choose Assets > Round Trip > Add Folder to Round Trip. The folder becomes an indexed source root.

2. Open Tools > Round Trip > Graph View. Use the Explorer to pick a class, then choose one method. Start small: a collision handler, score update or state change is easier to trace than the largest manager in the project.

3. Read from the entry node along the white exec wires. Follow colored data wires back to literals, parameters and GET pills. Select a node when you need its full identity in the right rail.

4. Change one thing, such as a literal on an unwired pin. Confirm that the draft banner names pending work, press Compile, then inspect the re-parsed graph.

Continue with Read a class you did not write and Change it visually, then Compile.

Work as a team

Choose shared layout storage when the arrangement itself is useful review material. Shared graph configuration lives under <Project>/RoundTrip; local configuration lives under <Project>/UserSettings/RoundTrip and stays specific to one machine. Keep ProjectSettings/RoundTripSettings.asset in version control so the team uses the same include paths and storage scope.

The team workflow, including what to share and what to keep local, is in Work as a team.

Next

• Your first method: build gameplay without writing code.
• Check what the AI did: review a source change through diff and graph.
• Read a class you did not write: bring in existing code and read it as a graph.
• Work as a team: choose shared or local graph configuration.