Creating Custom Action Leaf Nodes

You will script custom leaf nodes that communicate directly with Unity components to execute specific agent tasks like moving or attacking.

In this lesson, you will learn how to bridge your Behavior Tree’s decision-making logic with your game world by creating custom Action Leaf nodes that directly manipulate Unity components.

The Role of Leaf Nodes

In a Behavior Tree, decorators and composites handle the "traffic flow" of your AI’s logic, but leaf nodes are where the actual work happens. When a selector or sequence delegates a task, it hits an Action node. Because we have previously established Component-Based Logic Separation and Interface-Based Programming, your leaf nodes shouldn't contain complex movement or combat math. Instead, they should act as thin, specialized bridges that call methods on your agent's components.

Structuring the Action

To keep your architecture clean, define a base ActionNode class. Each specific action (like MoveToTarget or AttackTarget) will inherit from this, injecting the necessary dependencies—like a NavMeshAgent or a CombatController—to perform the task.

Here is how a simple "Move" action communicates with the NavMeshAgent:

public class MoveToTargetNode : ActionNode
{
    private NavMeshAgent _agent;
    private Transform _target;

    public MoveToTargetNode(NavMeshAgent agent, Transform target)
    {
        _agent = agent;
        _target = target;
    }

    public override NodeState Execute()
    {
        _agent.SetDestination(_target.position);
        
        // Return RUNNING while moving, SUCCESS when close
        if (_agent.remainingDistance < 0.5f) return NodeState.Success;
        
        return NodeState.Running;
    }
}

Decoupling Logic

Notice that the node doesn't calculate pathfinding or handle collisions; it simply communicates with the NavMeshAgent configured in our previous lessons. By injecting these components through the constructor, you ensure that your Behavior Tree remains testable and decoupled from specific GameObject hierarchies. If you decide to swap the movement system later, you only need to update the leaf node’s interaction logic, leaving the tree's overall structure intact. This approach treats your AI’s brain as a conductor, and your Unity components as the orchestra members executing the specific performance.

Key Takeaway: Action Leaf nodes serve as the essential interface between the decision-making tree and your agent's modular components, keeping your architecture clean and highly maintainable.