Nodes: action blocks
Updated
Block entry, calls and early returns. Create a block from a connected fragment and choose it by name in the call Inspector.
How to use
- An Action Block does not start just because it is on the graph. It needs a Call Block or an automatic-check assignment.
- Call Block waits for the fragment and provides its results. Check parameters, target and external continuations.
- Block Return ends the current call; skipping the protected action is only valid in an automatic Before check.
Expand a node for its inputs and results. Some fields appear only in the relevant Inspector mode.
Action Block
A named reusable group of nodes. Runs only when called and inherits the caller's window; does not start independently with the scenario.
Inputs, outputs and identifier
flow.block_start
Inputs: Timeout ms — whole number
Results: GameWindow — window
Continuations: Body
Call Block
Run an existing action block, wait for all its work to finish, then continue with this chain.
Inputs, outputs and identifier
flow.call_block
Inputs: Block — whole number; GameWindow — window
Continuations: Out
Block Return
Finish the current block early. In a Before check, you can also skip the protected action without skipping the next window.
Inputs, outputs and identifier
flow.block_return
Inputs: Return Action — text