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

Layout and configuration files

See what .rt.json remembers, where Local and Shared storage put it, and why the file never sits beside your C#.

You tidy a busy method until the branch, its calls, and the EXIT node all fit in one glance. Round Trip remembers that arrangement in a small file of its own, kept apart from your scripts, so the next time you open the method the nodes are where you left them.

Where a node sits on the canvas is a reading aid; it does not change what the game does. Round Trip keeps it out of your .cs scripts and stores it in one .rt.json settings file per class, inside one central folder. The script still decides every node and every wire.

Read this page when you decide whether your canvas arrangement should travel with the project, when you find an unfamiliar .rt.json file in a review, or when you want to clear your own saved layout.

A diagram settings file remembers:

  • Where each node sits in each method.
  • Where the canvas was scrolled to and how far it was zoomed.
  • Wire knots and the routes of wires bent around them.
  • Which shared pills you split into their own pills.
  • The size of each comment popup.
  • How each loop node is shown (From to or C-Style) and which switch cases are collapsed.

Deleting the file loses only that arrangement. Reopening the method lays its nodes out again automatically, with the same nodes and wires, though a value with a long read wire may come back as a separate pill beside the distant nodes that use it.

Local and Shared are arrangement choices

Select a screenshot to enlarge it.

Project Settings has Layout Scope set to Local beneath the actual Include Paths. The Layout scope dropdown is highlighted, with an arrow pointing down at it.
Figure 1. Keep your layout local Local stores canvas arrangement under UserSettings/RoundTrip. Leave it selected when teammates should arrange diagrams independently.
The same real settings provider has Layout Scope set to Shared. The Layout scope dropdown is highlighted, with an arrow pointing down at it.
Figure 2. Choose Shared deliberately Shared puts diagram settings under the project’s RoundTrip folder. Commit those arrangement files only when your team wants to review them.
A real method routes its gameObject wire through a small square knot below the Log call cards.
Figure 3. Recognize an arrangement-only edit A wire knot changes the route you read on the canvas. Its position belongs to diagram settings; it does not add a gameplay statement.

The Layout Scope dropdown picks one of two folders. Both hold files in the same format:

Layout Scope Folder Intended use
Local, the default <Project>/UserSettings/RoundTrip Your own arrangement on this machine. Unity leaves UserSettings/ out of version control by default.
Shared <Project>/RoundTrip An arrangement your team reviews and shares on purpose.

Round Trip never writes a diagram settings file next to a script.

Choose and find your layout storage

  1. Open Project Settings

    In Unity’s menu bar, open Edit > Project Settings and click Round Trip in the list on the left.

    Project Settings just opened on Round Trip, with a note above Source Indexing that these settings should be shared with the project.
  2. Leave Layout Scope on Local

    Scroll to the Layout storage heading. Leave Layout Scope on Local to keep the arrangement to yourself.

    The Layout Storage heading with the Layout Scope dropdown highlighted, with an arrow pointing at it, reading Local.
  3. Choose Shared only when your team wants it

    Open the dropdown and choose Shared only when your team wants canvas arrangements reviewed with the project.

    The same Layout Storage heading with the Layout Scope dropdown highlighted, with an arrow pointing at it, now reading Shared.
  4. Rearrange the canvas

    Open Tools > Round Trip > Graph view, open a method, and drag a node to a new spot, add a wire knot, or resize a comment popup.

    FlowExamples.UnlockGoal with its UnlockGoal node highlighted and, on the white exec wire between the entry node and BRANCH, a small square wire knot highlighted with an arrow pointing at it.
  5. Find the saved file

    In your file browser, open the folder for the scope you chose.

    The real .rt.json layout sidecar's text: format roundtrip.graph-layout, its source relativePath, and the UnlockGoal method's saved node positions.

The folder path below the scope’s folder follows where the script lives:

Script lives under Path below the scope folder
Assets/ The same path as inside Assets/, with nothing added.
Packages/<package-id>/ Starts with Packages/<package-id>/.
A configured external folder Starts with External/<stable-root-id>/.

The stored script path never holds a full machine path. External folders use a stable, cleaned-up id so teammates can check the project out somewhere else.

The file is plain JSON holding stable ids and numbers for positions and sizes. Treat it as editor-managed data. When one appears in a review, the useful question is whether the team meant to share that arrangement.

When it goes wrong

SymptomCheckFix
A teammate never sees your arrangement.Open Project Settings > Round Trip and read Layout Scope under Layout storage.Choose Shared only if the team wants to share arrangements, then commit the matching file under <Project>/RoundTrip.
A configuration file appears in a package or script folder.Check the file path. Round Trip never stores one beside a script.Choose the intended Layout Scope and move a node so Round Trip saves again.
A method opens with its nodes rearranged.Look for the class's .rt.json file in the scope folder.Restore the file if the arrangement mattered, or keep the new automatic layout.
An external folder produces a different path than expected.Check the configured folder id and its include path.Keep the folder id the same for everyone on the team.
Full-size image