Fatality

If you like this addon, I recommend checking out my other raid announce addon, Flump.

What is Fatality?
Fatality is a simple death report addon which announces information about the last hit(s) a person took before they died.

What makes it better than other, similar addons?
It's extremely lightweight and consumes much less CPU and memory than other addons which falsely claim to be better. If you're concerned about your FPS and general performance while raiding and want a simple addon to accurately report deaths without any extra junk or bloat, look no further.

Can I choose where the informaton is announced?
Yes. You can select where reports are sent depending on whether you are in a Raid or Party instance. You can choose to send reports to the following outputs:

Instance Instance chat - party/raid/instance, depending on your group.Self Just you - no one else will see these announcements.Guild Guild chat - you must be in a guild.Officer Officer chat - you must be an officer in a guild.Party Party chat - you must be in a party with at least one other person.Raid Raid chat - you must be in a raid with at least one other person.Raid Warning Raid warning - you must be promoted to Raid Leader/Raid Assistant.Channel A private channel, e.g. FatalityReports.Whisper A specific player, e.g. Moop.

Why can't I see any announcements?
By default, announcements will only be sent while inside Raid/Party instances.

What information is included in the reports?
The information included in reports can be configured. The following options are available and can be toggled according to user preference:

Absorbs The amount of damage absorbed; reported as (A: <absorb amount>)Blocks The amount of damage blocked; reported as (B: <block amount>)Resists The amount of damage resisted; reported as (R: <resist amount>)Overkill The amount of excess damage, e.g. if a person has 20000 remaining hitpoints and takes 50000 damage, their overkill would be 30000; reported as (O: <overkill amount>)School The school of damage the spell belongs to (Fire, Shadow, Physical, etc.)Source The unit who caused the damage eventIcons The raid icons displayed above a player's head

How are Cauterize and Spirit of Redemption "deaths" handled?
• Cauterize does not guarantee death and an announcement is therefore not sent when it procs (unless the Mage actually dies).
• Spirit of Redemption does guarantee death and is reported with an asterisk (*) next to the Priest's name as an indication of their current state.

How are deaths with known/unknown causes handled?
Due to limitations (bugs) within Blizzard's Combat Log, it is sometimes impossible for any addon to conclusively determine how a player died. As a general solution to this problem, Fatality assumes that any damaging hit taken at least 2 seconds before a player died is the cause of their death. Here are some examples of cases where death reports may vary because of these limitations:

UnknownSituation: No damage is recorded within the 2-second timeframe. This usually occurs when either (1) The person running Fatality is in another realm and data cannot be recorded (Ultraxion) or (2) A person falls off a platform and there is no recent damage events that can be linked to their death (Warmaster/Spine/Madness).Output: Fatality: Moop > [Death]

Known/UnknownSituation: Damage is recorded within the 2-second timeframe, but no overkill is reported by the combat log.Output: Fatality: Moop > ~45.4k Melee [Warmaster Blackhorn]

KnownSituation: Damage is recorded within the 2-second timeframe, but this time the combat log does report an overkill.Output: Fatality: Moop > 45.4k Melee (O: 123.4k) [Warmaster Blackhorn]

How do I enable/disable the addon?
Click the small green/red button at the top left of the configuration UI or type /fat on|off.

How are character-specific settings handled?
Configuration settings are saved separately for each character. However, the enabled/disabled status of the addon remains the same for all characters, i.e. if you click the green/red button to turn the addon on/off, it will also affect your other characters' settings.

Fatality still announces when there are other people in my group with it installed. Can you do something about this?
I'm afraid not; Fatality was designed to be an extremely lightweight solution for death reports. In order to implement a "smart disable" option, it would be necessary to make use of the Blizzard AddOn communication channel which can lead to a negative impact on your game's performance and, since I value my FPS, client-to-client communication is currently not something I want to include in any of my addons.

v2.1a | moop | Friday, 24th February, 2012
- Priest: Report Spirit of Redemption deaths with an asterisk (*) next to the player's name.
- Increase the amount of time for deaths to be displayed as Fatality: Player > [Death] from 1 second to 2 seconds in an effort to reduce erroneous reports.
- Added /fat on and /fat off commands as a convenient way to enable/disable the addon without having to open up the configuration UI.
- Localisation updates - ptBR/ruRU/zhCN.

v2.0 | moop | Sunday, 15th January, 2012
- Fatality now has a brand new user interface! To access it, type /fatality or /fat.
- Added localisation support for German (deDE), French (frFR) and Spanish (esES/esMX) - other locales (koKR/ptBR/ruRU/zhCN/zhTW) will be included in future updates. Visit http://goo.gl/STSrx if you can help out with translations.
- Improved Unknown death detection. For example, when a player jumps off the boat at Warmaster Blackhorn or from Deathwing's back on the Spine encounter, their death now should correctly be reported as Unknown.
- Spirit of Redemption deaths should now be fixed once and for all.
- Added several new options:

v1.2.4 | moop | Tuesday, 29th November, 2011
- Saved variables are now stored per character, which means you'll have to reconfigure your settings on each character you have Fatality enabled on.
- Fix DAMAGE_SHIELD and DAMAGE_SPLIT events. Damage events like Thorns and Hand of Sacrifice should now be recorded.
- Added an option to announce spell schools. This is enabled by default, type /fat school to disable.
- Added better detection for Spirit of Redemption deaths.
- Bump TOC to 40300.

v1.2.0 | moop | Tuesday, 8th February, 2011
- Fatality is now fully configurable in-game! Type /fatality list for more information. Note that, from now on, you will not need to edit Fatality.lua to set the addon up - it's all done in-game, meaning that settings will be saved between updates and you'll only ever need to set it up once. Please report any bugs you may experience!
- Added an option to set different numbers of reports for 10-man and 25-man raids. By default, 10-man is set to 5 and 25-man is set to 10.
- Added an option to set a minimum threshold for recorded damage. By default, this is set to 0, i.e. all damage will be recorded.

v1.1.8a | moop | Monday, 13th December, 2010
- Added an option for reporting to custom channels inside Party instances.
- While in random dungeons, players from other realms will now be reported as "Player" instead of "Player-Realm" since the realm isn't really relevant information.

v1.1.7 | moop | Sunday, 12th December, 2010
- Added an option for reporting inside Party instances as well as Raid instances. This is enabled by default, set PARTY_REPORTS to false to disable.

v1.1.6 | moop | Monday, 8th November, 2010
- Revert back to using UNIT_HEALTH combined with Overkill to hopefully fix some of the erroneous reports; this technique is only used in instances with other phases, i.e. Sartharion/Halion.

v1.1.3 | moop | Sunday, 22nd August, 2010
- Refactored a lot of the code to (hopefully) be more efficient.
- Added an option for short numbers, i.e. 9431 = 9.4k. This is enabled by default, set SHORT_NUMBERS to false to disable.
- Potential fix for reporting deaths as Unknown on "other phase" fights, i.e. Sartharion/Halion. Please report any issues.
- Added an option to report to self. Set OUTPUT to "SELF" to enable.
- Added an option to report multiple damaging events. This is set to 1 by default, increase EVENT_HISTORY as you wish. Note: Increasing this number beyond 3 will likely result in messages failing to be sent because they exceed the 255 character limit. If OUTPUT is set to "SELF", there is no limit to the number of characters that can be printed.

v1.1.2 | moop | Thursday, 10th December, 2009
- Added an option to include raid icons. This is enabled by default, set RAID_ICONS to false to disable. This feature is particularly useful for Penetrating Cold deaths in Phase 3 of the Anub'arak encounter.
- Changed the default number of reported players to 10.
- Bump TOC.

v1.1.1 | moop | Tuesday, 6th August, 2009
- Added an option to include Overkill. This is enabled by default, set OVERKILL to false to disable.
- Bump TOC.

v1.1.0 | moop | Saturday, 11th July, 2009
- Increase the time check between the last damage event and the time when UNIT_DIED fires from 0.5 to 2 seconds (before reporting the source of a player's death as Unknown). I've tested this locally over the last few days, and it seems to be working perfectly, please report any issues you may experience.

v1.0.6 | moop | Saturday, 13th June, 2009
- Now records every hit players take and outputs the very last one before they died, regardless of whether there was overkill or not. This should eliminate the rare cases where a player dies from exactly as much damage as their remaining hit points.
- Check for SPELL_INSTAKILL. Tank deaths from Meltdown on Iron Council hardmode should now be reported correctly, as well as Paladins who died from Divine Intervention.
- Check if a player is feigning death before reporting them as dead.
- Changed the default number of reported players to 5.

v1.0.5 | moop | Sunday, 7th June, 2009
- Added the option to report to custom channels.
- Reset the counter when we enter an instance, as well as when we enter combat.

Is there any option for just after-combat report of fails?
Because in real-time raid is little bit spam.. =) report after-combat is good for minus DKP etc.. i just want to know if there is any option for activate that..

Originally posted by creepy_inc Yeah the need to change settings only came after the update not long ago.

Would you mind pasting me the first 8 lines from Fatality.lua? It could be something specific to the settings you're using. Also, you mentioned you modified the code at some point, if you could include that, too, it'd be helpful in narrowing down the issue.

[edit] If the problem is only occurring with custom channels, then I'm pretty sure I've figured out why. I'd still like to see your settings to confirm, though.

Originally posted by oomp I'm not sure if this bug is specific to Fatality - there's a known bug with the combat log which causes it to randomly(?) break and cease to report any events. Do you notice other addons which rely on the combat log not working at the same time Fatality isn't working? I'll double-check the code either way to make sure I haven't missed something obvious.

If you update any of the Lua settings, a UI /reload is required in order for those settings to update, it's one of the disadvantages of not having an in-game configuration, though Fatality's settings shouldn't need to be changed often - I, for example, have been using the same settings for around 6 months without needing to change them.

Yeah the need to change settings only came after the update not long ago. I noticed today, running ICC 25 on my druid it wouldn't report, I didn't notice at first since very few died. a reload fixed it though. Maybe I have some mod that disable it somehow? I have "Peace and Quiet" installed, it disables general chat in instances. This is a custom channel though. Again I'll try and keep an eye on it, sorry if it has nothing to do with your mod. Just never noticed any problems before this update.

Originally posted by creepy_inc Something I have noticed though is that if you crash, or maybe even mess with other addons I have to reload the UI or log out for Fatality to start reporting again, never had that problem with the previous version. Also took me a few changes in the LUA until it started working properly for me, maybe I type something wrong who knows.

I'm not sure if this bug is specific to Fatality - there's a known bug with the combat log which causes it to randomly(?) break and cease to report any events. Do you notice other addons which rely on the combat log not working at the same time Fatality isn't working? I'll double-check the code either way to make sure I haven't missed something obvious.

Originally posted by creepy_inc It worked perfectly for reporting to the default "Raid" but took a while before I got it to work with a custom channel.

If you update any of the Lua settings, a UI /reload is required in order for those settings to update, it's one of the disadvantages of not having an in-game configuration, though Fatality's settings shouldn't need to be changed often - I, for example, have been using the same settings for around 6 months without needing to change them.

Well for the death not showing up at all I guess I only notice once or twice and yes it was only at Halion, can't really tell you much more. Sorry I know it's vague, I'll pay attention in the future.

As for the "Unknown" I kinda guessed that was the problem, same reason Numeration ( recount style meter ) doesn't really work there either. It doesn't have a sync option either.

Something I have noticed though is that if you crash, or maybe even mess with other addons I have to reload the UI or log out for Fatality to start reporting again, never had that problem with the previous version. Also took me a few changes in the LUA until it started working properly for me, maybe I type something wrong who knows. It worked perfectly for reporting to the default "Raid" but took a while before I got it to work with a custom channel.

I love your addon though and with the custom channel and spam out of the raid this is a really great tool. Thanks for updating!

EDIT: Tough to describe the actual bugs so for now I will just assume it was me doing something wrong and pay close attention in the future.

Originally posted by creepy_inc I still get "unknown" when I'm in the fire realm and someone dies in the shadow realm.

This is actually something that, without syncing between two clients (one in the shadow realm, one in the fire realm - something I won't be implementing at any time in the future), simply isn't possible due to the limited range of the combat log - these kinds of deaths will always be reported as Unknown. The fix mentioned in the changelog was for when the person running the addon is in the shadow realm, and a player dies inside; previously, Fatality wouldn't catch the death and instead, once the logger exited, spam all the deaths at once and report them as Unknown.

Originally posted by creepy_inc Also it's not catching all deaths for some reason.

Could you elaborate on this? Is it just in Ruby Sanctum you're experiencing this issue, or in other instances, too? I, personally, was testing in Ruby Sanctum for around a month before I released v1.1.3 and only experienced this once or twice, and couldn't work out a solution - perhaps, with some more information, I'll be able to figure out why it's occurring.

Just so you know, someone in Paragon's world first kill of Arthas 25HM was using your addon, which is actually what made me look this up since this is such an awesome concept that I dont have to ever dig through Acheron reports for death notifications :P Keep up the good work!

I'm currently on a break from World of Warcraft, but when I'm back, I'll be working on updating Fatality with some of your requests. For the time being, I've had some requests to translate the few English words used by the addon into other languages, so, if you think you can help, visit http://wow.curseforge.com/addons/fatality/localization/

Support AddOn Development!

You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.