Configure and reuse Abilities
Give each candidate a complete behavior without mixing gates, scoring and execution.
Gates and bonuses
Gates consume booleans and decide eligibility. Base scores and conditional bonuses determine priority among eligible candidates. A bonus node takes a boolean condition and a numeric amount; its scoring Context is not an arbitrary integer output.
Create an execution quickly
Choose the execution
Use the Ability execution menu or drag from an appropriate execution pin. Select a flow graph or a child BDS.
Create or reuse configuration
Create a graph when none is assigned; double-click an existing reference to navigate to it. A BDS can directly reference a child BDS without an extra bridge graph.
Author the operations
Add Actions through categorized menus: movement, character operations, time, animation and more. One Action node may contain several Actions.
Return to the caller
Use workspace Back / Forward to retrace navigation. Save the child graph and check the caller signature after changing inputs or outputs.
Save a reusable Ability
Save an Ability as a reusable asset in the inspector. Other BDS graphs can select it with Reference Ability. Maintain common rules such as low-health retreat in the source asset rather than treating every reference as an independent copy.
Before reusing an Ability, check its expected Actor type, variable scope, behavior resources and call arguments. The same variable name in two graph instances does not imply shared storage.
Completion and interruption differ
| Situation | Result |
|---|---|
| Normal leading candidate | Keep scoring; wait for the current behavior to finish. |
| Forced-interrupt leader | Exit the current branch and enter the new Execution. |
| Interrupted Action | Run Exit cleanup; do not emit a false FINISHED success. |
| Child behavior completed | Return to the caller and provide its output values. |