• World of Warcraft Addons
  • World of Warcraft
  • Average Rating:

  • Your Rating

  • Share
  • Report Abuse

Obituary

 
Project Updated:
Files Updated: Sun, Aug 16 2009
Supports Game Version: 3.2.0
Category: Combat
Tags:

, , , , and [Edit Tags]

Project Manager: GraemeF
Additional Authors: No additional authors
Current Version: 0.4.1
License: GNU General Public License version 3 (GPLv3)
Development Site: CurseForge
Avg Daily DL (last 30 days): 11
Downloads Total: 14,808
Favorites: 36
Comments: 21
  • About Obituary
  •  

What it does

Obituary announces deaths, whodunnit, and how.

By default it will only report deaths of players in your raid or party, but can optionally report on mob deaths too.

  • Player names are displayed in the correct colour for their class, and the damage done by the killing blow is also reported.
  • If available, a link to the spell/skill that dealt the killing blow is displayed.
  • Reports can be sent to your chat window (default), a channel of your choosing, or other addons such as MSBT.

It was inspired by Al'ar's flame patches, but has provided much in the way of entertainment and education since then. :)

Options

By default, Obituary will tell you when a party or raid member dies, what killed them, and how hard. You can change this behaviour in the Obituary page in the AddOns tab of your Interface Settings window.

  • You can switch it off by clearing the Enable check box.
  • You can enable/disable display of mob deaths with the Mobs check box.
  • You can choose a different output method by selecting one from the list.
  • If your chosen output method (e.g. a channel such as Raid or Say) doesn't support spell links you can switch them off by clearing the "Spell Links" check box.

Slash commands

/obit enable
Enables/disables the messages.
/obit mobs
Enables/disables display of mob deaths.
/obit links
Enables/disables display of spell links (to avoid errors when outputting to a channel that doesn't allow them).

You may also use /obituary for slash commands.


  • Downloads (5)
  •  
File Name Release Type Game Version Downloads Date
Addon Curse.com Beta 2.3.3 0 9/29/2008
  File Name Release Type Game Version Downloads Date  
  Obituary 0.4.1 Release 3.2.0 5,428 8/16/2009
  Obituary 0.4.0 Release 3.1.0 3,262 5/10/2009
  Obituary 0.3.5 Release 3.1.0 124 5/10/2009
  Obituary 0.3.4 Release 3.1.0 176 5/9/2009
  Obituary 0.3.3 Release 3.0.2 4,267 10/26/2008
  • 1 page(s)
  • Comments

Add Comment  

Add

You need to login or register to post.

Benefits of Registration

  • Interact with hundreds of thousands of other gamers on an open social network.
  • Post your stories, news, images, videos, and other content to share.
  • Create a network with your fellow gamers or join an existing one.
  • Gain reputation for everything you do.
  • cohu said

    Seems like the one on WoWInterface is a completely different AddOn.

    Reply Report Permalink
  • Malific said

    I'm a little confused here about getting the latest version.

    Curse.com: Version 0.4.1 last update 8/16/2009
    WoWInterface.com: Version 1.0.3 last update 7/01/2009

    Reply Report Permalink
  • Anyone got a fix for the SendChatMessage(): Invalid escape code in chat message: error in the current version? the previous fix in this thread doesnt work.

    Reply Report Permalink
  • GraemeF said

    You can fix this by disabling the spell links option, either with the check box in the options or with the "/obit links" command.

    Reply Report Permalink
  • Cruciatum said

    Only thing keeping me from using this addon is that, currently, there seems to be no way to report things to custom channels. I have a channel set up, which reports player deaths from another addon (Obituary reports things a lot better though) and I'd like to keep it this way to avoid spamming the raid channel and avoid showing people this info when they don't want to see it.

    Any chance of an update to allow reporting to 1-10 channels?

    Reply Report Permalink
  • valjean2 said

    Right now, Obituary reports priests with Spirit of Redemption as having died twice. Is there a way to correct that?

    Reply Report Permalink
  • GraemeF said

    Can you open a ticket and I'll take a look. Thanks.

    Reply Report Permalink
  • Aisenfaire said

    There's a similar addon called Fatality: http://wow.curse.com/downloads/wow-addons/details/fatality.aspx

    Maybe you guys could.. I dunno.. combine forces or something.

    Reply Report Permalink
  • Tiwack said

    Am still waiting for the update and fix for making announcing in raidchat working :D

    Been checking every couple of days for a couple of weeks... Any ETA when to see it fixed? Still i can't be without this. Pure awesomeness to me

    Thx once more^^

    Reply Report Permalink
  • GraemeF said

    Version 0.4.1 adds a Spell Links option - switching this off will stop the errors when you output to a channel that doesn't accept links.

    Reply Report Permalink
  • Rogakk said

    Really enjoying the addon, would it be possible to allow for multiple reportings? Instead of JUST chat, or JUST MSBT, do both? Or more?

    Reply Report Permalink
  • GraemeF said

    Hey thanks for all the great feedback! :D

    I'm still not playing much but was expecting an email notification when people added comments here, so it was a bit of a surprise when I returned... Anyway, I would suggest using something like Acheron for more detailed death reports:

    http://wow.curse.com/downloads/wow-addons/details/acheron.aspx

    It does a lot more than Obituary, which I would like to keep fairly lightweight. Of course you can do what you like with the code and if you want to make modifications I would suggest making a clone as described here:

    http://kb.curseforge.com/projects/cloning/

    The chat channel problems are not really due to a bug in LibSink, rather Obituary shouldn't be trying to use colours and links in chat channels that don't allow them. I'll fix this at some point.

    Reply Report Permalink
  • Tiwack said

    When i set it to announce in raidchat it doesn't announce anything at all... i can only make the default chat announce and combined with bigwigs working.. Update plz :D
    This is great to see wtf how ppl died in boss fights and sudden deaths on trash rofl :P

    Also its kinda troublesome to go add the fix to show the 3 last hits to it... Maybe you should implement it yourself. getting hit for 15k and then being announced that he died to seal of martyr hit for 500dmg is no good... -.- http://premoguild.com/forums/showthread.php?t=3493 gogo plux

    Reply Report Permalink
  • duhwhat said

    This is a great modification, and it would nice to see how Graeme would implement it. We're not looking for MUCH more detail like Acheron provides, just two more hits.

    Reply Report Permalink
  • gspbeetle said

    - Interesting stuff, i think they have add 3 new variables at the header:

    + local LOG_LINES = 3;
    + local OptTot = "";
    + local OptVar = 1;

    - And a bunch of code after" was killed" (the lines with+ are the new codes, the one without+ are already there)

    + if OptVar == 1 then
    + OptTot = lastDamage.name.." was killed"
    + end
    if lastDamage.spellName then
    output = output.." by "..lastDamage.spellName
    end
    + if OptVar > 1 then
    + OptTot = OptTot.." then by +"..lastDamage.spellName.."("..lastDamage.amount..")"..damageType
    + else
    + OptTot = OptTot.." by +"..lastDamage.spellName.."("..lastDamage.amount..")"
    + end
    + end
    if lastDamage.sourceName then
    output = output.." from "..lastDamage.sourceName
    + OptTot = OptTot.." from
    +"..lastDamage.sourceName
    end
    -- print to the configured output
    self:Pour( format("%s (%d%s).", output, lastDamage.amount, damageType), 1.0, 1.0, 1.0)
    + if OptVar == 3 then
    + --self:Print(ICON_LIST[8].."0\124t")
    + self:Pour( +ICON_LIST[8].."0\124t"..OptTot, 1.0, 1.0, 1.0)
    end
    table.remove(damageTable, destGUID);
    end

    Reply Report Permalink
  • kohanai said

    I'd like to know the same as SaladFork. Have you found a way to show the last 3 hits on a character? I tried the 'modded' version that was linked, but got nothing. Any help would be greatly appreciated.

    Reply Report Permalink
  • Shahz said

    When it's set to report in the raid channel ->

    SendChatMessage(): Invalid escape code in chat message:
    : ?
    : in function `SendChatMessage'
    LibSink-2.0-90065 (Obituary):281: in function `func'
    LibSink-2.0-90065 (Obituary):371: in function <...ace\AddOns\Obituary\Libs\LibSink-2.0\LibSink-2.0.lua:357>
    LibSink-2.0-90065 (Obituary):377: in function `Pour'
    Obituary-0.4.0\Obituary.lua:265: in function `ReportDeath'
    Obituary-0.4.0\Obituary.lua:149: in function `?'
    CallbackHandler-1.0-3 (Ace3):146: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
    :"safecall Dispatcher[9]":4: in function <[string "safecall Dispatcher[9]"]:4>
    : ?
    :"safecall Dispatcher[9]":13: in function `?'
    CallbackHandler-1.0-3 (Ace3):91: in function `Fire'
    AceEvent-3.0-3 (Ace3):73: in function

    Reply Report Permalink
  • Phaye said

    Open up "LibSink-2.0.lua" in the Obituary\libs\LibSink-2.0 folder.

    Find this line (should be around line 280)
    text = text:gsub("(|c%x%x%x%x%x%x%x%x)", ""):gsub("(|r)", "")

    Add this line directly below it
    text = text:gsub("|Hspell:%x%x%x%x%x|h", ""):gsub("|h", "")

    The Invalid escape code error should now go away, however, spells will no longer be linked in Raid/Party/Guild chat. Not an optimal solution, but a decent hack & slash until the Lib is updated. It will remain linking spells in all other channels however.

    Reply Report Permalink
  • Shahz said

    Thanks, that fixed the majority of the errors, however some still remain ->

    SendChatMessage(): Invalid escape code in chat message:
    : ?
    : in function `SendChatMessage'
    LibSink-2.0-90065 (Obituary):282: in function `func'
    LibSink-2.0-90065 (Obituary):372: in function <...ace\AddOns\Obituary\Libs\LibSink-2.0\LibSink-2.0.lua:358>
    LibSink-2.0-90065 (Obituary):378: in function `Pour'
    Obituary-0.4.0\Obituary.lua:265: in function `ReportDeath'
    Obituary-0.4.0\Obituary.lua:149: in function `?'
    CallbackHandler-1.0-3 (Ace3):146: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
    :"safecall Dispatcher[9]":4: in function <[string "safecall Dispatcher[9]"]:4>
    : ?
    :"safecall Dispatcher[9]":13: in function `?'
    CallbackHandler-1.0-3 (Ace3):91: in function `Fire'
    AceEvent-3.0-3 (Ace3):73: in function

    Reply Report Permalink
  • Phaye said

    Ran into that tonight and isolated that it's the raid symbols causing the errors as our previous code ripped out the "|h" terminators for the string.

    To combat this, and rather that continuing to mess with the library, i just disabled the raid symbols. Again a "hack and slash" approach but none the less here's a quick fix:

    Open "Obituary.lua" and look for this line:
    return "|Hicon:"..path..":dest|h|TInterface\\TargetingFrame\\UI-RaidTargetingIcon_"..targetNumber..".blp:0|t|h"

    replace it with:
    return ""

    Now it'll return nothing when it attempts to append a raid symbol. Tada your invalid chat escape codes should be resolved, though you'll no longer have raid symbols in the output as well.

    This error is a direct result of our previous "hack and slash" change to the Sink Library and not the author's fault.

    Reply Report Permalink
  • Addon Packs Containing Obituary
  • Similar Addons
  •  

Average downloads per day

  1. 23,777 Deadly Boss Mods Boss Encounters, and Combat
  2. 6,026 Recount Combat
  3. 5,653 BigWigs Bossmods Boss Encounters, and Combat
  4. 3,360 Omen Threat Meter Boss Encounters, and Combat
  5. 2,796 MikScrollingBattleText Combat, and PvP