UtilityActionContent

Remarks

⚠ The task is named the same way a behaviour tree names one, out of the same BehaviorNodeSchema and built by the same factories. That is doc 37 § D2's whole payoff made visible: a project writes MoveToTask once, declares it once, and gets it in a tree, in a utility set and — when P6 lands — in a GOAP plan.

Fields and properties (7)

• public string Name

  What it is called, in the table and in the debug record.

• public string Task

  Which task it runs, as BehaviorNodeSchema names it.

• public Dictionary<string, string> Fields

  The task's fields, by name.

• public float Weight

  Its multiplier. 1 for ambient, 2–3 for important, 5 for emergency.

• public float Cooldown

  How long after it ends before it may be chosen again, in seconds.

• public int Bucket

  Which group it is in. Higher wins, under the bucketed selector.

• public List<UtilityConsiderationContent> Considerations

  What decides how good it is.

Used by (12)

• TypeRegistrationVixen.Ai
• UtilityContentTestsVixen.Ai.Tests
• UtilitySetContentVixen.Ai
• UtilitySetContentCompilerVixen.Ai
• Vixen_Ai_UtilityActionContentSerializerVixen.Ai
• Vixen_Ai_UtilitySetContentSerializerVixen.Ai
• LiveAgentVixen.Editor.AssetEditors.Tests
• UtilitySetDocumentVixen.Editor.AssetEditors
• UtilitySetDocumentTestsVixen.Editor.AssetEditors.Tests
• UtilitySetModelVixen.Editor.Ai
• UtilitySetViewVixen.Editor.AssetEditors
• UtilitySetViewTestsVixen.Editor.AssetEditors.Tests