Learn by doing
Build one class, read unfamiliar code, make a visual change, review generated work, and share the same C# with a team.
On this page
Start with the job in front of you. Round Trip can begin with an empty project and no code, with a script an assistant just wrote, or with code you got from a tutorial, an asset, or a teammate. Each tutorial finishes at ordinary C# in your project.
Most of these pages walk through the Platformer sample, a sample from the optional Round Trip Sample - Platformer package and that you import into a test project, so every step names a real class. The same steps apply to any project once its folder is indexed. A test project is the safest place for a first try; when you follow a tutorial in your real game, protect it first.
Tutorials
Section titled “Tutorials”- Build it visually, then Compile: the shortest way in. Build a tiny component that logs a message, change one input on the canvas, and save it as a small, reviewable source edit.
- Your first class: make a game behavior without writing code. Make a 2D scene with a square, create a Movement component, add a Move control and an Update method on the canvas so the arrow keys move the square, then add a Jump button that hops it.
- Check what the AI did: an assistant edited your scripts. Read the change as a diagram, compare it with your last checkpoint, and decide whether to keep it.
- Read a class you did not write: bring in code from anywhere. In the Platformer sample, trace a coin count into the branch that opens the goal.
- Work as a team: designers build on the canvas, programmers type C#, and both share the same source file.
Common shapes
Section titled “Common shapes”Six small methods from the Platformer sample cover the shapes you will meet most often in any project:
- Guard clause: leave early when a door should do nothing.
- Count and threshold: react when the coin total reaches its target.
- Switch on a state: give each enemy state its own route.
- Turn at the edge: choose left edge, right edge, or keep moving.
- Scan a list: inspect every collision contact.
- Call a neighbor: pass work from the player to scene components.
- Common shapes: pick a shape that matches your next gameplay rule.
- Guides: look up the canvas, flow, call, and Compile tools by feature.


