Loss Of Control

Loss Of Control announces when you are suffering from a *Loss Of Control* event, e.g., stunned, silenced, spell-locked, etc., that prevents you from performing your role.

File Details

2.5.0

  • R
  • Nov 30, 2018
  • 170.30 KB
  • 257
  • 8.0.1
  • Retail

File Name

LossOfControl-2.5.0.zip

Supported Versions

  • 8.0.1

Loss Of Control

2.5.0 (2018-11-30)

Full Changelog

  • Rename the UNIT_AURA event handler for consistency.
  • Improve the debugging message for role changes.
  • Use MooSpec-1.0.6 to get class information for group members.
    Garbage-collect unused code to manage GUID-to-class mappings.
  • Sort Loss Of Control events based on severity to a healer.
    Assign priorities to Loss Of Control events based on how severely
    it affects a healer using two criteria: can still move, and can
    still cast spells. Report higher priority Loss Of Control events
    even if they expire sooner. When the higher priority events
    expire, resume reporting the lower priority events.
    Be consistent about using the total duration of Loss Of Control due
    to events at the same priority when deciding whether to announce or
    alert based on the user-settable thresholds.
  • Always broadcast Loss Of Control to allow alert thresholds to work.
    The decision to broadcast Loss Of Control was inside of a check for
    duration exceeding announcement threshold, which effectively meant
    that the announcement threshold was erroneously a floor for the
    alert threshold. Move the broadcast outside of the check so that
    the receiver's alert threshold will be used.
  • Fix the calculation of expirationTime.
    Use (startTime + duration) instead of figuring out the expiration
    time from the time remaining because the former calculation uses
    fixed values determined when the Loss Of Control event occurred.
  • Rename a local variable for clarity.
  • Shadow Prison stuns in Western Plaguelands.