SharpGraph

What a graph stores

SharpGraph expresses gameplay with blocks and generates C# built with the project. Graph documents use .rsg. Execution flow, values and object references are different connections; matching wire colors do not replace type checking.

Graphs support variables, functions, events, signals, branches, loops and asynchronous operations. You can keep other behavior in ordinary C#: both use the Reckfell API.

Open a working example

The engine's source examples include SharpGraphQuickStart. If your distribution does not contain it, that does not imply an available Asset Store download: the store has not launched.

1. Open the example's project.reckfell with the project manager.
2. Open Kits/GettingStarted/Example.rscene.
3. Select the FirstSteps root and open its SharpGraph behavior resource in Inspector.
4. Find Start → Set UI text → Wait → Set UI text.
5. Change Delay or a text parameter, save and run the scene.

The first label should change to the second after the delay. If it does not, check the running scene and its assigned behavior.

Create a behavior

Select an object, use Connect SharpGraph if the project is not configured, then Create Graph…. Save the .rsg inside the project. Open the compatible-operation search from an execution output to continue the chain.

A known first-creation issue remains for a new Control: its graph can save without automatically attaching the behavior host. Check Inspector after creation. If no behavior is assigned, creation is not complete; use the already attached example for an introduction. A fix for this case is not confirmed.

Choose value blocks with matching types. Connect separate execution outputs for branches. A continuation after a wait must follow that operation's completion; an unrelated wait block does not delay another execution chain.

Convert to editable C#

1. Graph + C# shows generated code beside the blocks.
2. Convert to C# creates separate files in Scripts/Behaviors, builds the project and opens the result in the IDE.
3. Use C# Behavior transfers parameters and references to a C# component. Save the scene after replacement.
4. Run it separately and compare its behavior with the graph version.

The source graph remains available and Undo can reverse the replacement. Repeated conversion produces a new copy and retains the earlier result. Subsequent handwritten C# edits do not synchronize back into .rsg. Converting arbitrary handwritten C# back into a graph is not a supported completed workflow.

Debug and organize

Use breakpoints and stepping to inspect the actual execution path and values. A breakpoint that never triggers can indicate that the C# variant is running after replacement, or a different scene is active. Detailed Debug tracing is not part of Release builds.

Extract repeated logic into functions, label meaningful regions and use clear parameter names. Graph libraries and project resources are separate from the future asset store.

Continue with the built-in IDE, C# components and Entities and hierarchy.