- Joined
- Feb 21, 2016
- Messages
- 60
- Thread Author
- #1
Not sure if this is a bug or works as intended. But when filtering for NPC's and using the 'nearest()' it does find the 'nearest' on the grid but doesn't keep in mind the obstacles. So often enough instead of having the actual nearest it returns an npc that is far away because of the obstacle in between. Is there a way to use 'nearest' method api with obstacle awareness? Or was it supposed to be obstacle aware already?