Quick Start

Export

This walkthrough creates a small Behavior Designer Pro task that stays active until interrupted. It keeps the first result easy to inspect and test. For a different product, complete the same connection steps and then use the State Designer or Character Controller example.

Before you start

Use Unity 2022.3 or newer, a compatible supported Opsive product, Atlas, and a configured model provider. Resolve existing Unity Console compilation errors first. Keep your project in source control so you can compare the resulting changes.

Connect

  1. Open Atlas from your product’s menu or docked panel. See Installation for the product menus.
  2. Choose Sign in to Atlas and complete the one-time connection in your browser.
  3. Use the Opsive account that owns the product. Enter a matching Unity invoice only if the browser requests one.
  4. Return to Unity and confirm that the relevant product and a usable model are selected.

See Account and product access if the connection does not complete.

Ask, then generate

Start with an explanation:

/ask When should a Behavior Designer Pro Action return Running instead of Success?

Then request one concrete file:

/gen Create SimpleIdleTask, a GameObject Action for Behavior Designer Pro that returns Running until interrupted. It must not move the character or complete automatically.

An illustrative SimpleIdleTask result with source expanded and file actions available.

Apply and verify

  1. Expand the generated file. Confirm its class name, base class, and update result match the request.
  2. Choose Save as… and save to a project folder such as Assets/AI/Tasks/SimpleIdleTask.cs. Confirm the write when prompted.
  3. Wait for Unity to compile. If it fails, inspect the exact Console error and the offered correction workflow.
  4. Add the task to a small test behavior tree. Assign that tree to a test object using the normal Behavior Designer workflow.
  5. Enter Play Mode and confirm the task remains Running. Stop or interrupt it and confirm the character has no unintended movement or state changes.

An idle task staying Running is the expected result. It is not a task that should progress to the next child in a Sequence by itself.

Use Generating and applying code for file controls and correction behavior. Continue with Providing context when your next request needs your own components or an existing graph.