RaidWatch 2

In Action

Raid Watch 2

Raid Watch is an addon for tracking events during boss fights in both raid and 5-men dungeons. It will keep track of important boss cooldowns, warn for events that requires the users attention and inform about some things that happen around him. It will do this in the form of timer bars, sounds, big warning text accompanied with a screen flash for the most important stuff and small text messages for less important things, direction arrow and more.
Raid Watch also have some functionality that is useful outside of boss fights, such as in game eqDKP display.

I have decided to disable the comments on since they are hard to keep track of, so instead:
For comments, suggestions, bug reports and general chat please post in the Raid Watch forums


From version 1.46 there is now a new module that handles the new alternate power bar that blizzard added. This bar is used in a few encounters and quests so far, for example Cho'gall for the corruption and Atramedes for the sound bar. This new plugin let you position it, or hide it completely and instead show a normal bar using the multi-purpose bar plugin that is used for health bars and other small things atm. The options for this plugin can be found under Plugins -> Alternate Power Bar.

How To


  • Timer bars Gives an easy overview of given events during an encounter
    • All timers will move between 2 or 3 anchors depending on their the length of the duration they have left. These anchors can be moved freely and placed individually. You can also configure at what duration they should move to each anchor.
  • Personal warnings Easy to react to message that is only shown to yourself when it concerns you
  • Messages Messages show about events happening to the raid or the boss in question.
  • Health frames Shows the current health of the boss, and also npcs when usefull. Can also be used to show other things besides health. One example i the Blood Power stacks in the Deathbringer Saurfang encounter.
  • Raid marking Automatic raid marks for important events that happen to players or NPCs.
  • Directions For some events you will get arrows pointing towards the point of interest.
  • Customization
    • Each event that is tracked in an encounter have detailed settings where you can turn of messages, timers and icons individually depending on your current role.
    • Colors and sounds can be individually set for each type of warning for each event.
    • Fonts, textures and colors can also be set on a global space to be able to make fast changes and have a uniform look of all objects.
  • Statistics You can see how many times you have done each encounter, how many times you defeated it, how many wipes. You can also see your fastest kill so far. All this is recorded separately for 10- and 25-men raid and also for normal and heroic.
  • Load on Demand All boss mods are in their own modules and are not loaded into memory until they are needed, and this will be done automatically. But can also be loaded manually if needed for configuration before raids.

Including mods for

  • The Ruby Sanctum
  • Icecrown Citadell
  • Crusaders Coliseum
  • Ulduar
  • Vault of Archavon
  • 5-men
    • Forge of Souls
    • Pit of Saron
    • Trial of the Champion


Raid Watch 2 is fully or partially translated to most languages, but could use some more people to help with the translation as they are important to make the mods to work for all languages. At any point where boss emotes or yells are used as triggers it will or may not work on other clients. But things that only rely on combat log events will still work.

If you want to contribute to the localization simply go to the Localization page or click the localization tab up top and then on your language and start translating. It is open for anyone as long as you have an account here.


  • Ideas and Inspiration: DBM, BigWigs
  • Ulduar Mod: Mcslein
  • Bad Omen For testing and feedback.

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

  • Avatar of tlai tlai Jul 10, 2010 at 04:29 UTC - 0 likes

    Yes after the boss is dead it blows up and i get memory error :(

  • Avatar of DaemonSambe DaemonSambe Jul 10, 2010 at 04:11 UTC - 0 likes

    Something introduced the the builds over the last couple of days is causing serious problems. Doing ICC.10 tonight, i had 3 fatal wow errors, and all as soon as a boss died. On Saurfang, Stinky and Precious, upon death, wow crashed out completely with a memory error. As RW is one of the few mods that would be specifically watching boss death, i turned it off... and did Fester/Rotface, Professor and Princes without crashing. I turned it back on for Queen and it crashed out again.

    I raided Thursday night without a problem however, doing the same mobs in ICC.10.Heroic. And i believe i updated right before raid time at 10est.

    A few hours later, i did 25m. I had reverted to b494 and was able to complete the raid without a crash.

    Last edited Jul 10, 2010 by DaemonSambe
  • Avatar of tlai tlai Jul 10, 2010 at 02:36 UTC - 0 likes

    Where's the options of the role selectable timers? I see it in the change log but do not see it in the config. Going to see if i lagg again at putricide, looking at the poster below who has the same issue i also use hudmap.

  • Avatar of mysticalos mysticalos Jul 09, 2010 at 05:20 UTC - 0 likes

    lies. i'm on a mac. it breaks CONSTANTLY, although only on halion and lich king. i don't think i've ever seen it ever break anywhere else.

  • Avatar of kagaro kagaro Jul 08, 2010 at 23:32 UTC - 0 likes

    you know the combat log doesnt break on the mac as far as ive seen.

  • Avatar of mysticalos mysticalos Jul 08, 2010 at 23:08 UTC - 0 likes

    i installed shadowed's mod for now

    which basically monitors UNIT_SPELLCAST_SUCCEEDED on self, and then if it doesn't fire in CLEU afterwards, clear combat entries.

    someone should just make a libcombatfixer :)

    i tried to get shefki to add it to blizzbugssuck but he said combat log breaking isn't the type of UI bugs they are targeting, doh.

    Last edited Jul 08, 2010 by mysticalos
  • Avatar of kagaro kagaro Jul 08, 2010 at 18:47 UTC - 0 likes

    ive seen some people how make a frame that every second calls the CombatLogReset function

  • Avatar of mysticalos mysticalos Jul 08, 2010 at 18:39 UTC - 0 likes

    I'm taking it you've noticed that halion breaks the combat log even more than heroic lich king huh? I dont know what it is about halion but in a given pull i usually lose combat log 3-4 times. Very frustrating. I actually spent an entire pull with no combat log once. the funny thing is i still got EVERY boss warning and timer cause of the amount of syncing I use heh. I'll probably have to extend combatlog fix beyond just pull as well. it's a shame blizz makes us work around their dumb bugs like this though.

  • Avatar of rantank rantank Jul 08, 2010 at 11:34 UTC - 0 likes

    I have seen these lockups in normal 10 and 25. I rolled back RaidWatch2 for heroic 25. If there were problems previously with AVR then maybe the culprit for conflict now is HudMap.

  • Avatar of kagaro kagaro Jul 08, 2010 at 11:29 UTC - 0 likes

    @cana: fixed


Date created
Nov 12, 2009
Last update
Oct 19, 2014
Development stage
  • deDE
  • enUS
  • frFR
  • koKR
  • ruRU
  • zhCN
  • zhTW
All Rights Reserved
Curse link
RaidWatch 2
Reverse relationships
Recent files