This project is abandoned.

Whether this project is out of date or its author marked it as abandoned, this project is no longer maintained.

If you wish to take this project over, please report it and state your intentions.



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.


  • 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).

  1. 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

  2. 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.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Cyrila Cyrila Dec 22, 2010 at 23:43 UTC - 0 likes

    Actually nevermind making a ticket, it was quite an easy addition... r58 has announcements for every Resurrection spell.

  • Avatar of Cyrila Cyrila Dec 22, 2010 at 22:22 UTC - 0 likes

    The problem with having spells announced when they start casting rather than when they finish, as per your example, is that the SPELL_CAST_START combat log event contains no target information. So unless I let WakeSpams listen to additional spellcasting events, there's no way to retrieve the target.
    In other words: It's the correct combat log event, but it might not have the data you are looking for - At least I'm guessing you'd want to announce something like "Casting Resurrection on X" instead of simply "Casting Resurrection", which is all it can do atm.
    You are welcome to create a ticket if you like and I'll keep you posted on when I have added appropriate tracking.

    Last edited Dec 22, 2010 by Cyrila
  • Avatar of Malazee Malazee Dec 22, 2010 at 18:46 UTC - 0 likes

    Is there a setting that would enable me to set an added spell to announce when I begin casting rather than when I complete the cast? Similar to the way most channeled spells work (like Hymn of Hope and Divine Hymn).

    I added "Resurrection" as a new priest spell for wakespams and ideally it should announce that I am casting Resurrection when I begin, not when the cast completes. I allowed wakespams to detect the spell automatically and these are the settings it put in:

    Duration of the spell (in seconds): 0 Combat Log Event: SPELL_CAST_START

    I'm assuming I should change the combat log event to something else in order to get the announce at the start of the cast, but I don't know what that would be.

  • Avatar of potatoboy potatoboy Nov 29, 2010 at 06:03 UTC - 0 likes

    Added ticket number 3

  • Avatar of Mishii Mishii Oct 22, 2010 at 01:22 UTC - 0 likes

    Thanks Cyrila!

    at the time of this comment, when I loaded up Curse Client, it's stating that the newest is 2.0.51-stable, so I'm guessing I can go with that instead of the beta :P


  • Avatar of Cyrila Cyrila Oct 21, 2010 at 15:44 UTC - 0 likes

    You have downloaded an outdated version (probably 1.1). If you're using the Curse Client, change "Preferred Relase Type" on WakeSpams from release to beta and re-download. The current version is 2.0.50-beta.

    It's something I have been considering, but most of the addon is written around the idea that you can only have 1 output per spell id. I'll put it on my todo list.

    You're probably using the wrong Spell ID. I can find 4 different Spell IDs for Will of The Necropolis, try another one of those.

  • Avatar of Mishii Mishii Oct 21, 2010 at 04:53 UTC - 0 likes

    I just downloaded this, and I can't get any options. i use /wakespams, and it comes up with help, and says this addon has no config - use LUA files. i don't know how to mess with LUA files, let alone if my computer can edit them.

    Did I do something wrong?

  • Avatar of neanor neanor Oct 15, 2010 at 21:05 UTC - 0 likes

    Loving this addon so far. I'm wondering - will it ever be possible to have two outputs? For example, if I want to announce something in the healer channel in addition to whispering somebody?

  • Avatar of Alcotraz Alcotraz Oct 15, 2010 at 17:46 UTC - 0 likes

    Aha I see. I got Rune Tap working now thanks to that but its not quite working for Will however :( The message stays up even after Will procs.

    Last edited Oct 17, 2010 by Alcotraz
  • Avatar of Cyrila Cyrila Oct 15, 2010 at 17:23 UTC - 0 likes

    You should only leave the event fields blank if it's an aura, since that's the primary event it scans for. I would advice you to use automatic detection, since it fills in the event fields automatically (you can delete custom spells in the edit tab). The only caveat with automatic detection is that you would have to cast the spell first, which in fact shouldn't be a problem since the spell detection doesn't have a limited time frame. You just might get the "spell detection was succesful" popup in the middle of combat though.

    Last edited Oct 15, 2010 by Cyrila


Date created
Jul 14, 2010
Last update
Oct 16, 2012
Development stage
  • enUS
GNU General Public License version 3 (GPLv3)
Recent files



Embedded library