[Discussion] Turning CanCollide off in a tool's handle gives weird results

I’ve recently stumbled upon a sudden error in my script related to tools. The events and functions in my script seemed completely random. For example an event may trigger, but only with a 1/10 chance, and some of my functions never ran.

This obviously caused my script not to work generally speaking, but a function that still worked 100% of the time was the clone function. Now this function clones the tool that is inside of the character’s equipment folder to the player’s equip space, however neither the client or server displayed the tool in the equipment folder (even before cloning), but sure enough the cloned version of the tool popped up in the clone destination.

If you tried to print the tool, it would actually print, but clicking on the print would lead you to nothing in the explorer and lead you to an invisible model, which is probably the tool in its limbo state.

This is the weirdest thing I have experienced in Roblox Studio to date. The tool seems to exist in a sort of limbo, where it both exists and doesn’t exist at the same time.

This touches on the subject of tool’s collidability being buggy, but doesn’t really explain the odd situation it created for me. I’m interested of what you think of this, and if there is a simple explanation. There probably is: Why does turning CanCollide off create these results?

1 Like