NEW V4 - Finishes & Contextual Animations
Executions in ACF are special contextual animations that synchronize two characters in a single, shared animation: finishers, takedowns, grapples, pushes, and any action requiring perfect sync between a Master and a Slave.
The logic is handled by:
Master Component – decides when an execution can start and triggers it
Slave Component – validates if the target can participate
Combined Anim Configs – store all settings and link to the Contextual Anim Scene Asset
Everything is driven by Contextual Anim Assets + the component system.
1. Execution Data (Contextual Anim Configs)
Executions are defined inside a Combined Animations Data Asset, which contains an array of:
FCombinedAnimConfig
Each config includes:
AnimTag – the gameplay tag used to identify this execution
CombinedAnimation – the Contextual Anim Scene Asset to play
MaxDistanceToStart – distance threshold to allow the execution
MasterRequiredActionsSet – optional tag requirement for the initiator
SlaveRequiredTags – tags the target must have
KillSlaveAfterAnim – if true, kills the target at the end
This Data Asset is referenced by the Master Component, which uses it to choose the correct execution to play.
2. Components Required
Characters participating in executions need:
Master Component
Used by the character initiating the execution. Handles:
Compatibility checks
Syncing movement and rotation
Triggering contextual animations
Broadcasting start/end events
Slave Component
Used by the target character. Handles:
Tag requirements
Custom per-animation conditions
Allowing or rejecting the execution request
Receiving synchronized animation
Triggering start/end events
ContextualAnimSceneActor
Both slave and master will need to have an ContextualAnimSceneActor component
3. Starting an Execution (Blueprint)
3.1 Discover the Best Execution
Call:
TryGetBestCombinedAnimForActor(TargetActor, OutCombinedAnim)
If it returns true, an execution is valid and all requirements passed:
distance
direction
tags
conditions
contextual anim availability
The returned OutCombinedAnim contains the Contextual Anim Scene Asset to use.
3.2 Slave Validation (Target Requirements)
The slave character can approve or reject executions using:
CanStartCombinedAnimation(CombinedAnim, Master)
The slave checks:
SlaveRequiredTags
Distance
Direction requirements
Custom UCASAnimCondition objects (optional)
Conditions can be stacked using AND/OR groups.
This allows you to restrict executions by:
health
combat state
special gameplay situations
gameplay tags
movement direction
anything else implemented as a condition
4. Start the Finisher
To Start a contextual anim you can call the following blueprint nodes:
TryExecyteCurrentTarget will try to play the best ContextualAnim for current target gathered from the ATSTargeting Component
TryPlayCombinedAnim will try to play the provided ContextualAnim with the provided target actor

5. Execution Events (Blueprint Bindings)
Both Master and Slave components expose events you can use to control gameplay:
Master Component Events
OnCombinedAnimationStarted
OnCombinedAnimationEnded
Slave Component Events
OnCombinedAnimationStarted
OnCombinedAnimationEnded
Combined Anim Component Hooks
Can be overridden in Blueprint:
OnJoinedScene – called when the Contextual Anim Scene starts
OnLeftScene – called when the scene ends
6. Finishers (Kill Slave After Animation)
Inside any FCombinedAnimConfig, set:
KillSlaveAfterAnim = true
When the animation ends, the target is automatically killed.
Great for stealth kills, fatal blows, and cinematic executions.
7. Positioning, Warping & Direction
Executions enforce:
MaxDistanceToStart
Relative Direction (front / behind / any)
Warp movement to reach the exact sync point
Forced slave rotation if required
Optional Z-axis ignoring (for uneven terrain)
These values come directly from the execution config or the contextual anim specifications.