Clickdetectors now work with FilteringEnabled

<3

2 Likes

they’ve always worked for me? unless something changed recently

If you attempted to listen to the event ClickDetector.MouseClick on the server, it wouldn’t work.

Clientside did work.

Also this only applies to FilteringEnabled games

oh yeah, ok

Can we get this for dialog next :slight_smile:

I’d actually prefer Dialog 2.0 where we have control over the appearance/functionality of dialog bubbles/response frames i.e. use custom images, choose where the response frame floats (corner, top, and the like), etc so there’d be a reason to use it

4 Likes

This fixed so many things, thanks for the update, always had me do a remote function which was annoying :wink:

What’s this dialog 2.0?

Documentation - Roblox Creator Hub ?

What’s broken about it in FE?

Take it one step further and please update the icon for the ClickDetectors? If this happens then @spotco will be my favorite staff (sorry zeuxcg). :heart_eyes:

From what I remember when I last used them, there were three major issues.

  1. The events did not fire server-side

  2. Once you finished ‘speaking’ to a dialog the bubble did not re-appear like it is supposed to

  3. Others could not see you speaking to the bubble / multiple people could speak to a bubble at once

1 Like

I’ll take a look. This one seems to be more involved.
Any examples of major games that use this?

(I’m guessing the robot in Welcome to ROBLOX Building - Roblox is one of them)

Server Clickdetectors don’t seem to work on mobile with filtering enabled.

Your mobile version might not be up to date.
Can you verify that you’ve got the latest version from your platform app store?

I have the latest android version on tablet.

Haven’t tested this, but this should be fixed with their next release (I think it’s tomorrow? was pushed back a day).

If a client moved a part closer to themselves and click it, would it still fire on the server even if the player was too far away?

1 Like

yes

1 Like

I suppose that’s to be expected. It just means that they still need to be validated by the server, slightly negating the usefulness of them working with FilteringEnabled. Still… I appreciate that I don’t need to have a BindableEvent with my ClickDetectors.

1 Like