Procedural Graph Mover Bug

General
3

Related: ProceduralGraphMover doesn't adjust Bounds Y position

I disagree with “just increase bounds height” because

  1. I am using bounds for its intended purpose – to filter out distant paths above and below the player, which is a valid use case. e.g. I don’t want pathing on overhead objects.

  2. The height a player may traverse is significant. As they travel, they may be 1024 units below or 1024 units above ground height. With this in mind, why wouldn’t the procedural graph mover snap to the y-axis of the player as they climb and descend mountains?

  3. Forcing a larger scan volume than needed seems wasteful to me.

Is my feedback incorrect?