promotional bannermobile promotional banner

Storm, Earth, and Fire

Tracker for Storm, Earth, and Fire spirits

File Details

v1.0b2

  • B
  • Mar 17, 2013
  • 27.88 KB
  • 125
  • 5.2.0
  • Retail

File Name

StormEarthAndFire-v1.0b2.zip

Supported Versions

  • 5.2.0

tag v1.0b2
6351154709c8222f0f18f7cd063e7d9b11074de3
Kevin Ballard <kevin@sb.org>
2013-03-16 22:20:51 -0700

Tagging as v1.0b2

--------------------

Kevin Ballard:
    - Better error message for invalid /sef invocations
    Also change config list to `/sef config list`, so `/sef config` gives
    the sub-commands.
    - Play a sound when a spirit dies
    - Don't check arena units unless we're in an arena
    - Be more careful with mouseover units
    The mouseover unit can silently disappear with no (reliable) event,
    whenever a mouse button is pressed, so UnitTracker cannot track this
    unit reliably.
    
    As such, always try to push mouseover to the end of the unitid list, so
    it will only be used when we have no other choice.
    
    Furthermore, in UpdateRaidIcons(), if the unit is mouseover,
    double-check that it actually exists before believing it when it says
    there's no raid target icon.
    - Restrict UNIT_TARGET to only valid units
    We don't want to risk getting a unit that we don't scan for in
    UNIT_TARGET or we'll never get the unitid out of our system.
    - Clear party/raid units when leaving group
    - Show raid icons for the spirit targets
    When we have a known unitid for a spirit's target, use it to look for
    raid icons. When we lose access to a target, dim out the icon to
    indicate stale data.
    - Add a unitid tracker
    Track when spirit targets gain and lose unitids. This can be used later
    to potentially show target information (e.g. health, raid icon).
    - Use the localized spellname in config mode
    Instead of hard-coding the name "Storm, Earth, and Fire" in config mode,
    just use whatever the game thinks the spell name is.
    - Remove the custom callback code from DB
    We already have CallbackHandler, so we may as well use it to power our
    DB callbacks.