The MouseHoverLeave event fires when a player’s
Mouse|mouse moves off of the
ClickDetector's parent. This event fires when using either a
Due to the nature of user input, you ought not depend on all
ClickDetector/MouseHoverEnter|MouseHoverEnter events to fire a matching MouseHoverLeave event.
The player does not have to click the ClickDetector for this event to fire. If you want an function to run when the player clicks, you can use
Creating a ClickDetector Door
The code sample below demonstrates the functionality of a
ClickDetector and its properties and events.
First the code creates a ClickDetector and set’s its
Instance/Parent|parent to the
door. It also sets the
ClickDetector/MaxActivationDistance|maximum distance players can interact with the ClickDetector to 10 studs and set’s the ClickDetector’s
Then, the code connects the ClickDetector to several events, including changing the door’s
BasePart/Transparency when the player’s mouse hovers
ClickDetector/MouseHoverLeave|off off the door. The player opens the door by
ClickDetector/MouseClick|left clicking their mouse while over the ClickDetector and closes the door by
ClickDetector/RightMouseClick|right clicking their mouse while over the ClickDetector.
This code works in a
Script and a
LocalScript as long as the script’s parent is the door
Mouse Hovering On and Off of a ClickDetector
The below code will print “Oh my… PlayerName left the confines of my parent” when a player’s mouse is moved off of the
ClickDetector|ClickDetector's parent, replacing “PlayerName” with the player’s name.
It will also print “Oh my… PlayerName hovered over my parent” when a player’s mouse hovers over the ClickDetector’s parent, replacing “PlayerName” with the player’s name.
In order for this example to work as expected, it must be placed in a
LocalScript whose parent is the ClickDetector.