Skip to content
TECHNICALLYARTIST
FAB

Troubleshooting

The minion reaches the resource but nothing happens

Section titled “The minion reaches the resource but nothing happens”

The Resource Component’s sphere is not big enough for the minion to overlap, or something is blocking the overlap. The minion harvests by overlapping the sphere with its capsule, so size the sphere larger than the mesh and make sure its collision overlaps the Pawn channel. If the minion is stuck on the BTT_Try_Extract task in the Behavior Tree, this is the cause.

The Resource Component's collision sphere drawn larger than the mesh in the viewport

The BT_Extract_Resource behavior tree, where a stuck BTT_Try_Extract points to an overlap problem

The extracted resource never appears in the minion’s hands

Section titled “The extracted resource never appears in the minion’s hands”

The order is missing its carried actor or its socket. In the Assignment Definitions, confirm the entry has an Extracted Resource Actor Class set and that Resource Socket Name matches a real socket on the minion’s skeletal mesh.

The minion never starts, or only the host works

Section titled “The minion never starts, or only the host works”

The Gatherer has no authority. In single player this should not happen; in multiplayer, the minion must be owned by the commanding player. Call Set Owner with the Player Controller when you spawn the minion. See Multiplayer & Replication.

A resource never disappears (or only on the host)

Section titled “A resource never disappears (or only on the host)”

The resource actor is not replicating. Enable Replicates on the resource actor so Extractions Remaining can replicate and the actor can remove itself on all machines when it is used up.

Check, in order:

  • Tags pair up. The order’s Resource Tag must equal the Resource Tag on the target actors.
  • It is in range. The resource is within the Gatherer’s Resource Search Radius (default 2500) of the home location.
  • It is reachable. There is a navigable path to it. Drop a NavMeshBoundsVolume over the area and press P to confirm the navmesh reaches both the minion and the resource.

The carried actor has no Extracted Resource Component, so its collision is not fixed on drop. Add the Extracted Resource Component to the carried actor; it re-enables a solid collision on landing while ignoring the Pawn channel. Also keep the mesh’s collision out of the way while it is carried (NoCollision or query-only ignoring Pawn).

The Output Log says “Assignment asset not set” or “Could not begin assignment”

Section titled “The Output Log says “Assignment asset not set” or “Could not begin assignment””

The Gatherer Component has no Available Assignments Data Asset, or the Assignment Tag you passed has no matching entry in it. Assign the data asset on the component, and confirm an entry exists whose Assignment Tag equals the tag you pass to Try Begin Assignment (matching is exact).

The Output Log says it “could not start behavior tree”

Section titled “The Output Log says it “could not start behavior tree””

The order’s entry in the data asset has no Assignment Behavior Tree. Give every assignment a Behavior Tree (the included BT_Extract_Resource, or your own). The minion also needs an AI Controller Class set, since the tree runs on the controller.