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

Choose your strategy

Pick the version control that fits your Unity project, commit before Round Trip edits your scripts, and know which setup guide to follow.

Round Trip writes to the real C# files in your project. Some actions write as soon as you confirm them, and Compile clears the canvas undo history when it saves, so a saved change cannot be undone from the canvas. Version control is what makes any change reversible: commit or check in before a session, and you can always get back to the version that worked.

Many solo developers get by without it. Once a tool, or an AI assistant, is editing your scripts, that stops being safe. The setup is one sitting; after that it is a check-in before and after each session.

Already using version control? Commit before you let Round Trip edit, then read What Round Trip adds.

Choose When Guide
Unity Version Control You have no version control yet. It is built into Unity Hub and the Editor, handles art and sound files without extra setup, and needs no command line. Unity Version Control
Git You or your team already use Git. Large files need Git LFS before they are first committed. Git
Diversion or Perforce Your team already uses one. Round Trip’s Changes list works with both; follow the vendor’s Unity setup. Diversion, Perforce

Whichever you choose, add a separate backup of the project’s source folders so a lost computer or repository is not a lost game. A backup is a second copy; it does not replace committing.

  1. Commit or check in before a Round Trip session, and before an AI assistant edits your scripts.
  2. After the session, open the Changes list in the top rail to see which classes changed, then commit again with a comment that says what works.
  3. If a change is wrong, restore the file from your last commit. Each guide’s Restore section shows how.

Commit ProjectSettings/RoundTripSettings.asset so the team indexes the same folders. Commit the RoundTrip folder only when the team shares layouts. Leave UserSettings out: it holds each person’s own layouts and last open method.

Changes and history covers the Changes list and the method menu step by step.

Review saved source changes

Select a screenshot to enlarge it.

The actual Changes list contains a modified PlayerController and its changed-method count. The Changes button in the toolbar and the PlayerController row are highlighted, with an arrow pointing at the button.
Figure 1. Find the changed class This example uses a real Git-backed source edit. Open Changes to choose the class you need to inspect. Other uncommitted work can appear in the same list.
The actual RefreshHud method has an M marker and its saved diagram is visible.
Figure 2. Open the marked method The M identifies a source change since the baseline. Read that method’s behavior, then review or restore the whole file with your version-control tools when needed.
Full-size image