WakeSpams
About
WakeSpams is a simple addon used to announce your usage of important abilities, such as mitigation cooldowns, powerups or interrupts, to your raid, party or in whisper to specific players. Branched out from its bigger brother (a raid cooldown tracker I'm currently working on) and skinned to the bone, WakeSpams is lightweight and straight to the point. I am willing to listen to feature requests, but I will not be bloating the addon, so an in-game config for this addon is probably as far as it goes.
What I initially intended for WakeSpams was to just have announces for Death Knights (as I wrote this addon for the maintank in our guild) and Priests (my own class), however when players of other classes requested to have an addon like this, with other similar addons not fulfilling their needs, I broadened the scope and later uploaded it here on WowAce.
Features
- Announces your dispels and dispel resists.
- Announces your taunt misses (immune, resist, etc).
- Announces your interrupts.
- Announcement of your (and your pet's) important abilities:
- When you activate them
- Countdown to when they are about to fade (optional)
- When they fade (optional)
Interface Options
You can add, modify and delete announcement settings on a per spell through the in-game config. It supports anything that has a spell ID and shows up in the combat log (this includes trinkets and pet abilities, as long as it's the right spell ID).
- Output Options:
- Global and spell specific settings for where to direct announcements based each of the following situations: when solo, in a party, in a raid, in a battleground, in arena, in Wintergrasp or Tol Barad
- Global and spell specific settings for where to direct announcements based each of the following situations: when solo, in a party, in a raid, in a battleground, in arena, in Wintergrasp or Tol Barad
- Adding spells:
- WakeSpams can, when you add a new spell, detect the best settings for it automatically. This is currently very simple, but it will be expanded upon later.
- Manually setting up each spell is also possible.
I've editted the original version to announce messages in the instance group. I've tested this on my main character and seems to work pretty good. Please test this.
Code is available on: https://github.com/Brainscrewer/WakeSpams
Due to the changes in the LFD/LFG/LFR systems, wakespams no longer works for these groups. Instead of /party and /raid they both are now /instance. There is no /instance option in wakespams, and thus one gets a lot of "you are not in a raid group" errors in LFR and a nothing being posted in LFD/LFG.
I adore this addon but this makes it pretty annoying at times.
Anyone have a fix for this?
Hi mate. Great addon but slight problem.
Reguarding interupts. The priest spell Silence is only working in PVE
Example " Interrupted: Rogue Wizard [Frostbolt]"
However this does not work in PVP anymore. For example if im dueling another player or in a BG and i interput a player cast spell with silence it does not work. and yes i have the correct Oput set. Now i remeber this working in the past.
I was wondering if this addon has the capability to announce cc casted on me? I'm a healer, and I'm looking for something that informs everyone when I'm cc'd and how long it lasts.
didnt work very good for monk tank/Heal CDs
Following these steps you should be able to add almost any spell, including trinkets and pet abilities:
1. Type /ws to bring up the WakeSpams options.
2. Go to your class tab.
3. Press add spell.
4. Type in the Spell ID. You can find this on sites such as wowhead. For example if I wanted to add Flash Heal (not a good idea), the link is http://www.wowhead.com/spell=2061 which means that 2061 is the spell id.
5. WakeSpams now asks you whether you want it to detect the spell automatically, which should be possible in most cases. In case it fails, you should be able to edit it manually.
6. Do as it says and cast the spell once.
7. After spell detection is complete, to make sure the spell was detected properly you can cast it again and it should (if successful) announce it in the chat. Each spell can have announcing behaviour changed individually in the spell's edit tab.
8. Done!
WakeSpams has been updated and should now be compatible with MoP thanks to zefter. I'm more than happy to respond to feature requests and bug reports as long as you use the ticket system: http://www.wowace.com/addons/wakespams/tickets/
Posted a ticket about WakeSpams Options not showing.
Love to see an update, keep up the good work!!
Any possibility to update for MoP?
Any plans to update for MoP?
I really love WakeSpams.
Please update. =)
Author missing for three months, unfortunately not a good sign.
Druids revive spell doesnt get announced anymore. Not entirely sure, but might be broken since patch 4.2
function WakeSpams:UNIT_SPELLCAST_START(_, unit, spellname, _, _, spellid)
there is the following:
-- Simulate combat log event
self:COMBAT_LOG_EVENT_UNFILTERED(nil, nil, "UNIT_SPELLCAST_START", _, UnitGUID("player"), UnitName("player"), nil, nil, target, nil, spellid, spellname)
replace it with:
-- Simulate combat log event
self:COMBAT_LOG_EVENT_UNFILTERED(nil, nil, "UNIT_SPELLCAST_START", _, UnitGUID("player"), UnitName("player"), nil, nil, nil, target, nil, nil, spellid, spellname)
should fix your issue. They made changes to the Event parse but forgot to update the function call from the SPELL_CAST_START handle, so it doesn't line up.
Time: 07/03/11 14:08:35
Count: 1
Stack: ...ibs\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147: in function <...ibs\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
[string "safecall Dispatcher[6]"]:4: in function <[string "safecall Dispatcher[6]"]:4>
[C]: ?
[string "safecall Dispatcher[6]"]:13: in function `?'
...ibs\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: in function `Fire'
...AddOns\Atemi\libs\Ace3\AceEvent-3.0\AceEvent-3.0.lua:120: in function <...AddOns\Atemi\libs\Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>
Locals: <none>
Besides that Divine Guardian and holy wrath aren't always announced.
Any ideas?
The alpha I have been working on wasn't ready for release when 4.2 hit.
I am busy with Firelands heroic progress this first week, but once we stop raiding 24/7 (probably around the end of the week) I'll get up a beta version, with most if not all of the current issues fixed. All it really needs at this point is interface options!
Was wondering if there is a way to distinguish NPC targets from Player targets.
So when I sap a Player it doesn't say there is a 60s duration.