> For the complete documentation index, see [llms.txt](https://dapper-raptor.gitbook.io/spline-volume/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dapper-raptor.gitbook.io/spline-volume/working-with-sbbtv/configuring-actors-for-trigger-interactions.md).

# Configuring Actors for Trigger Interactions

Setting up actor and triggers to work together

Once a [spline trigger volume is set up](/spline-volume/working-with-sbbtv/adding-a-spline-volume/spline-trigger-volumes.md), a small step is required for the actors that are going to interact with that trigger.

## Setup Overlap Events

Select your collision component and add the **On Component Begin Overlap** and **On Component End Overlap** events by clicking the respective green **"+"** buttons in the details panel.

<figure><img src="https://2399807916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfrAgERKNBzDDo0yMgfvh%2Fuploads%2FW4rKmT9fS4OvllJAiYlV%2Fimage.png?alt=media&amp;token=efb01b86-bb03-440c-bc2e-1dc2263983f9" alt=""><figcaption></figcaption></figure>

This will add the two engine events that dictate what happens when your actor's collision overlaps other collision in your scene. For each event, connect up the blueprint library function **Volume Actor Test** as shown in the screenshot below. Ensure that the **Other Actor** input is connected to the **Other Actor** reference from the event node, the **Other Component** input is connected to the **Other Comp** reference from the event node, that a **reference to Self** is connected up to the **Interacting Actor** input and that the **New Overlap** boolean is set to **true** for **Begin Overlap** and **false** for **End Overlap**.

<figure><img src="https://2399807916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfrAgERKNBzDDo0yMgfvh%2Fuploads%2FeqaapZ2MltpDMISQftui%2Fimage.png?alt=media&amp;token=444c594c-443f-4830-b77f-7e7dbfdaaaa6" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2399807916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfrAgERKNBzDDo0yMgfvh%2Fuploads%2FItxVo1YkxzTM11QZij8D%2Fimage.png?alt=media&amp;token=7175e395-8c9f-4db7-94f1-cd02cafeabb1" alt=""><figcaption></figcaption></figure>

This can be done on any actor that has a collision component. Once set up, you should see actors firing off the trigger (as long as their collision channel matches one defined in the volume actor).

Note that the **Volume Actor Test** node has an output boolean called **Interaction Handled**. This can be used when an actor requires multiple sets of overlap logic to know if the overlap was handled or not.
