Locked does something slightly different: Clicking on something that’s locked will specifically act as though you clicked on nothing. Clicking on something that’s CanQuery = false will currently act as though you clicked on whatever lies beyond it.
20 Likes
This is something especially needed for plugins. Being able to disable selection for specific parts (while having the dragger raycast pass through) is a feature I’ve been waiting for.
I got excited about this beta, but since preventing selection is unintentional behaviour, I’m a little disappointed now.
5 Likes
In Part.Locked the raycast still hits the part, but it is just not selected. With the CanQuery the raycast itself will ignore the part, that means you will be able to select a part behind a part, you are not able to do that with Part.Locked.
4 Likes
So will this allow a part with Query set to false to not be clicked by the draggers in studio? I always would try to set transparent parts (such as ones just to block players from wandering where they shouldnt) as locked only to be blocked when trying to click parts through them. It was very annoying, so I stopped using lock, as it really served no purpose for me.
6 Likes
Wondering if this somehow has something to do with the Pathfinding Service in the future. A nice addition to have though.
5 Likes
holy crap this is SO HELPFUL thank you so much Roblox, now i can finally ignore the HumanoidRootPart within raycasts for melees
6 Likes
FYI, you could always ignore or whitelist specific BaseParts in the Workspace. Just input a RaycastParams parameter to your Workspace:Raycast call:
local Workspace = game:GetService("Workspace")
local humanoidRootPart = ...
local raycastParams = RaycastParams.new()
raycastParams.FilterType = Enum.RaycastFilterType.Blacklist
raycastParams.FilterDescendantsInstances = { humanoidRootPart }
local origin = Vector3.new()
local direction = Vector3.new(0, 1, 0)
Workspace:Raycast(origin, direction, raycastParams)
10 Likes
Locked does not let you select parts behind the Locked part.
4 Likes
Will this work with Workspace:FindPartOnRay or is it just Workspace:Raycast?
4 Likes
isn’t that what locked is for lol
4 Likes
IIRC they both use the same raycast code internally, so I assume that it should still work properly in this case too
4 Likes
Reference to reply to this above:
3 Likes
3 Likes
oh, that definitely could use changing tbh
5 Likes
Explain Why it would need changing?
5 Likes
To note, I rely on setting a collision group on a part my plugin Studio Tweaks creates as a proxy for its own selection box override. This is necessary for obvious reasons (you don’t want to drag the selection box off of parts…). I would replace this with whatever solution Roblox provides to allow draggers to ignore parts.
2 Likes
This may cause some issues related to exploiting for shooting games, as instead of having to manipulate metatables and stuff like that to achieve wallbang, now all a exploiter has to do is set canquery to false on walls
4 Likes
Well, that’s your fault for relying on the client in the first place.
9 Likes
Roblox has been killing it with these updates as of late.
4 Likes
but I see nothing…
Instead of hiding the property entirely, I think it should be greyed out (read only state) instead so people know it exists, then you can unlock the property when CanCollide is false.
This should probably be a setting though since some users might be annoyed to see a property they don’t use often
16 Likes