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

Authoring

Create classes, methods, and variables visually, and choose how they are declared in C#.

On this page

A blank script is still a design problem: what owns the behavior, what values does it keep, and when does Unity call it? Round Trip gives those decisions their own focused controls.

Most authoring changes begin as drafts. You can inspect the diagram and preview the C#, undo mistakes, and use Compile as the explicit point where the draft becomes C# in your real script files. A few actions write to your scripts at once, without waiting for Compile: pressing Create on a new class writes its script file, adding a lifecycle method adds the empty callback, and confirming Delete method removes the method from its script.

Recognize the class, method and Lifecycle authoring controls

Select a screenshot to enlarge it.

The New class window with an empty NAME field, Runtime location and parent class cards.
Figure 1. Create the home for a behavior The New class window chooses the script location and parent. The plain class card is selected here; choose MonoBehaviour when the script belongs on a GameObject. Create writes a file immediately.
CelebrateCoin drafted in PlayerController with one entry node, a lit Compile button and Previewing your changes in the right rail.
Figure 2. Recognize a method draft A separate example on PlayerController: CelebrateCoin is not in the C# yet. The highlighted Compile button and pending-changes panel distinguish a draft from saved source.
PlayerController Lifecycle section shows its four existing callbacks and a + beside the header.
Figure 3. Find the separate place for Unity events Lifecycle is above Methods so the starting points are easy to find. Use its own + for another recognized callback, rather than creating a helper with a name of your own.
The Add lifecycle method picker offers Start and other unimplemented events under CORE, with a filter at the top.
Figure 4. Choose when Unity should call the script This existing PlayerController example offers callbacks the class does not have yet. Selecting one writes its empty C# declaration immediately; the canvas work is saved with Compile.
  • New class and method covers the Assets > Round Trip > New class and Assets > Round Trip > New method windows, and the + buttons that do the same inside the Round Trip graphs window.
  • Fields and defaults shows how variables (fields and properties), their starting values, and the dedicated default-value canvas fit together.
  • Lifecycle methods explains when Unity runs a script, why those starting points sit above Methods in their own left-rail section, and how to add one, including methods that run when the player presses a control. Use the quick event reference or build a working spike step by step.
  • Guards keeps prerequisites and null handling in the right rail so the canvas stays focused on the game’s work. Guard rules configures shared defaults and custom patterns in Project Settings.
  • Rename changes a method or variable name through the right-rail header while source stays untouched until Compile.

These tools do not hide C#. Each set of authoring controls offers only changes that can be written faithfully. If a declaration or method body cannot be written safely, Round Trip names the reason and keeps the file unchanged.

Full-size image