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

Three ways in

Build a game from nothing, check code an AI wrote, or bring in scripts from anywhere and work with them visually.

You can start from an empty project, from a script an assistant just wrote, or from code you got from somewhere else. Round Trip supports all three without asking you to convert the codebase or learn C# punctuation first.

Examples of the three starting points

Select a screenshot to enlarge it.

Movement Update visual script: the white exec wire runs from Update to Translate. Three pills feed one MULTIPLY, whose result reaches Translate through a to Vector3 pill.
Build: a moving character The first-class tutorial builds this visual script. Each frame it moves the square by the direction from the Move control times speed and time.
StompEnemy with an early EXIT and separate score and HUD branches.
Figure 1. Review: check every route The AI-review tutorial uses this existing sample method as a review exercise, not as evidence of an AI edit. Follow the stop before the state change and bounce.
OnCoinCountChanged with ShouldUnlock feeding a local and a final door branch.
Figure 2. Understand: trace a rule The class-reading tutorial follows this separate method. Trace coinCount and threshold into ShouldUnlock, then its answer into the final branch.

Use this route when no source file holds the behavior yet. The short example below creates a CoinAnnouncer component with an AnnounceCoin method that logs a message. It is a building block, not a playable game. Start in a practice project with an indexed source folder.

Build a class and a method on the canvas

  1. Create the class

    Open Tools > Round Trip > Graph view. Press + beside the class chip, name the class CoinAnnouncer, choose MonoBehaviour and press Create.

    Clip: in the Graph view, the plus beside the class chip, the name box, the MonoBehaviour card and the Create button of the Create new class window are highlighted in turn with an arrow pointing at each. CoinAnnouncer is typed as the name.
  2. Add the method

    Press + on the Methods header, type AnnounceCoin and press Enter.

    Clip: the plus on the Methods header is highlighted with an arrow pointing at it. It adds a row in edit mode, then the row's name box is highlighted while AnnounceCoin is typed and committed. An AnnounceCoin entry node appears on the empty canvas.
  3. Log a message and Compile

    Right-click the empty canvas, search Log and choose the call. Drag the entry node’s white Exec pin to the Log node’s Exec input. Click its message pin and type "Hello from Round Trip", quotes included. Then press Compile at the left of the top rail.

    Clip of the whole Graph view: right-clicking the empty canvas opens All actions and Log is typed. The Log row, the entry node's Exec pin, the Log node's Exec input and the message pin are highlighted in turn with an arrow pointing at each. The message pin takes the quoted text Hello from Round Trip. Finally the Compile button at the left of the top rail is highlighted with an arrow pointing at it as the pointer presses it.

Continue with Your first class for the full click-by-click exercise.

Use this route when an assistant has edited your scripts and you want to see what it did before you keep it. Commit before the assistant starts, so its work is the only difference you are reviewing and you have a known-good version to go back to.

Open the modified-classes button on the top rail (its tooltip reads Show modified classes.) and choose the class the assistant touched. Read the changed method as a diagram: follow guards, calls and value flow without relying on the assistant’s explanation. Compare the source file with your checkpoint using your version-control tool’s diff. If you reject the change, use that tool to restore the file.

The worked route is Check what the AI did.

Use this route when the code already exists: a tutorial script, a forum answer, an asset you bought, or a project you inherited. The example below uses ScoreCounter from the Platformer sample in a practice copy. Supported code can be changed on the canvas; Round Trip can refuse changes it cannot safely write.

Read a script you did not write, then change one value

  1. Add the source folder

    Select the sample’s Platformer/Runtime folder in the Project window and choose Assets > Round Trip > Add folder to Round Trip. Skip this step if you imported the Platformer sample, which adds the folder for you.

    In Unity, the Runtime folder in the Project window, then the Assets menu, its Round Trip item and the Add folder to Round Trip command are highlighted in turn with an arrow pointing at each.
  2. Open Graph view

    Choose Tools > Round Trip > Graph view. The Round Trip graphs window opens.

    The Unity Tools menu, its Round Trip item and the Graph view command are highlighted in turn with an arrow pointing at each, and the Round Trip graphs window appears.
  3. Choose the class

    Press Cmd/Ctrl+O to open the class picker, choose the Runtime scope and select ScoreCounter.

    The class picker opens. Its Runtime scope row and then the ScoreCounter row in the class list are highlighted with an arrow pointing at each, and ScoreCounter is chosen.
  4. Open the method

    In the left rail, select OnCoinCountChanged.

    ScoreCounter's OnCoinCountChanged is selected in the left rail, highlighted with an arrow pointing at it; the entry node connects to the first branch.
  5. Inspect the branch

    Click the first BRANCH to see its identity in the right rail.

    The ScoreCounter OnCoinCountChanged graph is open. The first branch and then its identity header in the right rail are highlighted; selecting the branch shows its details there.
  6. Tick the value and Compile

    Follow the branch’s true output to the first RefreshStatus call. Click its isGoalUnlocked box to tick it, then press Compile. Do this only in a practice copy and restore the original file afterwards.

    The first branch's true output reaches RefreshStatus with its isGoalUnlocked box unticked. That box and the pin label beside it, shortened to oalUnlocked, are highlighted with an arrow pointing at them.
    Clip: the isGoalUnlocked box on the first RefreshStatus call is highlighted with an arrow while the pointer ticks it. Then the amber Compile button in the top rail is highlighted with an arrow while the pointer presses it, and Compile starts.
    ScoreCounter.OnCoinCountChanged after Compile, laid out on two rows so no wire runs through a card. Compile is gray, the pending panel is gone and the first RefreshStatus call shows its isGoalUnlocked box ticked.

Continue with Read a class you did not write and Build it visually, then Compile.

Choose shared layout storage when the arrangement itself is useful review material. Shared layout and configuration files live under <Project>/RoundTrip; local files live under <Project>/UserSettings/RoundTrip and stay specific to one machine. Keep ProjectSettings/RoundTripSettings.asset in version control so the team uses the same include paths and storage scope.

The team workflow, including what to share and what to keep local, is in Work as a team.

Full-size image