GrimReaper

This project has become inactive.

This project is inactive and its default file will likely not work with the most recent version of World of Warcraft. The author may have abandoned it, or it may have outlived its usefulness.

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 consise combatlog display.

Now ported to Ace3 and done away with the evil Ace2. The King is Dead, Long Live the King.

Using

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 quickview 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 once more 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 maintank.
  • 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.

Donations

PayPal: [email protected]

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

  • Avatar of Zeksie Zeksie Aug 18, 2009 at 14:18 UTC - 0 likes

    Well. This is not as bad as it used to be back in the old days of WoW. New incremental garbage collection reclaims garbage as it's needed all the time. But I'll have a look through it, see if something can be improved without much effort. But, it could be just that this is the running level of GrimReaper. It does have to store a historical health log of entire raid for the duration of your combat log (usually around 5 minutes worth).

    Last edited Aug 18, 2009 by Zeksie
  • Avatar of ExcaliburClan ExcaliburClan Jul 01, 2009 at 09:29 UTC - 0 likes

    The addon seems to accumulate memory over time that is not released back. Would it be possible to have the data no longer used to be released? I would suspect tables populated with combatlog data, but not releasing back data that is no longer shown in the tooltips.

    My computer is old and with only 1GB RAM, i should buy a new one but cant afford atm. With some hands on i can however run WoW well in raids, as long as the addons dont start to consume memory. 2 very usefull addons seems bad at this, GrimReaper and Recount - both suffering from the same tendency to allocate more and more memory that is never released back even after the data is no longer used.

    GrimReaper is such an excellent analysis tool for a healer that i really want it to work well, but the memory hog currently prevents me to use it on a permanent basis, or i have to do alot of handson activities to force the memory to be released.

  • Avatar of teencute teencute Feb 17, 2009 at 17:47 UTC - 0 likes

    GOOD GOOD

Facts

Date created
May 27, 2008
Category
Last update
Sep 11, 2013
Development stage
Inactive
Language
  • enUS
License
GNU General Public License version 2 (GPLv2)
Curse link
GrimReaper
Downloads
130,705
Recent files
  • A: r104 for 5.4.0 Sep 11, 2013
  • A: r103 for 5.2.0 Mar 06, 2013
  • A: r102 for 5.1.0 Mar 02, 2013
  • A: r101 for 5.1.0 Dec 30, 2012
  • A: r100 for 5.0.4 Sep 03, 2012

Authors