Integrations

Export

Behavior Designer integration packages add tasks and adapters for supported
Opsive and third-party systems without making those systems runtime
dependencies of the base package.

Install an integration

  1. Install Behavior Designer and the target asset first.
  2. Download the matching integration package from the
    Opsive downloads page, then import its .unitypackage.
  3. Allow Unity to compile and resolve any target-asset setup prompts.
  4. Reopen the Behavior Designer window and find the new task category.
  5. Import a supplied sample only after the integration compiles.

Keep an integration package out of projects that do not install its target
asset; its scripts normally reference types supplied by that asset.

Detailed guides

  • Dialogue System: start
    conversations, barks, sequences, and quests, then wait for completion.
  • Opsive Character Controllers:
    drive AI movement, abilities, and items through the character controller.
  • Playmaker: start an FSM and return its result to
    a behavior tree.
  • uScript: start a graph and resume the tree from a
    Behavior Designer node.
  • Visual Scripting: exchange custom events
    with a Unity Script Graph.

Other downloaded integration packages are typically usable as soon as both
packages compile. Use the included task fields and sample as the first
compatibility check.

Troubleshooting

  • An integration task category is missing: confirm the integration package
    was imported and inspect the first Console compile error.
  • Types cannot be found: install the target asset version expected by that
    integration or remove the unused integration package.
  • The task starts but never completes: verify that the target system invokes
    its Behavior Designer callback or resume operation.