csharp
public interface IUtilityInputWhere a consideration's number comes from.
Remarks
doc 37 § Part 4's seam, and the one a project replaces most often: "how hungry am I", "how much ammo is left", "how many of them are there" are all a game's own question.
⚠ It returns a number in [0,1] and the normalisation is the input's job, not the curve's. A curve whose domain were "0 to whatever this game's maximum health is" could not be drawn, could not be shared between two considerations, and would have to be re-authored the day somebody changed the maximum. Normalising here is what makes the six shapes in ResponseCurveKind mean the same thing everywhere.
Methods (1)
float Read(in AgentContext context)Reads the world.
Used by (13)
- AiSnapshotsVixen.Ai
- BehaviorTreeResolverVixen.Ai
- BlackboardUtilityInputVixen.Ai
- ConstantUtilityInputVixen.Ai
- DelegateUtilityInputVixen.Ai
- DistanceUtilityInputVixen.Ai
- NearestPerceivedInputVixen.Ai.Perception
- PerceivedCountInputVixen.Ai.Perception
- PerceptionInputsVixen.Ai.Perception
- SeamTestsVixen.Ai.Nodes.Tests
- UtilityConsiderationVixen.Ai
- UtilityInputsVixen.Ai
- UtilitySetContentCompilerVixen.Ai