Goal

Use subtree tasks when several agents share a high-level tree but need different reusable behavior assets.

Tree structure

A Selector chooses a combat or civilian subtree according to the agent role.

How it runs

Create and test the Combat and Civilian behavior assets independently, then assign each asset to its Subtree Reference. In the Task Inspector, map the Shared Variables that each subtree needs by purpose so both assets receive the correct values from the parent tree.

The Selector tries the Combatant Branch first. When Is Combatant succeeds, the Combat Subtree Reference runs and reports the result of its behavior asset. When Is Combatant fails, the Selector skips that branch and runs the Civilian Subtree Reference instead.

Variations

Use Subtree Reference when the asset is known in advance, Subtree Reference Selector when a value chooses among several assets, and Set Subtree when another branch changes that value before the reference runs.

Tasks used in this tree

Subtree Reference, Subtree Reference Selector, and Set Subtree in the Actions reference, plus Selector and Sequence.