GoapDomainImporter

Remarks

The same two steps every AI asset takes: what travels is the data, and a game turns it into a GoapDomain — which builds the action graph — through GoapDomainContentCompiler against its own registries.

⚠ What the importer adds is the two checks a designer cannot make by looking. A condition on a world key that does not exist never holds, so the action it gates never runs and the goal it belongs to is never met — with nothing in the game to look at. And a goal whose conditions no effect can serve is a goal the resolver will report as unreachable once per re-plan, for ever. Both fail the build here.

Fields and properties (2)

• public const string DomainType

  The alias of the type this writes.

• public override int Version

  Its own version. Bumping it invalidates every artefact it has ever produced, which is the whole mechanism for "I fixed the mip filter, re-import everything".

Methods (1)

• protected override ValueTask<ImportResult> ImportAsync(ImportContext context, GoapDomainImportSettings settings, CancellationToken cancellationToken)

  Imports one asset.

Used by (1)

• BuiltInImportersVixen.Editor.Assets