IQueryGenerator

Remarks

doc 37 § Part 4's seam. A generator is deliberately dumb: it produces positions and does not know what they are for, because every question about whether a position is any good is a test's. That split is what lets one grid generator serve "where do I take cover", "where do I throw this" and "where do I flank from".

⚠ A generator may not read the world. The shipped ones are arithmetic over an origin, and the two that are not — points from entities, points on a navmesh — take what they need through a seam of their own, because Vixen.Ai can see neither a transform nor a mesh. Doc 37's whole argument for putting the planners in Core/ is that they do not reach for an engine.

Fields and properties (2)

• Symbol Name

  What it is called.

• int Estimate

  Roughly how many points it will make, so a run can size its list once.

Methods (1)

• void Generate(in AgentContext context, in QueryOrigin origin, List<QueryPoint> points)

  Generates.

Used by (14)

• BehaviorTreeResolverVixen.Ai
• CompositeGeneratorVixen.Ai
• ConeGeneratorVixen.Ai
• CurrentLocationGeneratorVixen.Ai
• DonutGeneratorVixen.Ai
• EntityGeneratorVixen.Ai.Nodes
• EnvironmentQueryVixen.Ai
• GridGeneratorVixen.Ai
• QueryContentCompilerVixen.Ai
• QueryGeneratorTestsVixen.Ai.Tests
• QueryGeneratorsVixen.Ai
• SeamTestsVixen.Ai.Nodes.Tests
• WorldQueryTestsVixen.Ai.Nodes.Tests
• WorldQueryTestsVixen.Ai.Nodes