The Clickdetector Problem

Join Date: 2009-07-05
Post Count: 108

#138544624Saturday, June 28, 2014 10:09 PM GMT

I put the following script into a clickdetector parented to a part. script.Parent.MouseClick:connect(function () print'derp' end) And it failed to work when testing in server. The button refused to print anything when clicked from a player, and yes I checked the output in the server window, not the client window. What am I missing here?

Taser597

Join Date: 2009-07-05
Post Count: 108

#138545848Saturday, June 28, 2014 10:21 PM GMT

Is this a bug?

xXBestPieXx

Join Date: 2012-11-08
Post Count: 1271

#138546063Saturday, June 28, 2014 10:23 PM GMT

Put function onClicked(part) print(derp) end script.Parent.ClickDetector.MouseClick:connect(onClicked) and make sure that the script is in the part, not the click detector.

Aesthetical

Join Date: 2014-01-01
Post Count: 2141

#138547530Saturday, June 28, 2014 10:36 PM GMT

You have to connect the function to the ClickDetector object, not the brick itself.

Taser597

Join Date: 2009-07-05
Post Count: 108

#138548506Saturday, June 28, 2014 10:46 PM GMT

The problem appears to have been caused by FilteringEnabled. I thought I tested it with FilteringEnabled off, but apparently not. It makes sense even if it's really annoying.

Taser597

Join Date: 2009-07-05
Post Count: 108

#138549029Saturday, June 28, 2014 10:51 PM GMT

It seems that there is no special exception for ClickDetectors, so FilteringEnabled prevents the event from firing server-side. This will mean a bunch of ugly workarounds with ReplicatedStorage. The price of fighting exploiters is high.

Aesthetical

Join Date: 2014-01-01
Post Count: 2141

#138550449Saturday, June 28, 2014 11:04 PM GMT

Just use GetMouse().