ClickDetectors do not always fire when parented to a model with multiple parts

[Entelogical]

If you take the repo place, run your mouse constantly over the model with multiple base parts and it won’t fire if the mouse is moving. The mouse has to be moving. It does fire as expected on the model with a single part

Bug.rbxl (54.8 KB)

[Metallochrome]

I’m also experiencing this issue but 100% of the time, recently any models with a click detector in it do not work at all unless I parent the click detector directly into an actual part.

[thirdtakeonit]

Thanks for the report! We’ll follow up when we have an update for you.

[PrinceTybalt]

ClickDetectors require you to keep your cursor over the same part from the moment the mouse is pressed until it is released. Otherwise the mouseClick event will not be fired. it doesn’t matter if the parent is a Model. Each part can work as a clickDetector, but the focus is lost if you switch parts. This is why if you run the cursor over the same part before releasing it DOES fire; but if you cross onto another part it does NOT fire.

You can, however, get the behavior you want with DragDetectors. DragDetectors do NOT lose focus when the cursor leaves the part you clicked.

In the attached model, I’ve done the following:
[1] replaced your ClickDetector with a DragDetector
[2] set DragDetector.ResponseStyle to Custom. This makes it so that the DragDetector does not actually move the part/model that you click on. (Instead it just updates the DragDetector.DragTransform with information that in this case is being ignored, but can be used for custom purposes)
[3] Changed the script to respond to the DragDetector.dragEnd signal instead of the ClickDetector.MouseClick event:

DragDetectorAlwaysFires.rbxl (56.5 KB)