oUF Indicators

oUF_Indicators shows buffs, not debuffs... What you are thinking of is already possible with oUF_DebuffHighlight

DogTag is a bit big and imo would defeat the whole point of oUF.

Id say it would be easier and better (or something) to let a layout/ouf support LibDogTag-3.0 and implement text strings (like dots and so colored after buffs, ive seen this in some interfaces on diffrent sites, looks cool )

Ammo and Rabbit have developed or co-developed some major addons, code from oRA2 and BigWigs are from both hands, not to mention the number of addons both have developed individually.

Really, take their advice and use it

God dammit.

Ammo beat me to it by one hour! :P
Seriously, your code is really, really bad, and you need to fix it. If you want more help, please join #wowace on freenode.

Wow...

You know there are better ways to detect debuffs. There is are events firing for them (UNIT_AURA) and you can respond to that instead of creating a gazillion onUpdates.

Also spells have IDs nowadays that can be used, removing the need for localization.

This addon will indeed eat my babies.

Hints on fixing:
1. Look at oUF_DebuffHighlight and implement a PostUpdateAura hook similar, removing the need for overwriting any active OnUpdates on the unitframes. Your method is destructive.
2. Use spellIDs you can find them on wowhead. Just look up the debuff you want to detect and you can build your names table using GetSpellInfo()
3. Don't loop the 40 buffs and debuffs for every single spell you want to find. Loop once and check all spells.
4. read up on local vars and global vars, you have a few globals leaking in your addon (line 38, 53, and similar)
5. You use a string value "true" and "false", you can use: local boss = true
instead of using a string.

-Ammo