Creating Custom Ability Task Classes

Extend the base Ability Task class to encapsulate complex, reusable logic that persists across multiple frames of an ability.

In this lesson, you will learn how to encapsulate multi-frame, asynchronous logic into custom UAbilityTask subclasses to clean up your Gameplay Ability code.

Moving Beyond Built-in Tasks

While built-in tasks like WaitTargetData or PlayMontageAndWait are excellent for common scenarios, they become insufficient when you need to perform custom, stateful logic that spans multiple frames—such as tracking a projectile's homing path or managing a complex, multi-stage interaction. Instead of cluttering your UGameplayAbility with complex timers and state variables, you move that logic into a dedicated UAbilityTask class.

Designing the Task

A custom task acts as a bridge between the Ability System and your gameplay logic. You inherit from UAbilityTask (or a helper like UAbilityTask_WaitDelay), implement Activate(), and expose delegates (FAbilityTaskDelegate) to communicate results back to your ability.

Here is a simplified structural example:

UCLASS()
class UMyCustomTask : public UAbilityTask {
    GENERATED_BODY()

    // Delegate to notify the ability when the task completes
    UPROPERTY(BlueprintAssignable)
    FMyTaskDelegate OnTaskCompleted;

    // Static factory method to create the task
    UFUNCTION(BlueprintCallable, meta = (BlueprintInternalUseOnly = "TRUE"))
    static UMyCustomTask* CreateMyTask(UGameplayAbility* OwningAbility);

    virtual void Activate() override {
        // Logic starts here, potentially spanning multiple frames
    }

    virtual void TickTask(float DeltaTime) override {
        // Perform per-frame updates
    }
};

Why This Matters

By isolating logic into a custom task, you keep your UGameplayAbility class focused on its high-level flow (what to do) rather than the granular implementation details (how to track time, check collisions, or manage network state).

When you instantiate this via your factory method using NewAbilityTask<UMyCustomTask>(...), the Ability System automatically handles the lifecycle and replication requirements. This modularity ensures that if you need a "Homing Projectile Tracking" logic in three different abilities, you write the logic once in the task class and reuse it everywhere, significantly reducing technical debt.

Key Takeaway: Custom Ability Tasks encapsulate complex, multi-frame state machines into reusable, modular objects, keeping your Gameplay Ability classes clean and maintainable.