Clicking on a part in-game that contains a ClickDetector that’s within range of MaxActivationDistance no longer triggers the Mouse.Button1Down event. I depended on the old behavior as it allowed me to organize my object clicking code in an easier to use manner while still utilizing the icon-changing behavior of ClickDetectors. I understand there were some recent tweaks to ClickDetector behavior, but I didn’t think anything like this was outlined in the proposed changes.
You can see this exhibited here:
ClickDetector.rbxl (14.7 KB)
Watch the local console. Anytime you click the baseplate it tells you, but when you click the smaller gray part nothing gets printed.
I think this has been a pretty recent issue, maybe within the past week or so at most, but I can’t pin down an exact date as to when this began occurring.