Does CanQuerry effect Mouse.Target?

Im looking into better ways to filter Mouse.Target. Yes i know of Mouse.TargetFilter, I remembered reading about canquerry and playing with it but didnt know if it would make a part invisible to Mouse.Target. I reread the dev forum but didnt really come out with an answer. Has anyone tried it?

I went ahead and tested it and i guess i should have expected the answer. So canquerry being set to fault will make a part undetectable by a ray. So any parts you dont want being hit by a raycast but are too lazy to put it in raycast params you can just set canquerry to off. Only bad side is that if you need a part to be collidable at the same time then you probably need to reference it in raycast params.

TLDR: CanQuerry = false makes parts invisible to rays and Mouse.Target.

PS: The way i tested was by using Mouse.Target in a while loop. I pointed to a part with CanQuerry = true and in the code i printed the name of the Mouse.Target if Mouse.Target wasn’t nil. So when i first pointed, the part’s name printed. When i turned CanQuerry off in the explorer (while the same session was running) and went back to the game, the name wouldnt print when i pointed to the part. Only “Baseplate” would print. I ran the same tests with RayCasting from the plyr camera onto a part and turning CanQuerry off the same way. Same result.

1 Like