Storage and teams
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 graph reads from left to right. Those are different kinds of change, and Round Trip keeps them separate.
C# remains the source of behavior. Graph configuration files remember how that source is arranged on the canvas. Project settings tell the whole team what Round Trip should index and recognize. Preferences keep your own canvas comfortable.
Pages in this group
Section titled “Pages in this group”- Graph 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 graph edit history.
The short rule is easy to carry: commit ProjectSettings/RoundTripSettings.asset; commit the RoundTrip/ root only when your team deliberately shares graph arrangement; leave UserSettings/RoundTrip/ to each person.