- name
SKILL.md
Tệp skill vẫn nằm trong kho mã của nhà phát hành.
Dán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill ai-behavior-trees-utility-ai -a cursor -yDán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill ai-behavior-trees-utility-ai -a claude-code -yDán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill ai-behavior-trees-utility-ai -a codex -yDán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill ai-behavior-trees-utility-ai -a grok -yGửi tin nhắn đã sao chép trong cuộc trò chuyện Grok Bot. Bot sẽ lấy tệp SKILL.md này từ GitHub và thêm vào bộ skill mà mọi Bot của bạn dùng chung.
Install this skill: https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/HEAD/skills/disciplines/ai-behavior-trees-utility-aiTừ nhà phát hành
A behavior tree (BT) gives an agent ordered, interruptible priorities; Utility AI scores every option and picks the most wanted one. The code is plain C# so it ports to any engine; the non-obvious part is the lifecycle contract (who resets what, and when), which is where almost every BT bug lives.
Not this skill: choosing FSM vs BT, steering, A*, flow fields and perception belong to
game-ai. Unreal's BehaviorTree/Blackboard assets, BTTask/BTService, EQS and StateTree
belong to unreal-behavior-trees. The agent that physically moves (NavMeshAgent,
NavigationAgent3D) belongs to the engine navigation skill.
targetPos, health01,
distToPlayer); leaves read them. Nodes never hold references to each other.Sequence whose first child is a guard condition must be a
ReactiveSequence, or the guard stops being checked once the action runs.Every node returns Success, Failure or Running. Parents reset a child as soon as it returns
a terminal status and when they abandon it while Running; the tree resets a terminal root.
Reset() must be idempotent and must clear only execution-local state (timers, reservations),
never persistent state such as a cooldown deadline.
// Selector = fallback/OR: return the first child that is not Failure.
// `Current` (from Composite) remembers a Running child so the next tick resumes there.
public sealed class Selector : Composite
{
public override Status Tick(Blackboard bb, float dt)
{
for (; Current < Children.Count; Current++)
{
var s = Children[Current].Tick(bb, dt);
if (s == Status.Running) return Status.Running; // resume here next tick
Children[Current].Reset(); // terminal child can re-enter cleanly
if (s == Status.Success) { Current = 0; return Status.Success; }
}
Current = 0;
return Status.Failure; // every child failed
}
}
This is the memory variant: it cannot be preempted. Sequence, ReactiveSelector,
ReactiveSequence, Parallel, the decorators and BehaviorTree follow the same contract in
references/behavior-tree-core.md.
// A consideration maps one raw fact to 0..1 through a response curve.
float Score(Blackboard bb)
{
float distance01 = Curves.InverseLerp01(bb.Get<float>("distToPlayer"), 20f, 2f); // near = 1
float health01 = Curves.Sigmoid(bb.Get<float>("health01"), k: 8f, mid: 0.4f); // hurt = low
// A 0 in any factor still vetoes the action; compensation stops each extra
// consideration from dragging every score toward 0. No allocation per call.
return Curves.Compensate(distance01 * health01, count: 2);
}
Selection: argmax with an inertia bonus of about 0.05 for the running action is the default; softmax (temperature about 0.2) when designers want variety without silly picks.
Run this shape in the project's test runner (Unity Test Framework, GdUnit4, xUnit) before
tuning by eye; Assert stands for the framework's assertion. A probe leaf counts ticks and
resets, so lifecycle bugs show up as numbers.
sealed class Probe : Leaf
{
public int Ticks, Resets; readonly int _after; readonly Status _end;
public Probe(int after, Status end = Status.Success) { _after = after; _end = end; }
public override Status Tick(Blackboard bb, float dt) => ++Ticks >= _after ? _end : Status.Running;
public override void Reset() { Ticks = 0; Resets++; }
}
// Guard lost mid-action: the running action must be aborted, not resumed.
var bb = new Blackboard(); var chase = new Probe(after: 3);
var seq = new ReactiveSequence().Add(new Condition(b => b.Get<bool>("sees"))).Add(chase);
bb.Set("sees", true); Assert(seq.Tick(bb, 0.1f) == Status.Running);
bb.Set("sees", false); Assert(seq.Tick(bb, 0.1f) == Status.Failure && chase.Ticks == 0);
Cover at least: a Wait that runs twice in a row takes full time both runs; a lost guard
aborts its action; a cooldown still blocks after its branch is aborted; utility returns null
(and the caller copes) when every action scores 0.
Sequence resumes at its running child, so
[CanSeePlayer?, Chase] chases forever after sight is lost. Use ReactiveSequence, or make
the action fail when its Blackboard input disappears.Selector at the root keeps resuming a running Patrol
and never re-asks Attack. Top-level priority selectors are reactive, and they must Reset()
the branch they abandon or its move or animation keeps running.Wait/Repeat accumulators were not
cleared because the parent skipped Reset() on a terminal child.Cooldown that clears its ready-time in Reset() lets an agent attack
every time it flickers between branches. Keep the deadline across resets.Parallel restarts finished children. Re-ticking a child that already succeeded restarts
it, and RequireAll then never sees all children succeed on one tick. Store per-child results.Sequence makes the agent step back to patrol for a tick each time it is
blocked. Wrap it in ForceSuccess when "wait for the cooldown" should hold the branch.Curves.Compensate), which keeps an exact 0 as a veto.exp(score / 0.01) is infinity in float). Subtract
the best score before exp.Tick allocates nothing (no LINQ, no closures
capturing locals, no boxing in hot Blackboards). Use a fields class instead of a
Dictionary<string, object> for agents that tick often.references/behavior-tree-core.md: read when writing or reviewing the runtime itself
(Blackboard, base classes, every composite including the reactive ones, Parallel,
decorators, BehaviorTree).references/utility-ai-system.md: read when building the scorer (curve library,
compensation, Consideration, UtilityAction, argmax and softmax selection).references/practical-examples.md: read when you need a full agent to adapt (guard
Patrol/Combat BT, needs-driven villager, hybrid UtilitySelectorNode).references/best-practices-and-pitfalls.md: read when scaling to many agents or debugging
(time-slicing, AI LOD, event-driven aborts, debug overlays, reproducible randomness).game-ai: decision-model choice, FSMs, steering, pathfinding, perception.unreal-behavior-trees: Unreal's asset-based BT, Blackboard, EQS and StateTree.unity-navmesh: the NavMeshAgent that carries out "move to" intents.Last verified: 2026-11-11.
Vector2 member names
(magnitude, normalized, sqrMagnitude); Godot 4 C# uses Length(), Normalized(),
LengthSquared(); System.Numerics.Vector2 uses Length() and Vector2.Normalize(v).tests/test_ai_examples.py compiles the published blocks with the .NET 10
SDK and runs the lifecycle scenarios.com.unity.behavior 1.0.17, LimboAI 1.8.1 and Beehave 2.9.3 for Godot.>
---name: ai-behavior-trees-utility-aidescription: >---# skills/disciplines/ai-behavior-trees-utility-ai/SKILL.mdCâu hỏi thường gặp
Tải skills/disciplines/ai-behavior-trees-utility-ai/SKILL.md từ nhà phát hành, hoặc sao chép đường dẫn và mở kho mã. PlugMCP chỉ liệt kê skill và không lưu trữ tệp này.
Nhà phát hành duy trì nó tại https://github.com/gamedev-skills/awesome-gamedev-agent-skills.
Claude, Cursor, Codex và Grok Build có thể đọc tệp SKILL.md mà bạn thêm từ kho mã của nhà phát hành. Grok Bot cài đặt skill khi bạn gửi liên kết thư mục GitHub của skill trong cuộc trò chuyện.