LiteButtonAuras shows your buffs on you and your debuffs on your target inside your action buttons with a colored border and timer. It is like AdiButtonAuras, and Inline Aura before it, just much dumber and much easier to maintain.

A buff you cast on yourself shows a green highlight in ability button:

A debuff you cast on your target shows red highlight in ability button:

For all of your action buttons:

• Suggest button (border glow/ants) with timer if:
  • your target is casting a spell you can interrupt and the button action is an interrupt, or
  • your target is enraged and the button action is a soothe
• Show a green highlight and timer if:
  • the action name matches a buff on you that you cast, or
  • the action is a totem or guardian and it is summoned
• Show a red highlight and timer if:
  • the action name matches a debuff that you cast on your target
• Show a debuff-colored border (curse/disease/magic/poison) if:
  • your target is an enemy, and
  • you can purge the buff, and
  • the button action is a purge/spellsteal

LiteButtonAuras works with the default Blizzard action bars, Dominos, Bartender, ButtonForge, ActionbarPlus, and anything that uses LibActionButton (including ElvUI).

Supports WoW retail, classic era (Vanilla/SoD) and classic (WotLK).

Support for interrupts and timers on classic is now baseline in the WoW API. You don't need to install any other libraries.

Compared to AdiButtonAuras (which this addon was modeled on), LiteButtonAuras:

1. matches buffs/debuffs by name, so it doesn't require manually maintaining spells every expansion.
2. has less code and hopefully uses less CPU (probably not though).
3. has limited support for custom rules (only "show aura on ability").
4. doesn't show buffs/debuffs on abilities that have a different name unless manually configured.
5. limited support for customizing (timer appearance, location, show stacks or not).
6. doesn't show hints for using abilities, except for interrupt, purge and soothe.
7. doesn't show holy power/chi/combo points/soul shards.
8. doesn't handle macros that change the unit (always assumes target).

AdiButtonAuras seems to be maintained again, so if you want some extra features give it a look.

LiteButtonAuras has a configuration panel that you can open from the Blizzard settings or by using the /lba opt slash command.

You can adjust the visual appearance of the ability overlay, as well as add and remove extra aura displays where the name doesn't match.

You can also adjust the options via slash command.

/lba - print current settings
/lba help - print help
/lba colortimers on | off | default - turn on/off using colors for timers (default on)
/lba decimaltimers on | off | default - turn on/off showing 10ths of a second on low timers (default on)
/lba stacks on | off | default - turn on/off showing buff/debuff stacks (default off)
/lba font default - set font to default (NumberFontNormal)
/lba font FontName - set font by name (e.g., GameFontNormalOutline)
/lba font FontPath - set font by path (e.g., Fonts\ARIALN.TTF)
/lba font Size - set font size (default 14)
/lba font FontFlag - set font flag (OUTLINE or THICKOUTLINE)
/lba font FontNameOrPath Size FontFlag - set font by name/path, size and flag

If you are changing the font from the default, you will (almost certainly) want to use fonts with the OUTLINE flag (shows a dark border around) for them to be visible.

The default LBA font NumberFontNormal has an outline, but (for example) GameFontNormal doesn't and you'd need to use GameFontNormalOutline instead or explicitly set the OUTLINE flag.

Note that setting colored fonts will not use the color, only the font, size, and flags. There is no difference in LBA between NumberFontNormal and NumberFontNormalYellow.

By default LiteButtonAuras only shows highlights when the name of the buff/debuff and the name of the action match. (Plus a special case for totems and guardians like monk statues.)

Using the /lba aura command you can add extra auras that will highlight your abilities (for example, to show a debuff on the ability that triggers it).

/lba aura list - list current extra aura mappings
/lba aura add <auraSpellID> on <ability>
/lba aura remove <auraSpellID> on <ability>

If an ability is in your spell book you can use it by name otherwise by spell ID.

You can only add auras using this, or remove ones you previously added. You can't use "hide" to change the default behaviour of showing buffs/debuffs that match the ability name.

You can stop an ability from ever getting highlighted due to the default name matching.

/lba ignore list - list abilities never to highlight
/lba ignore add <ability>
/lba ignore remove <ability>

If ability is in your spell book you can use it by name otherwise spell ID.

Every ability and every buff/debuff has an associated Spell ID, which you need to know to configure custom highlights (above).

LiteButtonAuras doesn't include any helpers for finding spell IDs, you'll need to do it yourself. Here are three ways to do this:

1. Look up wowhead.com. The spell ID is the number after spell= in the URL.
2. Get an addon that adds Spell IDs to the tooltip.
3. If you have the Details! addon, it keeps a list of spells you can view with /details spells

1. Macro @units. There's no simple way to figure out what unit an action will target. It can be done with a lot of complex processing, maybe. If Blizzard ever added a GetActionUnit() I would do it in a heartbeat so I can have focus interrupt suggesting.
2. Non-Auras. E.g. channeling time, combo/chi/holy power/etc points. A lot of these could be done, but LBA's focus is on auras only and I personally feel those are better done in other ways or by other addons.

In general a lot of not supporting things involves keeping LiteButtonAuras small and simple enough that when a major WoW release comes out I can update it without causing myself so much stress I give up.

If more than two weeks go by after a major patch and this addon isn't updated, I've probably been hit by a bus. In that case I encourage anyone with the necessary ability to take over maintenance of the addon. It is released under the terms of the GNU General Public License, which means anyone can take it and do whatever they want with it, as long as they don't claim they wrote it and they too release their code under the same terms.