Skip to content

t1k:unity:dots-ai:behavior-designer-pro

FieldValue
Moduledots-ai
Version3.30.3
Efforthigh
Tools—

Keywords: AI, behavior designer, behavior tree

/t1k:unity:dots-ai:behavior-designer-pro

Behavior Designer Pro — DOTS Entity Reference

Section titled “Behavior Designer Pro — DOTS Entity Reference”

Reference for Behavior Designer Pro (BDP) — a behavior tree tool for Unity DOTS by Opsive. This skill covers DOTS Entity mode only — Burst-compiled, job-parallel ECS task systems.

Related skills: t1k-unity-dots-core-ecs (ECS fundamentals) · t1k-unity-dots-core-jobs-burst (Jobs, Burst) · t1k-unity-dots-combat-rpg (RPG gameplay) · t1k-unity-dots-core-performance (optimization)


  • Using any Opsive.BehaviorDesigner.* namespace
  • Creating ECS entity tasks (ECSActionTask, ECSConditionalTask)
  • Working with EvaluateFlag, TaskComponent, BranchComponent ECS components
  • Entity baking for behavior trees (auto-bootstrap on world creation — BDP 3+)
  • Conditional aborts with IReevaluateResponder
  • Programmatic tree creation (TreeLogicNodes, ITreeLogicNode, fluent TreeBuilder)
  • Performance throttling (EvaluateFlag + AIUpdateTier integration)
  • Migrating BDP 2 → BDP 3 (3rd-generic wrapper refactor)

  • Unity: 6000.5+ (Unity 6)
  • Entities package: 6.5.0+ (builtin — ships inside the editor, not the registry)
  • BDP package: com.opsive.behaviordesigner 3.2.0 from a scoped registry, plus its deps com.opsive.graphdesigner 3.1.0 and com.opsive.shared 2.3.0. com.opsive must be listed in the registry scopes or the resolve fails with a misleading cannot be found
  • Platform: All except WebGL (Entities/Burst limitation)
  • Assembly: DOTSBDP asmdef must reference Opsive.BehaviorDesigner.Runtime.Systems — the only load-bearing Opsive entry, since 3.2.0 carved it out as a real asmdef and it owns BehaviorTreeSystemGroup. Opsive.BehaviorDesigner.Runtime and Opsive.Shared.Runtime are DLLs, not asmdefs; those entries are inert and work only via auto plugin linking. Under overrideReferences: true list the DLL filenames in precompiledReferences instead. See migration-3-0-to-3-2-asmdef-split.md (references/migration-3-0-to-3-2-asmdef-split.md) §2/§2b

ModuleReferenceCoverage
Conceptsconcepts-guide.md (references/concepts-guide.md)Tree flow, task types, composites, decorators, conditional aborts
Entity Tasksentity-task-guide.md (references/entity-task-guide.md)ECS tasks (6 files each), Burst systems, jobs, flags, reevaluation
Entity Bakingentity-baking-guide.md (references/entity-baking-guide.md)Baking workflow, spawning, BDP 3 auto-bootstrap
Tree Creationtree-creation-guide.md (references/tree-creation-guide.md)Programmatic tree building, TreeBuilder API, BattleDemo archetypes
DOTS RPG Integrationdots-rpg-integration-guide.md (references/dots-rpg-integration-guide.md)17 BDP tasks, 3-layer architecture, system ordering bridges
Performanceperformance-throttling-guide.md (references/performance-throttling-guide.md)EvaluateFlag throttling, AIUpdateTier, scaling strategies
Migrationmigration-2-to-3-guide.md (references/migration-2-to-3-guide.md)BDP version migration recipes (institutional memory)
Migration (3.2)migration-3-0-to-3-2-asmdef-split.md (references/migration-3-0-to-3-2-asmdef-split.md)Registry install (com.opsive.* scope), BDP 3.2.0 assembly split — BehaviorTreeSystemGroup reachability, DLL vs asmdef linking, retired ISubtreeReference workaround

Install: BDP ships from a scoped registry (com.opsive.behaviordesigner 3.2.0 + com.opsive.graphdesigner 3.1.0 + com.opsive.shared 2.3.0), not an embedded Packages/ folder or an Asset Store import. Any guidance telling you to edit files under Packages/com.opsive.behaviordesigner/ is stale — that path no longer exists. See migration-3-0-to-3-2-asmdef-split.md §0.


BehaviorTreeSystemGroup (SimulationSystemGroup)
├── BDPEvaluateFlagThrottleSystem (before group — disables EvaluateFlag for skip-frame entities)
├── BeforeTraversalSystemGroup (OrderFirst)
│ └── ReevaluateTaskSystemGroup (conditional abort reevaluation)
├── InterruptSystemGroup
│ └── InterruptTaskSystemGroup
├── TraversalSystemGroup
│ ├── TraversalTaskSystemGroup (custom task systems — 15 total)
│ └── EvaluationSystem (tree traversal)
└── EvaluationCleanupSystem (OrderLast — re-enables EvaluateFlag)
Layer 1: PERCEPTION (AISystemGroup)
AIUpdateTierSystem → DetectionSystem → AggroSystem
↓ [BDPAfterPerceptionBridge]
Layer 2: BEHAVIOR (BehaviorTreeSystemGroup)
BDPEvaluateFlagThrottleSystem → BDP internal → Custom task systems
↓ [BDPBeforeNavigationBridge]
Layer 3: EXECUTION (Navigation + Combat)
AgentNavigationBridgeSystem → AutoAttackSystem

→ See references/ecs-components-guide.md for the full ECS component table (~600-800B overhead per entity), EvaluateFlag throttle pattern, and task status flow.

using Opsive.BehaviorDesigner.Runtime; // BehaviorTree API
using Opsive.BehaviorDesigner.Runtime.Tasks; // TaskStatus, ECSActionTask, ECSConditionalTask
using Opsive.BehaviorDesigner.Runtime.Components; // ECS: TaskComponent, BranchComponent, EvaluateFlag
using Opsive.BehaviorDesigner.Runtime.Groups; // BehaviorTreeSystemGroup
using Opsive.GraphDesigner.Runtime; // ITreeLogicNode, IAuthoringTask

  • To create an ECS task, inherit ECSActionTask<TSystem, TComponent, TComponentFlag> or ECSConditionalTask<TSystem, TComponent, TComponentFlag> with Burst-compiled ISystem (BDP 3 — 3rd generic is the per-task flag struct)
  • Do NOT override the Flag property — BDP 3 base class implements it via the 3rd generic. Override causes CS0108 warning
  • Each entity task = 4-6 files: Authoring, Component (IBufferElementData), Flag (IEnableableComponent), System (ISystem), Job (IJobEntity), optional ReevaluateSystem+Flag
  • To bake behavior trees, place BehaviorTree on a prefab in a SubScene — BDP 3 auto-bootstraps the baked-tree system on world creation; no explicit call needed
  • To create trees programmatically, set bt.TreeLogicNodes, bt.EventNodes (with Start node), then bt.Serialize()
  • To force system ordering, use empty bridge ISystem structs with [UpdateAfter]/[UpdateBefore]
  • All task systems MUST be [DisableAutoCreation] — BDP manages their lifecycle
  • All task systems MUST include EvaluateFlag in their query (BDP template enforces this) -> See references/scaling-incident-guide.md for ECS task gotchas and performance scaling table (<100 to 2000+ units).
FileContents
concepts-guide.md (references/concepts-guide.md)Tree flow, task types, composites, decorators, conditional aborts
entity-task-guide.md (references/entity-task-guide.md)ECS tasks (6 files each), Burst systems, jobs, flags, reevaluation
entity-baking-guide.md (references/entity-baking-guide.md)Baking workflow, spawning, BDP 3 auto-bootstrap
tree-creation-guide.md (references/tree-creation-guide.md)Programmatic tree building, TreeBuilder API, BattleDemo archetypes
dots-rpg-integration-guide.md (references/dots-rpg-integration-guide.md)17 BDP tasks, 3-layer architecture, system ordering bridges
performance-throttling-guide.md (references/performance-throttling-guide.md)EvaluateFlag throttling, AIUpdateTier, scaling strategies
ecs-components-guide.md (references/ecs-components-guide.md)ECS component table, EvaluateFlag throttle, task status flow
scaling-incident-guide.md (references/scaling-incident-guide.md)ECS task gotchas, vendor bug workarounds, performance scaling table
advanced-guide.md (references/advanced-guide.md)Advanced BDP patterns and techniques
migration-2-to-3-guide.md (references/migration-2-to-3-guide.md)BDP version migration recipes (institutional memory)
migration-3-0-to-3-2-asmdef-split.md (references/migration-3-0-to-3-2-asmdef-split.md)Registry install, BDP 3.2.0 assembly split, DLL vs asmdef linking, retired ISubtreeReference workaround
bdp-task-generic-guide.md (references/bdp-task-generic-guide.md)BDPTaskData<TPayload> — form-b rationale, exact API, all shipped payload types, MANDATORY [assembly: RegisterGenericComponentType] registration gotcha (runtime Unknown Type on missing entry), Patrol/WaitDuration/Flee examples, 3 use-cases, step-by-step new-task guide, write-back gotcha