Flow inputs and return values
Treat a flow graph as a callable procedure with a signature, argument bindings and results.
Entry defines the start and inputs
Entry is both the execution start and the input declaration. Select Entry and use Add Input on the node or in the inspector to define a name, type and default. Do not wire a legacy function-input node as a second independent execution start.
Bind arguments at the caller
Declare the signature
Add Target : Actor and Speed : Int in the child graph, then save. Explicitly define whether an empty Actor means fallback or failure.
Select the child graph
Choose it on a child-flow node or BDS Execution. The caller displays matching input pins and literal fields.
Supply arguments
Enter inline values, or connect matching variable/property/operation outputs. Connected literal fields become read-only.
Declare and consume results
Add a function Return and a result such as Result : Int. The call node exposes output pins and result-to-variable bindings. Consume returned values only after the child completes.
Defaults, literals and wires
| Source | Meaning |
|---|---|
| Parameter default | Used when this call does not override the value. |
| Call-site literal | A fixed value supplied by this caller. |
| Connected data pin | The connected source supplies a matching typed value. |
| Result storage | Keep a completed call’s result in a variable for later nodes. |
When a signature changes
Save the child graph, return to the caller and verify its updated pins and bindings. Renaming or changing types may invalidate existing wires; silently converting them would hide an error. In Play mode, apply changes to the selected runtime instance separately from saving the asset.