Appearance
Scriptgraph fundamentals
Read signals and values separately
Follow signal connections to understand the order in which work starts. Then inspect the variables each action reads or writes. Finally inspect its properties: a correctly connected action can still be configured for a different behavior.
For example, TimerAction.Start begins a timer, StartTime supplies its duration, and OnTimeOut is the output used to continue when the timer expires. A variable connection to StartTime is not a start signal.
Use exact contracts
Node labels can be friendly descriptions. Action class names and pin names must match the installed catalog. Use the node reference rather than guessing a pin from the visual label.
Variables include boolean, float, vector, string, and actor values. Match the variable type to the pin. Actor handles must refer to the appropriate live actor or group for the action.
Listen at the right time
OnEventAction exposes StartListening, StopListening, and OnEvent. Its Target binding identifies the actor to watch when the selected event and action require one.
When a target comes from spawning, assign that live handle first, then enable listening. Document the selected event type and payload; an image of the connections alone does not show those settings.
Choose the specific event you want to listen for and configure its available properties.
Build in small steps
- Choose the real source of the first signal.
- Add one action and set its required properties and variables.
- Connect a visible outcome so you can see whether the signal arrived.
- Add completion, failure, and cleanup paths deliberately.
- Save and reopen the zone, then test the intended gameplay conditions.
The first scriptgraph illustrates a short sequence. Mission patterns shows how to combine these ideas.