GrimReaper
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.
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 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.
Donations
PayPal: [email protected]
icon = "Interface\\Addons\\GrimReaper\\Images\\Death",
text = "GrimReaper"
})
function ldbobj:OnClick(button)
if button == "LeftButton" then
gr.db.profile.hide = not gr.db.profile.hide
gr.cycleState = nil
gr:Tip()
gr:DoIcon()
elseif button == "RightButton" then
gr:ShowMenu(self)
end
end
That should do the trick to have it atleast as ldb. Option to disable minimap-button is missing though.
But where can i fix the position of the whole thing.
After logoff / logon it always resets to the right down position.
Is there any manual somewhere?
GOOD GOOD
These days, however, grimreaper never seems to catch the final moments of my death, and is thus largely useless for me in performing the stuff I actually want to use it for: analyzing the reasons for why I died.
When checking grim reaper after a death, the last entries that should be there, detailing what killed me, are always missing :(
"Interface\AddOns\GrimReaper\GrimReaper.lua:1201: bad argument #5 to 'format' (string expected, got nil)"
tail = format("%s %s(%d %s)%s", tail, not report and "|cFFFFFF80" or "", a.resisted, " ", endColour)
to avoid errors. Do beware that this will most likely screw up the intended function of the line.
Sorry if i'm not allowed to do that but i love the addon and i want it error free until the next release of the mod is out :)
Zeksie, I've gotten a lot of lua errors lately, mostly in PvP, saying "...string expected, got nil". I will copy the exact error message next time I see it, but it is something to do with mob/player names/types I think. I can see within the GrimReaper pane, for example, "Shadowbolt" and "4250" but it doesn't show whose shadowbolt and the lua error occurs every time I hover over anything my own toons didn't cast.
thanks for this nice addon!
Sometimes I want to see what has happened but for example the person was survived and got an heal over time and your addon always jumps to the last entry.