When dismounting via /dismount macro, the event for PLAYER_MOUNT_DISPLAY_CHANGED and UNIT_AURA fire at the exact same frame OR UNIT_AURA fires about 50-100ms before. This means the /10 Blizzard bug does not occur and the transition can skip applying the *10 correction completely.
However, when dismounting using the Journal dismount button OR by clicking/keybinding the mount icon, there is a 50-300ms delay between the PLAYER_MOUNT_DISPLAY_CHANGED and UNIT_AURA event, with UNIT_AURA always arriving second. This means the /10 Blizzard bug applies between those events and the correction is mandatory.
The issue is, SOMETIMES the /10 Blizzard bug persists for a few frames AFTER the UNIT_AURA event fires. This is noticeable as a camera jerk - to the left, then back to the right as everything corrects itself. This is random and unpredictable. We remove the *10 correction on the UNIT_AURA event, thinking the /10 Blizzard bug is removed on it (and it should be), but sometimes it persists a bit longer.
My assumption atm is that UNIT_AURA does not predict the removal of /10. It just coincides with a different event that is the true removal of /10.
TODO:
- Find this event and watch for it instead of UNIT_AURA.
When dismounting via /dismount macro, the event for PLAYER_MOUNT_DISPLAY_CHANGED and UNIT_AURA fire at the exact same frame OR UNIT_AURA fires about 50-100ms before. This means the /10 Blizzard bug does not occur and the transition can skip applying the *10 correction completely.
However, when dismounting using the Journal dismount button OR by clicking/keybinding the mount icon, there is a 50-300ms delay between the PLAYER_MOUNT_DISPLAY_CHANGED and UNIT_AURA event, with UNIT_AURA always arriving second. This means the /10 Blizzard bug applies between those events and the correction is mandatory.
The issue is, SOMETIMES the /10 Blizzard bug persists for a few frames AFTER the UNIT_AURA event fires. This is noticeable as a camera jerk - to the left, then back to the right as everything corrects itself. This is random and unpredictable. We remove the *10 correction on the UNIT_AURA event, thinking the /10 Blizzard bug is removed on it (and it should be), but sometimes it persists a bit longer.
My assumption atm is that UNIT_AURA does not predict the removal of /10. It just coincides with a different event that is the true removal of /10.
TODO: