If a delay is specified in the properties for the Unhide event (like shown in the screenshot below), the event is never processed.
This field is meant to allow the mapper to have the event in question processed following the specified delay. For most events this works fine, but for Unhide (and probably some others), specifying any delay at all appears to make the event do nothing.
"event_debug_msg" confirms the Unhide isn't being processed at all when a delay is specified. See screenshots below - Unhide with a delay does nothing, but Explode with a delay processes as intended following the delay (as an example of an event that works properly with a delay).
If a delay is specified in the properties for the Unhide event (like shown in the screenshot below), the event is never processed.
This field is meant to allow the mapper to have the event in question processed following the specified delay. For most events this works fine, but for Unhide (and probably some others), specifying any delay at all appears to make the event do nothing.
"event_debug_msg" confirms the Unhide isn't being processed at all when a delay is specified. See screenshots below - Unhide with a delay does nothing, but Explode with a delay processes as intended following the delay (as an example of an event that works properly with a delay).
Unhide event with no delay specified (0.0 sec):
Unhide event with a delay specified (0.1 sec):
Explode event with no delay specified (0.0 sec):
Explode event with a delay specified (0.1 sec):