When a PathfindingModifier or both attachments of a PathfindingLink are parented to a part with CanCollide, CanQuery, and CanTouch set to false, they stop working and are ignored completely by the navmesh. I tested this on both the old and new pathfinding algorithms and the issue is there for both of them. I only noticed this today and I could not find any documentation on this behavior.
Note that this happens regardless of the value of PathfindingModifier.PassThrough or PathfindingLink.IsBidirectional
Reproduction Steps:
Turn on the “Navigation Mesh” and “Pathfinding Modifiers” visualization modes
For PathfindingModifiers:
- Create a Part with transparency=1 (to see the annotated area) and CanCollide=false
- Insert a PathfindingModifier into the Part. The annotated area should now be shown
- Turn off CanQuery and CanTouch on the Part
- The annotated area should now disappear from the navmesh
For PathfindingLinks:
- Create either one or two Parts
- Insert two attachments into the Part (or one in both if you created two Parts)
- Move the two attachments away from each other (any distance will do)
- Create a PathfindngModifier anywhere in workspace and set Attachment0 and Attachment1 to the two attachments created earlier
- The PathfindingLink should now be shown between the two attachments
- Turn off CanCollide, CanQuery, and CanTouch on both attachment’s parent Part
- The PathfindingLink should now disappear from the navmesh
Repro file: PathfindingRepro.rbxl (56.9 KB)
Expected behavior
PathfindingModifiers and PathfindingLinks should work regardless of CanQuery and CanTouch.