Where ClickDetectors changed?

At some point today, players of my game, Stop it, Slender! 2, started to complain about not being able to activate the generators, which use a ClickDetector. I haven’t updated the game in weeks so this seems like an issue with a client update. From what I can tell, the MouseClick event won’t fire unless your mouse is angled at an extremely specific spot, but the mouse cursor changes to the clickable one as you’d expect, so I know my mouse should be able to click the part. This seems to be happening in more than just one case; the pages in the game also take several clicks for the MouseClick event to fire and in another game of mine they’re also having troubles getting the event to fire.

Is anyone else’s game that uses ClickDetectors acting weird? My game uses a system that sends feedback to my Discord server, and the first complaint about this was 2:40PM CST, and since then there’s been a lot more, so it looks like this just started today.


The orange outline is the hitbox of the ClickDetector, and this is where my mouse had to be while spam-clicking for the MouseClick event to finally fire. Note that my cursor is the normal one as the game deletes the ClickDetector after the event fires.

Games of mine where this seems to be happening:

https://www.roblox.com/games/30869879/Stop-it-Slender-2 (Generators are almost impossible to activate as explained, and pages often take several clicks to pick up even though it’s just a single part with a ClickDetector in it.)
https://www.roblox.com/games/675444474/Kleptomaniacs (The glass on the display cases use ClickDetectors, and clicking at some angles doesn’t seem to do anything despite the cursor changing as expected.)
One thing to note is that in Stop it, Slender, the MouseClick event is being caught on the client, and on Kleptomaniacs it’s the server.

1 Like

Looks like an FFlag relating to ClickDetectors did change today.

I made this change D: . It was mean to make ClickDetector.MouseClick actually work like a mouse click, not a mouse up but it must have broken something. I have turned off the flag for now and will look into what happened.

4 Likes

Looks like it reverted it to normal, thank you.

I figured out why this happened. It turns out half the click detector code uses the hit point to determine the distance from the click detector, and half uses the center of the part. Because of this you can click a part when HoverEnter and HoverLeave do not fire. I will change all the distance checks to use the hit point, the fix for this should come out in about 2 weeks.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.