I wrote an addon named CombatAlarm (http://wow.curseforge.com/addons/combatalarm/) that may do what you want, but it's possibly broken now, and it is a terribly written addon. I all but abandoned it before BC ended, but I updated it when I came back at the end of LK. It might work, but be warned that no attempts were made to throttle events, and the spaghetti code involved is highly inefficient, but if all else fails, and if you can stand the worse addon written by yours truly, then I hesitantly suggest CombatAlarm. The usual software disclaimers apply; I'm not responsible if this addon overheats your CPU or otherwise destroys some hardware or stored data (no this is not serious, unless it really happens). Also I won't pay your repair bill once CombatAlarm blows up in your face right when you get some encounter's critical debuff (and yes, I'm really serious about this one. I'm a poor worgen.). Disable showing errors, as I never addressed an existing stack trace related to my laziness about displaying formatted combat log messages; I cheated, but it didn't work. I think this only applies if you choose to display the event's combat log message via your scrolling combat text display, And one more thing - forgive me for my sin against humanity that I have committed by writing this atrocity, and especially for keeping it around like the coding packrat I am.
What CombatAlarm does -- as well as DebuffAlarm, AuraAlarm, and the planned ScriptableAlarm -- is it plays sounds, displays icons or text, and in ScriptableAlarm (the other addons paint the background too) individual widgets per each alarm paint your entire screen's background some user-defined transparent color, blended with other active alarms (there will be a healthy selection of blend methods), and without obstructing the view of your surroundings too much (you can adjust the opacity of alarms individually or adjust the base opacity value to effect all alarms together). Right now AuraAlarm is the only "<blank>Alarm" addon that is up-to-date and written. Also, it has some annoying bugs and design flaws I never addressed before I got going on my tooltip addon and leaving AuraAlarm behind to collect dust.
Honestly AuraAlarm needs rethinking all together, and that is where ScriptableAlarm comes in. With it a savvy user can have the addon sound an alarm based on a custom lua script's return value -- if true the alarm's lit, and if false it's not active. The idea is you have the addon alert you as loudly as you want, and under any condition that the WoW API allows. That was sort of the idea behind CombatAlarm -- a highly generic addon in principle -- but the combat log isn't exactly a reliable source all the time, and it's very costly for an addon to process in the way CombatAlarm does, attempting to catch every single event and process it in real time. And the worse part about combat log events is that some auras don't appear in the logs, such as LK's necrotic plague, hence me abandoning the combat log based DebuffAlarm in favor of AuraAlarm, which just polls aura data.
In ScriptableAlarm you should be able to base an alarm on a combat log event, any other frame event, or you can poll unit data at each WidgetAlarm update. Then ScriptableAlarm will display the alarm based on your script's runtime conditions. Practically anything you can do with an addon that alerts you to some event or condition should be doable by some lower-level configuration of ScriptableAlarm, and later down the road there will exist optional user-friendly option tables with predefined and behind-the-scene alarm scripts that are custom fit to the user's needs, such as injecting specific spell IDs or whatnot into predefined, and addon provided code templates.
But yeah, back to directly answering your question instead of giving possibly false hopes about the ultimate upcoming alerter addon (cough-ultimate-cough). Try CombatAlarm if you're absolutely desperate and out of choices (a small technical note, you'll need to obtain some knowledge about how combat log events are designed if you don't already know. Let me know through a PM if I can help in any way with the learning curve involved, but bring a combat log of the related events). Here's a resource that may come in handy (http://www.wowwiki.com/API_COMBAT_LOG_EVENT) And lastly, If you're interested in more powerful and advanced alarms, then keep an eye on the Wowace forum's General Addons discussion for my inevitable chatter with my boring and lone self about the development of ScriptableAlarm. That's likely next on the agenda after I restructure a library of mine.
If for some reason CombatAlarm is your last hope, and you then discover that it has acquired an addon-crippling bug since last expansion, then let me know and I'll see about fixing it for you -- with hammers and duct tape of course.
TY so so much! I am going to look into this now. I used to know alot about the combat log events back when I used to play alot, in BC. I remember studying that wiki page alot, and I am going to re study it now before I contact you so I can have a solid base knowledge.
edit: I got msbt to trigger on resist but I can't get it to trigger on a target dispeling or purging and the like
Create a new trigger, and click the Add Event button in the trigger config window that pops up. Change the Main Event dropdown to select the Aura Dispel event. Delete both of the default conditions that appear, and then click the Add Condition button. Set up this condition:
Condition: Source Unit Affiliation
Relation: Is Equal To
If you only want to know about hostile targets, or player targets, or both, you can add more conditions:
Condition: Source Unit Reaction
Relation: Is Equal To
Condition: Source Unit Control
Relation: Is Equal To
Wow thank you alot for that. I am now able to get MSBT to show the notification text however It will not fire the mp3 file, which is in the folder. Yea it's in there before loading and yea it even sounds it when you hit "play" in the gui... so really weird.