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

Guides

Find the part of Round Trip you need, from reading a class to compiling a visual change back into C#.

A coin pickup, an enemy patrol, and a locked goal all look different in play. In Round Trip they share the same route: find the class, open a method, read or change its visual script, then Compile when you want the draft written to C#.

Each guide describes the steps for the classes and methods in your own project. Where an example helps, it names a class from the Platformer sample, a sample from the optional Round Trip Sample - Platformer package and that you import into a test project to learn with. Many guides end with Compile, which changes the real script files in the project you have open.

A quick route through the editor

Select a screenshot to enlarge it.

The real CollectCoin window has class members on the left, the method diagram in the middle and details on the right.
Figure 1. Find and read a method The Explorer guides help you get to the method. Canvas and flow guides explain the visible pins and paths once it is open.
The real CelebrateCoin draft shows Previewing your changes and the filled Compile control.
Figure 2. Recognize an unsaved change Authoring guides create or change a draft. Compile guides explain the separate step that writes it to your actual script.
  • Explorer: find classes and members, read their identity, and jump to source.
  • Canvas: understand nodes, pins, wires, pills, literals, layout, snap and align, and shortcuts.
  • Flow: read and build branches, loops, switches, exception paths, and exits.
  • Calls and data: connect method calls, GET and SET nodes, operators, arrays, tuples, ranges, enums, and data classes.
  • Authoring: create classes, methods, variables, defaults, lifecycle methods, guards, and renames.
  • Compile: preview drafts, see what gets written, and understand when Round Trip refuses.
  • Storage and teams: protect your game files, choose where layout and configuration files live, and inspect changes and history.
  • Architecture: see what ships in the Unity Asset and which C# constructs it supports.

Before you change anything, put the project under version control and commit; Protect your game files helps you choose a version-control tool. Start with Explorer if the code already exists. Continue through Canvas and Flow to learn how the diagram reads. Use Calls and data and Authoring when you are ready to change behavior. Finish with Compile and Storage and teams before sharing work.

  • Explorer: open a class and find the method you care about.
  • Canvas: learn the visual language in the middle of the window.
  • Flow: trace the paths your game can take.
Full-size image