Grim Reaper

Grim Reaper

Your tank died? Why? That's the question really.

Grim Reaper gives you a very quick and easy access to the relevant combat log of any raid member with just a flick of the mouse or the press of a key. It will also monitor raid member health levels for the duration of combat log data and will show the health of any unit alongside their concise combat log display.


There are several ways to use Grim Reaper.

  • My personal favorite is to leave it hidden most of the time and use the hotkey activator. If you go into Blizzard key bindings and scroll down to Grim Reaper and setup a key for the Quick View function (I use F10), then whenever I need the reaper window I hold the quick view button, mouseover to who I'm interested in and release the quick view key. This locks the view onto that player and you can scroll around and do your investigating. When you're done with it, simply press the quick view key again and Grim Reaper hides itself once more.
  • Others will prefer to setup a keybind to lock the reaper on a target and leave it open all the time, perhaps watching their main tank.
  • Some people prefer to dock Grim Reaper onto the tooltip, but this offers reduced functionality as the display is non-interactive in this mode, but it does offer a quick and simple view.


PayPal: [email protected]

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

  • Avatar of ywfn ywfn Oct 29, 2010 at 01:27 UTC - 0 likes

    No minimap icon to toggle it on/off in the new version? Not showing up for me, anyway.

    Is it supposed to be LDB-only now?

    Last edited Oct 29, 2010 by ywfn
  • Avatar of mook mook Oct 28, 2010 at 00:25 UTC - 0 likes

    Ooh, what a handy AddOn! I love it, thanks for the work Zeksie.

    I do seem to be having a problem with the keybinding though. Clicking on the LDB feed toggles the display open and closed, but no matter what key I bind the 'Quick View' to in the keybindings, I can't get the window to toggle - wondering if anyone else is experiencing this, or if it's a conflict with another AddOn I'm using?


  • Avatar of Zeksie Zeksie Oct 27, 2010 at 15:38 UTC - 0 likes

    Ported to Ace3 now. Enjoy! :)

  • Avatar of Zeksie Zeksie Oct 25, 2010 at 17:06 UTC - 0 likes

    The current version seems to mostly work, so won't spend a lot of time adjusting that.

    Porting it to Ace3 atm so there'll be some worthwhile updates when that's done.

  • Avatar of milansch milansch Oct 23, 2010 at 18:55 UTC - 0 likes

    Still a brilliant addon! And still working for client 4.0.1 at least for me. I wish someone could continue development/maintenance... :)

  • Avatar of Fropper Fropper Oct 21, 2010 at 14:44 UTC - 0 likes

    Will there be an update for 4.0.x?

  • Avatar of Inny Inny Nov 18, 2009 at 16:15 UTC - 0 likes

    Was going to post some issues I was having, but I get most of my addons from Curse (w/ client updates), and haven't cleared my variables in forever; so I deleted all my GR variables and downloaded r83 from here (is that a newer version than on Curse)? And I'm already noticing it's showing for instance buff gains that it wasn't before, so maybe my issues don't apply anymore either.

    Regardless, great addon, love it. Cheers.

    Edit: Any way to scroll really fast through the log? (like page down, home/end) I know I can scale the window holding alt and scrolling while hovering over the frame, and just scrolling to scroll through the history, but pgdn/end combinations don't seem to work, unless I'm being silly. Thanks!

    Last edited Nov 18, 2009 by Inny
  • Avatar of Zeksie Zeksie Aug 28, 2009 at 10:06 UTC - 0 likes

    Even after a short fight, the combat log still contains the previous fights until some 5 minutes previously. The health storage has to go back to the start of the log. Which is why the usage is continuous over time.

    Nothing is kept that is not required. And anyhing discarded is re-used. It's that simple. And to be honest, 5-7mb is really not a lot for what it's doing.

    Last edited Aug 28, 2009 by Zeksie
  • Avatar of Daiyara Daiyara Aug 26, 2009 at 11:01 UTC - 0 likes


    do you have any link for your 'trashman' addon? I just use a simple file that tries to free the virtual memory when I click on it, but I need to minimize WoW to use it, so an addon would help a lot, specially with the high memory usage of Recount, GrimReaper and Decursive.

  • Avatar of ExcaliburClan ExcaliburClan Aug 24, 2009 at 11:09 UTC - 0 likes

    No its not as bad, but i think i should provide just abit more info so we are talking about the same thing.

    GrimReaper seems to allocate memory over time that is not put to the garbagecollection at all.

    In order to try to improve my comps poor performance, i discovered that garbage indeed do accumulate a little over time, and i tested if doing a full garbagecycle would improve things - it did. So i wrote an addon (Trashman) that every 15 seconds force a full garbagecycle, and this helped alot. some addons do creep alittle on garbage, those addons was stopped by this added garbage handling. I do find it odd that this indeed improves my performance, but i suspect the low memory forces virtual memory swaps to a lesser degree doing this... bad comp, ill fix that later.

    However GrimReaper seems to lock the memory- i checked the code and found what i think is some time-delete data code for 2 hours, setting down the time-limit to 15mins helped some but didnt fix the full problem, and it seemed to cause some other problems aswell.

    In raid i use up about 17-18mb addon memory. With my Trasman running it keeps pretty much in check over the course of a full raid. Using GrimReaper however starts off at some measly 0.1mb or something, and can grow as high as 7-8mb wich is not released in the course of the raid. This is the memory buildup i am referring to.

    Some memory buildup is necessary,as it shows logs from recent events for a multitude of players, i understand that, but seeing the tooltip show full data for every player after a short fight, and GrimReaper having allocated maybe 0.2-0.3mb more memory, it seems holding 7-8mb after a raid is excessive.


Date created
May 27, 2008
Last update
Mar 03, 2015
Development stage
  • enUS
GNU General Public License version 2 (GPLv2)
Curse link
Recent files