Event Track

Event Tracks support the creation of custom events that are scripted in a dedicated Sequencer Blueprint layer.

Choose your operating system:




In Sequencer, you can define frames in your sequence where you want to execute Blueprint Scripting functionality. This is accomplished using the Event Track.

This guide provides an overview of the Event Track, including how to create it, access the Director Blueprint, and the types of events you can create.



To create an Event Track, click the Track (+) dropdown in Sequencer, navigate to Event Track, and select either the Trigger or Repeater event type.

create event track

Event Tracks can also be created under an Object Binding Track, which will bind the event to that object.

create event track actor

Once an Event Track is created, you can create additional event Sections by clicking the Section (+) dropdown on the Event Track and selecting an event type.

add more event tracks

When adding events, you can choose to add either Trigger or Repeater type events. Trigger Events cause an event to evaluate on the same frame as the keyframe, whereas Repeater Events will evaluate for each frame for the duration of the event section.

Trigger Events

Trigger events are events that evaluate once per keyframe. When this track is created, you can then Keyframe it to create event keyframes.

trigger event

Repeater Events

Repeater events are events that will fire or evaluate for each frame of the sequence continuously for the duration of the event section. Adjusting the Frames Per Second of the sequence will also adjust the evaluation rate of the repeater to match. When this track is created, it will contain a finite Section range, controlling its evaluation time.

repeater event

You can Edit, Move, and Trim this event section just like any other section in Sequencer.

Director Blueprint

The Director Blueprint is the logic center for the Event Track from which you will perform Blueprint Visual Scripting from your event endpoints. Parameters and Object Bindings can also be specified in the Blueprint in order to pass variable and object information throughout the script. Each Level Sequence has its own Director Blueprint, containing all the logic for the events in that sequence.

There are several ways you can open the Director Blueprint:

  1. Double clicking an event keyframe or section. This method will also bind the event to a new endpoint if it is currently unbound.

    double click event

  2. Clicking the Director Blueprint Toolbar button.

    director blueprint toolbar button

  3. Clicking the Actions Toolbar button and then selecting Open Director Blueprint.

    open director blueprint

Event Endpoint

Regardless of whether a Trigger or Repeater event is created, you must bind it to an Event Endpoint in order to add logic to it. To do this, right-click the keyframe (if using trigger) or section (if using repeater) and select Properties > Unbound > Create New Endpoint. Doing this will bind the event keyframe or section to a new endpoint node and open the Director Blueprint.

create new endpoint

The Event Endpoint can be renamed in the Blueprint's Details panel from the Name property.

rename event

You can create as many event keyframes or sections as you need. Event nodes can also be shared between multiple event sources by using the Quick Bind or Rebind To menus.

event track link

Parameters and Event Payloads

Similar to Blueprint Custom Events, the Event Track can have input parameters associated with it. Using event parameters and payloads, you can send property values to targets when the event fires.

To add a parameter to your event, select the event endpoint and click the New Parameter (+) button in the Details panel. Doing this will create a new parameter in the details and on the node for scripting

event track parameter property

When you right-click the event keyframe or section, additional properties for your parameters will be displayed under the Payload category. Here you can define the values on the parameters, which will be sent when the event executes.


Object Binding

When creating an Event Track under a bound object in Sequencer, it will create an Object Binding for the Event Track where the target object of the event node becomes bound to the object the Event Track has been added to. This makes it easier to script functions on specific Actors in your sequence, as functions can now be called on the object directly.

event track actor binding

An additional property will also be exposed on the keyframe or section properties context menu. Pass Bound Object To controls which object parameter this event should be bound to. If you have added additional Object or Blueprint Interface parameters to your endpoint node, then they will be selectable here.

pass bound object to

If an endpoint node is not yet designated for your object bound event, you can use the Quick Bind command to add script functions directly related to the bound object, similar to calling functions from an object reference in Blueprints.

quick bind event actor

Event Properties

When right-clicking either a Trigger keyframe or Repeater section, you can view the following properties in the Properties context menu.

event properties




The Event Endpoint this keyframe or section is bound to in the Director Blueprint.

By default this is unbound and can be bound by clicking the dropdown menu and selecting Create New Endpoint or any other existing endpoint node.

unbound create new endpoint

Quick Bind contains a list of compatible functions for this event, including the object binding if the Event Track is bound to an object.

quick bind

Call In Editor

Enabling this will cause the event logic to evaluate in the editor session without requiring you to Play or Simulate in Editor. This property appears once the event is bound to an endpoint node.

You can also right-click the Event Track to view the following properties in the Properties context menu.

event track properties



Fire Event when Forwards

Enabling this will cause the Event to fire when the sequence is playing forward normally.

Fire Event when Backwards

Enabling this will cause the Event to fire when the sequence is playing in reverse.

Using the Forwards and Backwards properties can be useful if you need to reset an event chain back to normal when previewing your sequence multiple times. You can set one Event Track to fire forward only and another to fire backward only. Afterward, you can hook up the forward event to the normal event chain, and the backward event to the reset chain.

Event Position

Defines where in the evaluation the event should trigger.

  • At Start Of Evaluation will cause the event to fire first, before anything else is evaluated in the sequence.

  • At End Of Evaluation will cause the event to fire last, after everything else has been evaluated in the sequence.

  • After Spawn will cause the event to fire after Spawnables have spawned and evaluated.

Help shape the future of Unreal Engine documentation! Tell us how we're doing so we can serve you better.
Take our survey