Storage and teams
Protect your game files before editing, then know which Round Trip files belong to the project, which belong to you, and how the editor shows source changes.
On this page
Your teammate changes a method. You move three nodes so the diagram reads from left to right. Those are different kinds of change, and Round Trip keeps them separate.
C# remains the source of behavior, and Round Trip edits those real script files. Diagram settings files remember how that source is arranged on the canvas. Project settings tell the whole team which code Round Trip should read and which patterns it should recognize. Preferences keep your own canvas comfortable.
Pages in this group
Section titled “Pages in this group”- Protect your game files: choose a version control, commit before Round Trip edits, and restore a file from a commit. Setup guides for Unity Version Control, Git and Backups.
- Layout and configuration files: what
.rt.jsonremembers, where Local and Shared storage put it, and what happens if you delete one. - Settings and preferences: the line between Project Settings > Round Trip and Preferences > Round Trip.
- Changes and history: modified classes, file actions, navigation history, and canvas edit history.
The short rule is easy to carry: commit ProjectSettings/RoundTripSettings.asset; commit the RoundTrip/ root only when your team deliberately shares diagram arrangements; leave UserSettings/RoundTrip/ to each person.

