I’m brand new to this library and just starting to integrate it with our existing code base, so I’m currently running paths manually and not relying on AIPath or similar high level classes. When I ask for a path using XPath, there’s a function called ChangeEndNode which is called whenever the path is complete that overwrites the path’s endPoint to the final node’s center. Because of this, the ClosestOnNode exactness for the end point does not do what I expected it to, since it acts basically the same as SnapToNode. I’m not sure if this is a bug or something intentional with how XPath is supposed to work but is not obvious to me.
ABPath works like I’d expect in this regard, but I’d like to use XPath rather than ABPath so that I can run paths but with an EndingConditionProximity (to path within a specified range of a target). I can of course hack up the code myself to get the desired behavior, but I know so little about the library that it seems as if I might just be missing something.