UtilitySetContentCompiler

Remarks

The same shape BehaviorTreeContentCompiler has, and it shares that compiler's back half outright: an action's task is looked up in the same BehaviorNodeSchema, built by the same factories and registered in the same AgentActionRegistry. Two files that both say Wait(2) get one action between them whether one of them is a tree and the other a set.

⚠ Everything it cannot resolve is a diagnostic and a placeholder, never a refusal. Tuning a set before its inputs exist is the ordinary order of work, and a compiler that refused would make the file unopenable until every name resolved. A consideration whose input is missing scores zero, which under the zero rule vetoes its action — so an unfinished set is an agent that does nothing rather than an agent that does the wrong thing.

Methods (1)

• public static bool TryCompile(UtilitySetContent content, BehaviorTreeResolver resolver, out IReadOnlyList<BehaviorTreeDiagnostic> diagnostics, out UtilitySet? set, BlackboardLayout? layout = null)

  Builds a set from a file.

Used by (3)

• UtilityContentTestsVixen.Ai.Tests
• UtilitySetDocumentVixen.Editor.AssetEditors
• UtilitySetImporterVixen.Editor.Assets