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

Architecture

See how your C#, the Unity package source, the compiled engine, and the shared canvas fit together.

Your own C# files sit at the top because they own the game’s behavior. Round Trip reads and shows them, then writes narrow changes back to them when you press Compile. The diagram uses ScoreCounter.cs from the Platformer sample as the example file.

The Round Trip package architecture from Unity up to your projectThe architecture rises into a vertical stack. Your project sits on top. The Round Trip Unity package source and shared canvas sit below it. Compiled Engine and Core libraries sit above Unity. A request travels down from project source through the editor to the Engine, then returns as a diagram. The final frame distinguishes source layers from compiled layers.Your projectyour C# files · PlatformerScoreCounter.csio.bitquirky.roundtrip.engineUnity package sourceExplorer windowCanvas and rails (UI Toolkit)Indexer, menus, settingsio.bitquirky.graphshared canvasRoundTrip.Engine.dllRoslyn parserMSAGL layoutsource writerJSON layout storeRoundTrip.Core.dllgraph modelcompiled, not shipped as sourceUnity 2022.3+diagram readycompiledsourceThe Round Trip package architecture from Unity up to your projectThe architecture rises into a vertical stack. Your project sits on top. The Round Trip Unity package source and shared canvas sit below it. Compiled Engine and Core libraries sit above Unity. A request travels down from project source through the editor to the Engine, then returns as a diagram. The final frame distinguishes source layers from compiled layers.Your projectyour C# files · PlatformerScoreCounter.csio.bitquirky.roundtrip.engineUnity package sourceExplorer windowCanvas and rails (UI Toolkit)Indexer, menus, settingsio.bitquirky.graph · shared canvasRoundTrip.Engine.dllRoslyn parserMSAGL layoutsource writerJSON layout storeRoundTrip.Core.dllgraph modelcompiled, not shipped as sourceUnity 2022.3+diagram readycompiledsource
Your C# stays above the Unity integration, while Core and Engine provide the model, C# parsing, layout, storage, and source-writing work underneath.

The middle layer is the Unity package source: the Explorer, UI Toolkit controls, indexing, settings, menus, and host adapters under Editor/ and Runtime/. You can read and extend that integration.

Under it sit RoundTrip.Core.dll and RoundTrip.Engine.dll plus their dependencies. Core defines the model of methods, nodes, pins, and connections. Engine reads C#, lays out diagrams, stores JSON settings, supports visual editing, and writes source changes. Neither layer depends on Unity types.

Beside the Unity integration is the io.bitquirky.graph package, which supplies the shared graph canvas and, on Unity 2022.3, loads the package’s SVG icons from their source. com.unity.vectorgraphics supplies vector rendering support.

  • What ships: every package folder, plugin DLL, and dependency.
  • Supported C#: what you can work with visually, what has limits, and what you still edit in C#.
Full-size image