Classes and members
Find a class, add or open a method, and move through its members from the Explorer rail.
On this page
A project can have a hundred classes. The left rail takes you from all of them to one method’s canvas in a few clicks.
What it does
Section titled “What it does”The Explorer, the left rail of the Round Trip graphs window, lists every class in the folders you include. Pick a class and the rail fills with its sections: Lifecycle for the Unity callbacks such as Update, Methods for everything else it can do, Variables for the values it keeps, and Local variables for the open method’s own values. Click a method and its diagram opens on the canvas. Click + on a section header and you add a new one.
The behavior you are after is often in a class you would not guess. Use the class picker, search across every member, or navigate with the keyboard to reach the right method without opening files.
Why Lifecycle is above Methods
Section titled “Why Lifecycle is above Methods”Start with Lifecycle when you are finding out what makes an object act. It lifts Unity’s recognized event methods out of the general method list so the usual starting points are easy to find, even in a large class. They remain methods in the same script, with the same canvas editing tools and Unity execution rules.
For example, PlayerController reacts to a trigger in OnTriggerEnter2D under Lifecycle, then calls CollectCoin under Methods to do the work. Other scripts and Inspector-connected events can also call methods; not every caller is a Lifecycle row. Lifecycle methods has a quick event reference and a step-by-step example.
When to use it
Section titled “When to use it”Use the Explorer whenever you start work on a behavior: to add a method to the player for collecting a power-up, to open the enemy’s Update and change how it patrols, or to find the method a teammate pointed you at by name.
The class list comes from the source folders included in Project Settings > Round Trip. Methods are grouped under PUBLIC, PRIVATE, and INTERNAL; protected ones join the internal group.
Why some properties appear in Methods
Section titled “Why some properties appear in Methods”Properties normally belong under Variables. If a property calculates a result or runs other behavior in a getter or setter, Round Trip moves it to Methods so you can inspect that behavior. Merely having get and set does not move a property: an auto-property or a simple wrapper around its own backing field stays with the stored values.
See Properties: Variables or Methods? for a screenshot walkthrough of God Complex’s GameMaster, the C# that causes each placement, and the distinction between opening an accessor and reading a property’s value.
A method with several versions that take different inputs shows as one row with a caret. Right-click it and choose Expand overloads to see each version. A behavior-bearing property with both accessors groups them similarly; choose Expand accessors to see its get and set rows.
Right-click menus
Section titled “Right-click menus”The class chip at the left of the top rail and every row in the Explorer have a right-click menu. What it offers depends on what you right-click:
| You right-click | The menu offers |
|---|---|
| The class chip | Copy class name copies the class’s name, such as PlayerController. Copy full name copies it with its namespace, such as RoundTrip.Platformer.Runtime.PlayerController. Open source opens the class’s script at its declaration, as Source on the right of the toolbar does. |
| A method row | Copy method name copies the method’s name, such as CollectCoin. Copy full path includes its namespace and class, such as RoundTrip.Platformer.Runtime.PlayerController.CollectCoin. Last is Delete method. |
| A row with a caret that groups overloads | Copy method name and Copy full path for the shared name, then Expand overloads or Collapse overloads. |
| A property row that groups get and set | Expand accessors or Collapse accessors. |
| A get or set row | View in source, which opens the script at that accessor. |
| A Lifecycle row | Override into this class on a callback inherited from a parent class that this class does not implement yet, and Delete method on a callback this class declares. |
The copied text is plain, so it pastes anywhere. The + beside the class chip has no menu, and the chip has none until a class is open.
What it looks like
Section titled “What it looks like”
How to use it
Section titled “How to use it”Open a class and move through its methods
Open the window
Open Tools > Round Trip > Graph view. The Round Trip graphs window opens with the Explorer on the left, the canvas in the middle, and the inspector on the right.
8 stepsFull size ↗Pick a class
Press Cmd/Ctrl+O to open the class picker. Type part of a class name, use Up or Down to move through the matches, and press Enter.
Add a method
Click + on the Methods header. A new row appears in the list as a name box holding
NewMethod. TypeCollectPowerUpand press Enter, or press Escape to keep the default name.Switch methods
Click another method row under PUBLIC or PRIVATE. If the method you are leaving has changes not yet compiled, an Unsaved changes dialog asks whether to save and compile. Yes writes them into the script first, the same as pressing Compile. No leaves without saving, which drops a method you never compiled.
Add a Lifecycle method
Click + on the Lifecycle header. The lifecycle picker opens. Pick a callback you want, such as Start.
Search for anything
Press Cmd/Ctrl+P, or click the search field at the right of the toolbar, and type the name of a method, input, or local. Pick a result and the window moves straight to it.
Move with the keyboard
Click a method row, then use Up and Down to move through the rail. On a row with a caret, press Right to expand it and Left to collapse it. Press Enter or Space on a method row to open it.
Delete a method
Right-click a method row and choose Delete method. In the dialog, click Delete.
Copy or open from the chip
Right-click the class chip at the left of the top rail and choose Copy full name. The class’s name with its namespace is on the clipboard. Right-click it again and choose Open source to open the class’s script at its declaration.
What it writes
Section titled “What it writes”Browsing writes nothing, and expanding or collapsing a group does not touch the script. A new method row is written into the class when you press Compile. If you also work in C#, an overload group is several declarations of one name, such as the three versions of Configure on the Platformer sample’s Door. The two shorter ones only pass null on to the longest, so Round Trip shows them as one Configure row: the right rail reads 2 defaulted overloads, and its PARAMETER DEFAULTS section lists the values each shorter version fills in.
Overloads that do their own work are separate versions instead: each is its own row once the group is expanded, and each opens its own diagram.
When it goes wrong
Section titled “When it goes wrong”When it goes wrong
| Symptom | Check | Fix |
|---|---|---|
| A class is missing from the picker. | Check whether its folder is included in Project Settings > Round Trip. | Add the source folder, then let the index refresh. |
| The method name is in the list, but the diagram you expected is not on the canvas. | Look for a caret on the row: it groups several versions of the method. | Right-click the row, choose Expand Overloads, and open the version whose inputs match. |
| A property row does not open a diagram. | Look for the caret and its get or set children. | Choose Expand Accessors, then open the get or set row. |
| The Methods section and its + are missing. | Look at the class chip in the top left: no class is open yet. | Press Cmd/Ctrl+O and open a class first. |
| Right-clicking the class chip shows no menu. | Check whether a class is open, and that you right-clicked the chip itself rather than the + beside it. | Open a class with Cmd/Ctrl+O, then right-click its name on the chip. |
- Identity and inspector: read and edit the selected method in the right rail.
- Navigate to source: jump from a diagram to its script and back.
- Nodes, pins, and wires: place the first nodes on your new method.









