POBDS / 12
SendEvent
Add this flow operation to an Action node. Configure the corresponding fields in the inspector, including event connections and completion policy.
Configuration
Parameters and pins
| Name | Type | Direction | Default | Meaning |
|---|---|---|---|---|
| EventName | String | configuration | "" | Required. Event name to send or match. |
| Delay | Single | configuration | 0 | Delay before starting; the common flow field uses seconds. |
| FlowAction.Delay | Float (s) | configuration | 0 | Delay before entering this Action, in seconds quantized to simulation milliseconds; separate from an Action-specific wait duration. |
| FlowAction.EveryFrame | Boolean | configuration | false | Continuous execution option; for example, keep invoking a method each frame. Unfinished Actions still receive Update; this does not force completion or repeat Enter. |
| FlowAction.FinishEvent | String | configuration | "" | Optional event when this Action finishes; empty does not prevent the node from emitting FINISHED once every Action completes. |
| FlowAction.FailEvent | String | configuration | "" | Optional failure event for this Action; connect error handling as needed. Interruption is not success. |
Output / result: See execution completion rules
Example
Entry → Action [SendEvent] → FINISHED → Return. Use FAILED for error handling. Enable continuous updates only where needed.
Completion and interruption
An Action node advances when all Actions finish. Exit also runs on interruption, but interruption does not emit a false success. Milliseconds, seconds and world units are not interchangeable.