Summary of bug here.
Heart Tub’s IO Functionality isn’t implemented properly, making it useless to connect it to anything else.
Steps to Reproduce
-Hook any of the Heart Tub’s events to a different piece of IO functionality, say hide/unhiding a heal volume.
-Hook up something with a toggle function, say a light switch, to the Heart Tub to turn it on or off.
##What Should Happen
-What should happen is when I click the “Turn On” button on the Heart Tub, it should both turn the Heart Tub’s vibrate function on, and trigger any connections tied to the “OnTurnedOn” event. Likewise, when the tub is turned off it should trigger its “OnTurnedOff” events.
-If you have some other type of IO feature that’s hooked up to toggle the Heart Tub’s vibrate function, it should toggle the Heart Tub’s vibrate function when triggered.
What happened
-Toggling the Heart Tub on with it’s “Turn On”/“Turn Off” button has no effect on anything tied to the “OnTurnedOn”/“OnTurnedOff”/“On Toggled” Events.
-If you have some other type of IO feature that’s hooked up to toggle the Heart Tub’s vibrate function, when you toggle it it does not toggle the vibrate function, but instead it only triggers the Events tied to the Heart Tub.