Integrations and Troubleshooting
Export
Use the task implementation that matches the movement component controlling the agent. Importing an integration adds provider-specific options; it does not convert existing tasks automatically.
Pathfinding integrations
Download supported Movement Pack integrations from the Opsive integrations page. After importing an integration, select its implementation in each task’s Pathfinder field.
When changing pathfinders, review arrival distance, stopping distance, update rate, agent radius, navigation sampling, and local avoidance. The same numeric settings can have different practical meanings in two implementations.
The agent wobbles instead of stopping
Compare the movement component’s stopping distance with the task’s arrival distance. For Unity navigation, increase NavMeshAgent Stopping Distance so the agent can remain inside the task threshold.
For Follow, provide enough tolerance around the maintained distance so the agent does not alternate between moving and stopped at one exact boundary.
The agent moves through walls
Check whether the graph uses Move Towards. That task moves directly and does not calculate a path. Use Seek with the correct pathfinder when obstacles must be avoided.
The task stays Running on an unreachable target
Confirm the target and generated waypoints are on navigation data for this agent type. Decide whether the graph should keep retrying, fail to a fallback branch, or select the nearest reachable point.
Do not make the arrival distance so large that the task succeeds from the wrong side of a wall.
Pursue overshoots a fast target
Reduce Target Distance Prediction and inspect velocity for teleport or network-correction spikes. Seek can be more stable for rapidly changing motion.
The game needs unrestricted 3D movement
The included pathfinder workflows operate on a navigable surface rather than a fully volumetric route. Use a supported surface with a separate height offset or implement a project-specific steering and volumetric navigation solution.
Movement ownership conflicts
If the destination is correct but motion jitters or resets, inspect every component writing the Transform, Rigidbody, root motion, or navigation destination. Keep one active movement authority and let the behavior tree select intent.