Help

Fatality

Boss Encounters Login to Add Favorites
  • 4 Likes
  • Project Manager: oomp
  • World of Warcraft
  • 113,421 Downloads
  • Supports: 4.3
  • 101 Average Daily Downloads
  • Comments
  • Created 5/25/2009 5:46:34 PM
  • Updated 2/2/2012 4:50:53 PM
  • 251 Favorites
  • Project Site
  • License: All Rights Reserved
  • Release Type: Release
  • Newest File: v2.1
or
Support development! **
Donate

About Fatality

* The latest version of Fatality (v2.0+) has a full configuration UI. If you're using an older version, update now! *

  • If you like this addon, I recommend checking out my other raid announce addon, Flump.
  • If you want this addon in your language, visit the localisation page [Updated 27th January 2012] to see if you can help!

Fatality is a simple addon which announces information to a specified channel about the last hit a person took before they died. Below is an example of what would be reported after a player (Moop) took 24,534 melee damage from The Lich King, resulting in death:

Fatality: Moop > 24.5k Melee [The Lich King]

Configuration includes; the number of people reported, the number of events in each report, whether numbers should be shortened, the minimum amount of damage to be recorded, whether raids icons should be shown, and more. Type /fatality list in-game for a more extensive list of options.

  • Configuration: /fatality or /fat

Only works inside Raid/Party instances.

http://i.imgur.com/LQqYf.png http://i.imgur.com/5EpMi.png http://i.imgur.com/3yBnS.png http://i.imgur.com/WuVKG.png http://i.imgur.com/jOTKE.png http://i.imgur.com/aBANO.png http://i.imgur.com/hEzHH.png http://i.imgur.com/XsoN5.png http://i.imgur.com/r4iLh.png http://i.imgur.com/wCt7D.png

v2.1 | moop | Thursday, 2nd February, 2012
- Lots of minor optimisations to the way data is stored.
- Several bug fixes related to Unknown deaths.
- Increased the default minimum amount of recorded damage from 0 to 5000.
- Added localisation support for Korean (koKR), Brazilian Portuguese (ptBR), Russian (ruRU), Simplified Chinese (zhCN) and Traditional Chinese (zhTW). Visit http://goo.gl/STSrx if you can help out with missing/inaccurate translations.
- Added a new option - Source: Include who caused the damage.
- Hunter: Better Feign Death detection.
- Priest: Tweak Spirit of Redemption handling.
- Warlock: Implemented Life Tap damage recording.

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:

Quote:

• Promote: Only announce if promoted.
• LFR: Enable inside LFR.
• Raid: Enable inside Raid Instances.
• Resists: Include resisted damage in reports.
• Absorbs: Include absorbed damage in reports.
• Blocks: Include blocked damage in reports.
• Whispers: Send announcements via whisper.

- Fix a minor bug introduced in v1.2.6 where if the user entered an instance with Fatality disabled, then enabled it, it wouldn't register correctly.

• • • As always, if you experience any problems or have any suggestions, leave a comment! • • •

v1.2.6 | moop | Tuesday, 3rd January, 2012
- Fatality's enabled/disabled option is now stored globally, meaning that if it's changed on one character, it'll be changed for all characters. Other settings remain character-specific.

v1.2.5 | moop | Wednesday, 30th November, 2011
- Report players as "Player" instead of "Player-Realm" inside Raid instances.

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.3 | moop | Wednesday, 29th June, 2011
- Updated COMBAT_LOG_EVENT_UNFILTERED arguments for 4.2.
- Removed old code which made use of UNIT_HEALTH to determine deaths.
- Bump TOC to 40200.

v1.2.2 | moop | Wednesday, 27th April, 2011
- Updated COMBAT_LOG_EVENT_UNFILTERED arguments for 4.1.
- Fix SPELL_INSTAKILL announcements.
- Bump TOC to 40100.

v1.2.1c | moop | Friday, 18th February, 2011
- Fix invalid "Report cannot be sent because it exceeds the maximum character limit of 255." errors.

v1.2.1b | moop | Friday, 18th February, 2011
- Fix /fat history command.
- Accept "SELF" as a channel regardless of the case when setting the output.

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.8b | moop | Sunday, 26th December, 2010
- Fix reporting players as "Player" instead of "Player-Realm" inside Party instances.

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.7a | moop | Sunday, 12th December, 2010
- Make sure to re-check instance type when Fatality has been enabled/disabled while already inside an instance.

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.5 | moop | Sunday, 16th October, 2010
- Use Blizzard's new and improved Overkill argument to determine deaths.
- Remove old UNIT_HEALTH death-detection code.
- Bump TOC to 40000.

v1.1.4 | moop | Thursday, 2nd September, 2010
- Fix reporting to custom channels sometimes not working.

v1.1.3 | moop | Sunday, 22nd August, 2010
- Refactored a lot of the code to (hopefully) be more efficient.
- Potential fix for reporting deaths as Unknown on "other phase" fights, i.e. Sartharion/Halion. Please report any issues.
- Added an option for short numbers, i.e. 9431 = 9.4k. This is enabled by default, set SHORT_NUMBERS to false to disable.
- 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.9a | moop | Tuesday, 7th July, 2009
- Attempt to fix reporting Spirit of Redemption deaths twice.
- Switch to using a player's GUID as a table key instead of their name.

v1.0.9 | moop | Monday, 6th July, 2009
- Report the source as "Unknown" when there is no combat log event for a player's death.

v1.0.8 | moop | Wednesday, 24th June, 2009
- Possible fix for erroneous reporting when there is no combat log event for a player's death, for example, falling off the tram on the way to Mimiron.

v1.0.7 | moop | Friday, 19th June, 2009
- Check for ENVIRONMENTAL_DAMAGE, i.e. deaths from Falling, Drowning, Fatigue, etc.

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.

v1.0.4a | moop | Monday, 1st June, 2009
- Bump TOC.

v1.0.4 | moop | Monday, 1st June, 2009
- Added a slash command to enable/disable the addon: Type /fatality or /fat in-game. This setting persists between sessions. (default: enabled)
- Not sure why I thought criticals/crushings could be either 0 or 1, updated code to reflect values of nil or 1.

v1.0.3 | moop | Sunday, 31st May, 2009
- Bump TOC.
- Add default values to comments.
- Now only checks if we're inside an instance when required.
- Set default delay between announcements to 0 seconds instead of 1 second.

v1.0.2 | moop | Friday, 29th May, 2009
- Added the ability to toggle/format timestamps. Check lines 4 and 5.

v1.0.1 | moop | Monday, 25th May, 2009
- Initial release.

v1.0.1 | moop | Monday, 25th May, 2009
- Initial release.

Comments

First Previous Page 1 of 8 Next Last
  • #106

    There used to be a /fat off command. Is there a substitue slash command to turn it off, or do I need to uncheck the box?

  • #107

    There are currently no other slash commands than /fat, which brings up the configuration UI; you can then toggle the addon on/off by clicking the small green/red button at the top left of the frame.

    For the sake of convenience, I'll re-add both the /fat on and /fat off commands in the next update.

  • #101
    Deaths not recording properly

    i updated fatality yesterday (feb 5) but during my raid it wasnt recording deaths properly. It would record most deaths as  "Alexavis > [death]" and when mousing over death as if it was a spell it would only say " Death - instant" . Is there some reason this is happening? Until then i'm going back to the previous version.

  • #102

    Firstly, thanks for the bug report!

    Secondly, I must say, it seems very strange to me. I've been testing the latest version myself for several weeks and haven't experienced the problem you're describing. If you could answer the following questions, it might help me to understand why this is happening for you:


    1) What party/raid instance were you in? (10-man/25-man)
    2) What boss did the problem occur on?
    3) What was the real cause of death for people who died?
    4) Do you have a /combatlog or link to a World of Logs report from the raid in question?
    5) What's your average latency in-game?
    6) Could you type /fatality and link me a screenshot of the settings you're using?

    Thanks again!

  • #105

    Thanks for the clarifications. If you'd like to upload your log somewhere so I can double-check it, be sure to compress it first (zip/rar), otherwise, as you said, the file size will be huge - compression drastically reduces their size.

    From what I can see, this behaviour is actually intended. I will update the description page of Fatality to clarify why deaths are being reported like this, but I'll explain it here so you can confirm it in future...

    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 1 second 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:

    [Unknown]
    Situation: No damage is recorded within the 1-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/Unknown]
    Situation: Damage is recorded within the 1-second timeframe, but no overkill is reported by the combat log. 
    Output: Fatality: Moop > ~45.4k Melee [Warmaster Blackhorn]

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

    Last edited by oomp on 2/7/2012 6:19:12 PM
  • #103

    1) has happened to me in raid finder and in 10 man normal instances. havn't done a dungeon (was vp capped ^^;) so i'm not sure how it would have been there

    2) it varied but on alot of bosses. One example is when my guild was working on Maddness it would record deaths from impales and other damge but then we wiped once and the next attempt our pally healer acidentaly got impaled but fatality bugged and didnt say it.

    3) as above and then a few other reasons were aoe dmg the healers couldnt keep up or in raid finder just somthing stupid (if you know what some raid finder groups are like when not listening)

    4) no world of logs for my guild i did get a combat log but its too big for anywhere i tried to upload :/ )

    5) my latency is usually around 50ms/50ms on low graphics (my laptops a little old) but i hadly ever have framerate issues at 15fps (screenshots below say 3fps because 25 mans do lag me a little)

    6) yes i can ive been using these settings before i had this problem (link to screenshot of settings plus chat when fatality worked and then didnt work  plus another screen shot of bug plus the person that died and then said why they died in raid chat->  http://sta.sh/#/d1ho8toca9rj  http://sta.sh/#/d198v5w5loso  )

     

    Last edited by burgessa on 2/7/2012 3:58:13 PM
  • #97

    In previous versions, when the reason for someone's death couldn't be determined, it reported the death to the raid line as a death to "Unknown".  In the new 2.0 version, it just seems to ignore those deaths altogether and not say anything.  I think it was extremely useful to have every death announced and timestamped on the raid line, even if the reason couldn't be determined.  Could we have this added back, perhaps as an option?

  • #98

    BTW, an example of a death that didn't seem to be reported at all was when someone died to screwing up the jump inbetween platforms on Madness of Deathwing.

  • #100

    Great, thanks

     

  • #99

    This feature wasn't intentionally removed and is currently not working in v2.0 due to a minor bug.

    It's been fixed and will be functioning correctly in v2.1, which I'll be releasing in the near future.

  • #94

    I would love to have an output option for /say

  • #95

    While it's no problem to implement, I intentionally didn't include either /say or /yell in order to keep those channels clear, since they're generally places where people announce (via their boss mod) if they have some kind of harmful debuff, so people around them can notice it and react accordingly - if Fatality were to announce there, it'd just clog up the chat and get in the way of more relevant information.

    Feel free to give me some examples where it'd be useful and I might consider adding it, but when I initially decided to exclude those two channels, I couldn't think of a single place where it'd be useful to anyone.

  • #96

    You're right, it certainly isn't useful to anyone. But I like the spamming in LFR :D

    Nevermind though, I managed to get it working without any knowledge of lua.

    I didn't expect it to be as easy as adding     {SAY,"SAY"},      below local outputs = { in Fatality_Options.lua

     

  • #93

    I'll be releasing an update in the next few days which addresses a few minor bugs and includes support for the following locales:

    If you notice any inaccurate or missing translations, visit the localisation page, leave a comment here, or send me a private message and I'll make sure they're corrected.

    [update] v2.1 has now been uploaded and includes support for all locales.

    Last edited by oomp on 2/2/2012 4:55:41 PM
  • #92

    Thanks buddy for confi UI <3

  • To post a comment, please login or register a new account.
Learn how to disable ads
Learn how to disable ads
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster Addon Downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse.com Experience
  • Premium Curse Client
  • and many More Features
  • Learn More »