QueryImporter

Remarks

The same two steps a .vxutility takes, and for the same reason: an EnvironmentQuery holds live generator and test objects — a physics world, a navmesh — so what travels is the data and a game turns it into a query through QueryContentCompiler.

⚠ Two checks that a designer cannot make by looking at the file. A query with no generators has nothing to score and answers "nowhere" for ever; and a query with no scoring test ranks every surviving point equally, so it always returns whichever point the generator happened to make first — which looks like the query working and is a coin toss. Both fail the build here.

⚠ A registered generator or test that this build has never heard of is a warning and not an error, for BehaviorTreeImporter's reason: the importer compiles against an empty resolver, and a game registers its own trace and its own cover test in code at start-up. Failing the build on those would fail it on every query worth writing.

Fields and properties (2)

• public const string QueryType

  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, QueryImportSettings settings, CancellationToken cancellationToken)

  Imports one asset.