Get an Epic Experience with Premium

Fatality

Boss Encounters Login to Add Favorites
  • 19 Likes
  • World of Warcraft
  • 13,318 Monthly Downloads
  • Supports: 6.0.2
  • 424,768 Total Downloads
  • Updated 10/23/2014
  • Created 05/25/2009
  • 346 Favorites
  • Project Site
  • Comments
  • Release Type: Inactive
  • License: All Rights Reserved
  • Newest File: v2.4c
or
Support development! **
Donate

About Fatality

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 event
Icons The raid icons displayed above a player's head

What other options are available?
Raid Enable inside Raid instances
Party Enable inside Party instances
LFR Enable inside the Raid Finder
Promote Only announce while promoted (Raid Leader/Raid Assistant)
Shorten Display shortened numbers, e.g. 9431 becomes 9.4k

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:

Unknown
Situation: 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/Unknown
Situation: 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]

Known
Situation: 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.

Which locales are supported and how can I help with translations?
http://i.imgur.com/5EpMi.png English (enUS)
http://i.imgur.com/jOTKE.png French (frFR)
http://i.imgur.com/LQqYf.png German (deDE)
http://i.imgur.com/3yBnS.png Spanish (esES)
http://i.imgur.com/WuVKG.png Latin American Spanish (esMX)
http://i.imgur.com/grCWx.png Italian (itIT)
http://i.imgur.com/XsoN5.png Russian (ruRU)
http://i.imgur.com/hEzHH.png Brazilian Portuguese (ptBR)
http://i.imgur.com/aBANO.png Korean (koKR)
http://i.imgur.com/r4iLh.png Simplified Chinese (zhCN)
http://i.imgur.com/wCt7D.png Traditional Chinese (zhTW)

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.

v2.4c | natal | Thursday, 23rd October, 2014
- Bump TOC to 60000.

v2.4b | moop | Saturday, 10th May, 2014
- Bump TOC to 50400.

v2.4a | moop | Saturday, 9th March, 2013
- Make sure only player deaths are reported.

v2.4 | moop | Friday, 8th March, 2013
- Removed Life Tap detection.
- Use GetInstanceInfo() instead of GetInstanceDifficulty().
- Bump TOC to 50200.

v2.3c | moop | Sunday, 6th January, 2013
- Make sure to update chat settings when a new output has been selected.

v2.3b | moop | Thursday, 13th December, 2012
- Hopefully fix the 'Instance' option...

v2.3a | moop | Thursday, 6nd December, 2012
- Made the 'Instance' option from the Output dropdown menu smarter. Thanks to Sintacks and rotes!

v2.3 | moop | Sunday, 2nd December, 2012
- Added support for Instance Chat. Thanks to Vandesdelca32!
- Bump TOC to 50100.

v2.2c | moop | Sunday, 4th November, 2012
- Fixed a bug which prevented environmental damage from being reported.

v2.2b | moop | Sunday, 9th September, 2012
- Fixed the 'Self' option from the Output dropdown menus.
- Added a check for UnitIsGroupLeader("player") in addition to UnitIsGroupAssistant("player"). Thanks to ywfn!
- Added localisation support for Italian (itIT). Thanks to Adam77!

v2.2 | moop | Saturday, 8th September, 2012
- Fixed a minor UI bug.
- Localisation updates - deDE/esES/esMX/frFR/ruRU.
- Replaced IsRaidOfficer() with UnitIsGroupAssistant("player"). Thanks to Dracula!
- Bump TOC to 50001.

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.1 | moop | Thursday, 2nd February, 2012
- Lots of minor optimisations to the way data is stored.
- Several bug fixes related to Unknown deaths.
- Unknown deaths are now reported as: Fatality: Player > [Death]
- 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.

Comments

First Previous Page 2 of 12 Next Last
  • #168

    Mirror Images still broken in 2.4, reports 3 deaths for the mage when the images die.  (Not sure if you tried to fix it?)  Added back in my code I mentioned below to fix it for me.

    Last edited by ywfn on 3/8/2013 9:52:27 PM
  • #169

    Sorry, missed that, fixed in v2.4a - please update!

  • #171
    Here's the entries for Mirror Images. Other pets that use the same name as the player are working similarly though. An example is the Highborne Soul Mirror.

    3/10 05:25:07.529  SPELL_SUMMON,0x04000000003F7173,"Stingray",0x10511,0x0,0xF130B88C0038BBDD,"Mirror Image",0xa28,0x0,88088,"Mirror Image",0x1
    3/10 05:25:07.529  SPELL_SUMMON,0x04000000003F7173,"Stingray",0x10511,0x0,0xF130B88C0038BBDE,"Mirror Image",0xa28,0x0,88086,"Mirror Image",0x1
    3/10 05:25:07.529  SPELL_SUMMON,0x04000000003F7173,"Stingray",0x10511,0x0,0xF130B88C0038BBDF,"Mirror Image",0xa28,0x0,88090,"Mirror Image",0x1
    3/10 05:25:07.529  SPELL_AURA_APPLIED,0x04000000003F7173,"Stingray",0x10511,0x0,0x04000000003F7173,"Stingray",0x10511,0x0,55342,"Mirror Image",0x40,0x04000000003F7173,450441,108,26786,0,300000,BUFF
    3/10 05:25:07.529  SPELL_CAST_SUCCESS,0x04000000003F7173,"Stingray",0x10511,0x0,0x0000000000000000,nil,0x80000000,0x80000000,55342,"Mirror Image",0x40,0x04000000003F7173,450441,108,26786,0,294000
    3/10 05:25:37.505  SPELL_AURA_REMOVED,0x04000000003F7173,"Stingray",0x511,0x0,0x04000000003F7173,"Stingray",0x511,0x0,55342,"Mirror Image",0x40,0x04000000003F7173,450441,108,26786,0,300000,BUFF
    3/10 05:25:38.155  UNIT_DIED,0x0000000000000000,nil,0x80000000,0x80000000,0xF130B88C0038BBDF,"Stingray",0x2111,0x0
    3/10 05:25:38.155  UNIT_DIED,0x0000000000000000,nil,0x80000000,0x80000000,0xF130B88C0038BBDE,"Stingray",0x2111,0x0
    3/10 05:25:38.155  UNIT_DIED,0x0000000000000000,nil,0x80000000,0x80000000,0xF130B88C0038BBDD,"Stingray",0x2111,0x0
    Last edited by ywfn on 3/10/2013 5:28:47 AM
  • #170

    If you could supply a WoWCombatLog.txt where this is occurring, I might be able to implement a slightly better fix, because, if I remember correctly, the reason I avoided checking flags in the first place was fights like Cho'gall/Nefarian etc. where players get mind controlled, they are considered NPCs and therefore won't be reported with the COMBATLOG_OBJECT_TYPE_PLAYER check -- this may no longer be the case in MoP, though.

  • #167

    I've released a new version (v2.4) which should address the issue people have been experiencing.

    Once it's approved by Curse, please update and let me know if the problem persists.

    Last edited by oomp on 3/8/2013 3:15:39 PM
  • #165

    As of the last patch, not working at all.

  • #164

    GetInstanceDifficulty() needs to be changed to the new GetInstanceInfo() for 5.2.

    Also as of 5.2, though, certain "pets" are being reported as player deaths.  For example, if a mage summons Mirror Images, then when they die, 3 deaths get reported for the mage.  Some other pets do similar stuff.

  • #166

    Not sure what changed with the pets in 5.2, but I added a COMBATLOG_OBJECT_TYPE_PLAYER check into the unfiltered combat log event function to avoid the problem.  If anyone out there wants to fix these two problems in your own copy until an update arrives:

    Around line 347, look for:

    local difficulty = GetInstanceDifficulty()

    And change it to these two lines:

    local _, _, difficulty = GetInstanceInfo()
    difficulty = difficulty + 1

    Around line 257, look for:

    if not (UnitInRaid(destName) or UnitInParty(destName)) then return end

    And insert this line before it:

    if bit.band(destFlags, COMBATLOG_OBJECT_TYPE_PLAYER) == 0 then return end
    Last edited by ywfn on 3/6/2013 3:49:30 PM
  • #163

    Posting here since the ticket system isn't used:

    Just join an instance, this function's been removed/deprecated/renamed

    Date: 2013-03-05 21:11:30
    ID: 2
    Error occured in: Global
    Count: 2
    Message: ..\AddOns\Fatality\Fatality.lua line 347:
    attempt to call global 'GetInstanceDifficulty' (a nil value)
    Debug:
    Fatality\Fatality.lua:347: CheckEnable()
    Fatality\Fatality.lua:360: ?()
    Fatality\Fatality.lua:31:
    Fatality\Fatality.lua:30
    Locals:
    self = <unnamed> {
    0 = <userdata>
    ADDON_LOADED = <function> defined @Interface\AddOns\Fatality\Fatality.lua:390
    SetCharacterTable = <function> defined @Interface\AddOns\Fatality\Fatality.lua:231
    PLAYER_ENTERING_WORLD = <function> defined @Interface\AddOns\Fatality\Fatality.lua:359
    FormatOutput = <function> defined @Interface\AddOns\Fatality\Fatality.lua:128
    UpdateOutputSettings = <function> defined @Interface\AddOns\Fatality\Fatality.lua:307
    UnregisterEvents = <function> defined @Interface\AddOns\Fatality\Fatality.lua:330
    ReportDeath = <function> defined @Interface\AddOns\Fatality\Fatality.lua:243
    RegisterEvents = <function> defined @Interface\AddOns\Fatality\Fatality.lua:323
    UpdateTime = <function> defined @Interface\AddOns\Fatality\Fatality.lua:239
    db = <table> {
    }
    PLAYER_REGEN_DISABLED = <function> defined @Interface\AddOns\Fatality\Fatality.lua:355
    CreateSlashCommands = <function> defined @Interface\AddOns\Fatality\Fatality.lua:367
    CheckEnable = <function> defined @Interface\AddOns\Fatality\Fatality.lua:336
    ZONE_CHANGED_NEW_AREA = <function> defined @Interface\AddOns\Fatality\Fatality.lua:363
    title = "Fatality"
    ClearData = <function> defined @Interface\AddOns\Fatality\Fatality.lua:299
    COMBAT_LOG_EVENT_UNFILTERED = <function> defined @Interface\AddOns\Fatality\Fatality.lua:255
    version = "2.3c"
    RecordDamage = <function> defined @Interface\AddOns\Fatality\Fatality.lua:191
    HandleSpiritDeath = <function> defined @Interface\AddOns\Fatality\Fatality.lua:116
    }
    (*temporary) = nil
    (*temporary) = "attempt to call global 'GetInstanceDifficulty' (a nil value)"
    instance = "party"
    limit = nil

    AddOns:
    LibVan32, vrelease_v1.6.6
    Swatter, v5.15.5383 (LikeableLyrebird)
    WowheadLooter, v50007
    DevPad, v5.0.0.1
    NPCScan, v5.0.0.5
    NPCScanOverlay, v5.0.0.3
    ACP, v3.4.1
    ActionBarSaver, v
    AdiBags, vv1.6.4
    AdiBagsOutfitter, vv1.3-1-g4579f0c
    Altoholic, v5.1.001
    AltoholicCharacters, v5.1.001
    AucAdvanced, v5.15.5383 (LikeableLyrebird)
    AucFilterBasic, v5.15.5383 (LikeableLyrebird)
    AucFilterOutlier, v5.15.5383.5381(5.15/embedded)
    AucMatchUndercut, v5.15.5383.5381(5.15/embedded)
    AucScanData, v5.15.5383 (LikeableLyrebird)
    AucStatHistogram, v5.15.5383 (LikeableLyrebird)
    AucStatiLevel, v5.15.5383 (LikeableLyrebird)
    AucStatPurchased, v5.15.5383 (LikeableLyrebird)
    AucStatSales, v5.15.5383.5381(5.15/embedded)
    AucStatSimple, v5.15.5383 (LikeableLyrebird)
    AucStatStdDev, v5.15.5383 (LikeableLyrebird)
    AucStatWOWEcon, v5.15.5383.5323(5.15/embedded)
    AucUtilAHWindowControl, v5.15.5383.5381(5.15/embedded)
    AucUtilAppraiser, v5.15.5383.5381(5.15/embedded)
    AucUtilAskPrice, v5.15.5383.5381(5.15/embedded)
    AucUtilAutoMagic, v5.15.5383.5381(5.15/embedded)
    AucUtilCompactUI, v5.15.5383.5381(5.15/embedded)
    AucUtilEasyBuyout, v5.15.5383.5381(5.15/embedded)
    AucUtilFixAH, v5.15.5383 (LikeableLyrebird)
    AucUtilItemSuggest, v5.15.5383.5381(5.15/embedded)
    AucUtilPriceLevel, v5.15.5383.5381(5.15/embedded)
    AucUtilScanButton, v5.15.5383.5320(5.15/embedded)
    AucUtilScanFinish, v5.15.5383.5381(5.15/embedded)
    AucUtilScanProgress, v5.15.5383.4979(5.15/embedded)
    AucUtilScanStart, v5.15.5383.5381(5.15/embedded)
    AucUtilSearchUI, v5.15.5383.5381(5.15/embedded)
    AucUtilSimpleAuction, v5.15.5383.5381(5.15/embedded)
    AucUtilVendMarkup, v5.15.5383.4828(5.15/embedded)
    Babylonian, v5.1.DEV.332(/embedded)
    BeanCounter, v5.15.5383 (LikeableLyrebird)
    Clique, vv50100-1.0.2
    CombatMusic, vrelease_v4.6.3
    CombatMusicMetrics, vnull
    Configator, v5.1.DEV.344(/embedded)
    DataStore, v5.1.001
    DataStoreAchievements, v5.1.001
    DataStoreAgenda, v5.1.001
    DataStoreAuctions, v5.1.001
    DataStoreCharacters, v5.1.001
    DataStoreContainers, v5.1.001
    DataStoreCrafts, v5.1.001
    DataStoreCurrencies, v5.1.001
    DataStoreInventory, v5.1.001
    DataStoreMails, v5.1.001
    DataStorePets, v5.1.001
    DataStoreQuests, v5.1.001
    DataStoreReputations, v5.1.001
    DataStoreSpells, v5.1.001
    DataStoreStats, v5.1.001
    DataStoreTalents, v5.1.001
    DBMCore, v
    DebugLib, v5.1.DEV.337(/embedded)
    ElvUI, v5.36
    ElvUIAddOnSkins, v1.16
    ElvUIChatTweaks, v5.86
    ElvUIChatTweaksExtra, v
    ElvUIChatTweaksSpam, v
    ElvUIConfig, v1.00
    ElvUIDTBars, v4.07
    ElvUILanguageCycleSkin, v1.0
    ElvUILocPlus, v1.76
    Enchantrix, v5.15.5383 (LikeableLyrebird)
    Fatality, v2.3c
    FlightMap, v5.1.0
    ForteCasting, v
    ForteClass, v
    ForteCooldown, v
    ForteCore, v1.980.8
    ForteHealthstone, v
    ForteSoulstone, v
    ForteSummon, v
    ForteTalent, v
    ForteTimer, v
    GAOnlineCheck, vrelease_v1.2.19
    GRSearch, vbeta_0.2.1
    GRUpdate, vrelease_v1.6.5
    GTFO, v4.22
    GuildTithe, vrelease_v2.5.5
    GupPet, v2.104
    Informant, v5.15.5383 (LikeableLyrebird)
    LanguageCycle, v5.0.4.a
    LibExtraTip, v5.12.DEV.342(/embedded)
    LibStub, v
    MikScrollingBattleText, v5.7.126
    MoveAnything, v13.4.0
    MyRolePlay, v5.2.0.101
    Omen, v3.1.8
    Outfitter, v5.8.2
    Postal, v3.5.1
    RangeDisplay, vv4.1.2
    Recount, v
    Reflux, v1.15
    ReforgeLite, v1.23
    SharedMedia, v3.0.5-184
    SilverDragon, vv3.0.3-2-gaae17e2
    Stubby, v5.15.5383 (LikeableLyrebird)
    TipHelper, v5.12.DEV.343(/embedded)
    TipTac, v13.02.19
    TipTacExtraTip, v1.0
    TipTacItemRef, v13.02.19
    TipTacTalents, v13.02.19
    TomTom, vv50100-1.0.2
    WeakAuras, v1.4.7.9
    WIM, vr369
    ZygorGuidesViewer, v4.0
    BlizRuntimeLib_enUS v5.2.0.50200 <us>
    (ck=e92)

     

    Last edited by Vandesdelca32 on 3/5/2013 9:31:58 PM

    -- Vandesdelca32
    -- Andaendis @ Wyrmrest Accord

  • #161

    I'm getting a sound upon login and at random moments. I'm not sure if it's this mod or another one, but it says "fatality!" in a voice similar to Alvin from The Chipmunks. If it is this mod, how can I disable that?

  • #162

    That's actually BugSack and it's associated library, not this addon, that sound you're hearing is the sound it plays when a Lua error happens

    -- Vandesdelca32
    -- Andaendis @ Wyrmrest Accord

  • #153

    My guild uses a  special channel for addon output during raids, could you add special channels to the output drop down?

  • #154

    There is a Channel option in the output dropdown menus already.

  • #151

    Getting this error with the latest release 2.3c

     

    2x Fatality\Fatality-2.3c.lua:138: attempt to index field "?" (a nil value)
    Fatality\Fatality-2.3c.lua:138: in function "FormatOutput"
    Fatality\Fatality-2.3c.lua:246: in function "ReportDeath"
    Fatality\Fatality-2.3c.lua:281: in function "?"
    Fatality\Fatality-2.3c.lua:31: in function <Fatality\Fatality.lua:30>

    Locals:
    self = <unnamed> {
     0 = <userdata>
     ADDON_LOADED = <func> @..\Fatality.lua:390
     SetCharacterTable = <func> @..\Fatality.lua:231
     PLAYER_ENTERING_WORLD = <func> @..\Fatality.lua:359
     FormatOutput = <func> @..\Fatality.lua:128
     UpdateOutputSettings = <func> @..\Fatality.lua:307
     UnregisterEvents = <func> @..\Fatality.lua:330
     ReportDeath = <func> @..\Fatality.lua:243
     RegisterEvents = <func> @..\Fatality.lua:323
     UpdateTime = <func> @..\Fatality.lua:239
     db = <table> {}
     PLAYER_REGEN_DISABLED = <func> @..\Fatality.lua:355
     CreateSlashCommands = <func> @..\Fatality.lua:367
     CheckEnable = <func> @..\Fatality.lua:336
     ZONE_CHANGED_NEW_AREA = <func> @..\Fatality.lua:363
     title = "Fatality"
     ClearData = <func> @..\Fatality.lua:299
     COMBAT_LOG_EVENT_UNFILTERED = <func> @..\Fatality.lua:255
     version = "2.3c"
     RecordDamage = <func> @..\Fatality.lua:191
     HandleSpiritDeath = <func> @..\Fatality.lua:116
    }
    guid = "0x0600000005888E65"
    name = "Miniissa-Ravenholdt"
    flags = 0
    c = <table> {
     flags = 0
     name = "Miniissa-Ravenholdt"
     time = 61043.426
     guid = "0x0600000005888E65"
    }
    count = 1
    limit = 10
    send = <func> @..\Fatality.lua:67
    wipe = <func> =[C]:-1

    ♪~ ( ) I My Sonos!

  • #155
    • Do you have a World of Logs report or a recorded WoWCombatLog.txt file I can take a look at?
    • Is it occurring on all deaths or was it an edge-case? If so, do you have any additional details to help me figure ouit what's going on? 

     

  • To post a comment, please login or register a new account.
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 experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Dying Light Wiki Game Giveaway