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

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.

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.

Find the part you need to change

Select a screenshot to enlarge it.

The real project settings page lists a source include folder and Local layout storage. The Include Paths row and the Layout Scope dropdown are highlighted, with an arrow pointing down at the dropdown.
Figure 1. Shared project setup Start with Project Settings for source folders and storage. These choices are shared through ProjectSettings/RoundTripSettings.asset.
The real Preferences grid section contains the visual preview and snapping controls. The Snap to grid switch is highlighted, with an arrow pointing at it.
Figure 2. Your own canvas feel Use personal Preferences for the grid and other canvas behavior. A teammate can choose a different look without changing the game scripts.

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.

Full-size image