Category: Raid Mods
Addon Information
Download Latest Version.
To add favorites please register for a free account. If you already have one you need to login. How do I install this? (FAQ)
Author:
Version:
1.1.1
Date:
08-06-2009 06:52 PM
Size:
1.97 Kb
Downloads:
2,185
Favorites:
52
MD5:
Pictures
Click to enlarge
Fatality
Fatality is a very simple addon with almost no in-game configuration which announces information to a specified channel about the last hit a person took before they died.

The number of people reported is configurable, as is the delay between each report, and whether or not timestamps are displayed - just open up Fatality.lua and edit the first 7 lines to suit your needs.

Below is an example of what would be reported to raid chat (default) after a player (Moop) took 30,000 melee damage from Stormcaller Brundir, resulting in death:

Fatality: Moop > 30000 Melee > Stormcaller Brundir

Toggle on/off in-game: /fatality or /fat

Only works inside raid instances.

P.S. I wrote this to help familiarise myself with the WoW API and Lua in general, hope someone'll find it fun/useful.
  Change Log - Fatality
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.
  Archived Versions - Fatality
File Name
Version
Size
Author
Date
1.1.0
2kB
oomp
07-11-2009 04:53 PM
1.0.9a
2kB
oomp
07-06-2009 08:11 PM
1.0.9
2kB
oomp
07-06-2009 12:29 PM
1.0.8
2kB
oomp
06-24-2009 05:15 PM
1.0.7
2kB
oomp
06-19-2009 11:34 AM
1.0.6
2kB
oomp
06-12-2009 09:37 PM
1.0.5
2kB
oomp
06-07-2009 12:28 PM
1.0.4a
2kB
oomp
06-01-2009 11:22 AM
1.0.4
2kB
oomp
06-01-2009 10:45 AM
1.0.3
1kB
oomp
05-30-2009 07:58 PM
1.0.2
1kB
oomp
05-29-2009 02:04 PM
1.0.1
1kB
oomp
05-25-2009 06:42 PM
  Comments - Fatality
Post A Reply Comment Options
Old 09-05-2009, 06:06 AM  
oomp
A Defias Bandit
Interface Author - Click to view interfaces

Forum posts: 3
File comments: 10
Uploads: 3
Re: Quiet reports

Quote:
Originally posted by sillysyra
What would i enter in place of RAID to make this print to my chat box (like a notification) so no one else sees it?
Currently, you're unable to. I suggest making a channel called "fatalityreports" and setting OUTPUT to "CHANNEL" and CHANNEL_NAME to "fatalityreports" - that should do the trick until I stop being lazy and add a more practical option to do so.
oomp is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 08-13-2009, 09:24 PM  
sillysyra
A Defias Bandit

Forum posts: 3
File comments: 27
Uploads: 0
Question Quiet reports

What would i enter in place of RAID to make this print to my chat box (like a notification) so no one else sees it?
sillysyra is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 07-07-2009, 12:51 PM  
oomp
A Defias Bandit
Interface Author - Click to view interfaces

Forum posts: 3
File comments: 10
Uploads: 3
Quote:
Originally posted by sammael
just been in OS25 and it reported every voidblast death as Fatality: Name > Unknown
Hmm. I'm curious to find out what's causing this behaviour - do you happen to have a /combatlog of the raid?

EDIT: I did OS25 yesterday myself, and I experienced what you are referring to and I can confirm that Fatality is actually working as intended. This behaviour occurs when you are in a different phase to the person who dies, so let's say you take a portal, and then someone dies from a Void Zone outside the portal, your combat log won't record the damage, so when you come out of the portal, and UNIT_DIED fires, Fatality reports the death as Unknown, since, as far as your combat log is concerned, there wasn't any damage which could have killed that person.

You can test this with the latest version (v1.1.0) by dying from a Void Zone yourself, which will ensure your combat log is in range of the damage source - if Fatality still reports the death as Unknown, please let me know.

Last edited by oomp : 07-11-2009 at 05:07 PM.
oomp is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 07-07-2009, 11:24 AM  
sammael
A Defias Bandit

Forum posts: 2
File comments: 48
Uploads: 0
just been in OS25 and it reported every voidblast death as Fatality: Name > Unknown

didn;t test on angel form cuz i was asked to turn addon off
:<

reverting to 2 versions back for now ^^
sammael is online now Report comment to moderator   Edit/Delete Message Reply With Quote
Old 07-06-2009, 03:19 PM  
oomp
A Defias Bandit
Interface Author - Click to view interfaces

Forum posts: 3
File comments: 10
Uploads: 3
Quote:
Originally posted by sammael
latest version reports when my priest dies "second time" in angel form as Fatality: Name > Unknown
This is not intended, I'll look into it.

EDIT: I've hopefully fixed this in the latest version (v1.0.9a) - please test and let me know.

Last edited by oomp : 07-06-2009 at 08:02 PM.
oomp is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 07-06-2009, 03:02 PM  
sammael
A Defias Bandit

Forum posts: 2
File comments: 48
Uploads: 0
latest version reports when my priest dies "second time" in angel form as Fatality: Name > Unknown

previous version didnt do this is this intended ?

thanks for great addon



:edited atrocious typos ^^

Last edited by sammael : 07-06-2009 at 04:30 PM.
sammael is online now Report comment to moderator   Edit/Delete Message Reply With Quote
Old 07-06-2009, 12:53 PM  
Skylinee
A Kobold Labourer

Forum posts: 0
File comments: 166
Uploads: 0
Probably a weird request, but here goes: Option to report the remaining (7 if the limit is 3 during a 10man raid for example) deaths to self only, and the option to easily print any of those self messages to raid if needed (shiftclicking them if they're bracketed maybe). This way i can see all deaths without unnecessary spam.


Also the latest version reports priests dieing twice when they die because of http://www.wowhead.com/?spell=35618


Please blacklist this spell.

Last edited by Skylinee : 07-06-2009 at 02:14 PM.
Skylinee is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 07-06-2009, 12:35 PM  
oomp
A Defias Bandit
Interface Author - Click to view interfaces

Forum posts: 3
File comments: 10
Uploads: 3
Quote:
Originally posted by Vaihnae
I'm used to announce ,the reasons why someone died, in a costum channel.
Code:
local OUTPUT = "CHANNEL"
local CHANNEL_NAME = "cname"
Your code should look like that, where "cname" is the name of the channel you want to report to, e.g. "fatalityreports" or something.
oomp is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 06-25-2009, 03:25 AM  
Vaihnae
A Kobold Labourer

Forum posts: 0
File comments: 26
Uploads: 1
I'm used to announce ,the reasons why someone died, in a costum channel.
But I keep getting the following error:

'Unknown chat type'

Is there a way to fix this?


so long,
Vaih
Vaihnae is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 06-13-2009, 10:29 AM  
oomp
A Defias Bandit
Interface Author - Click to view interfaces

Forum posts: 3
File comments: 10
Uploads: 3
Quote:
Originally posted by Skylinee
I liked the way it was before, tanks are supposed to die from Meltdown for example. Could you add a on/off option for this?
The aim of this addon is to provide quick information about how/when people die, regardless of if their deaths were intentional. It helps people in the raid who aren't perhaps paying attention to raid frames, or for post-wipe reference (e.g. Healer died first, then 2 seconds later a tank, and so on.)

Another reason for this choice was because I was experiencing a bug when the Meltdown tank died, it'd report the last hit they took (e.g. 20k Melee from Steelbreaker), which wasn't actually the hit that killed them; Meltdown was.

With that being said, if you'd still like to remove this functionality, which I don't recommend, you can delete the following from lines 41 to 45:

Code:
elseif subevent == "SPELL_INSTAKILL" then
     local spellID = ...
     tstamp = TIMESTAMP and date(TIMESTAMP_FORMAT).." " or ""
     slink = GetSpellLink(spellID)
     candidates[destName] = instakill:format(tstamp, destName, slink)
oomp is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 06-13-2009, 07:07 AM  
Skylinee
A Kobold Labourer

Forum posts: 0
File comments: 166
Uploads: 0
''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''


I liked the way it was before, tanks are supposed to die from Meltdown for example. Could you add a on/off option for this?
Skylinee is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 06-01-2009, 04:26 PM  
Kogasu
A Kobold Labourer

Forum posts: 0
File comments: 16
Uploads: 0
Like it so far. Keep it simple. There are other tools Like Grim Reaper for parsing combat logs and determining "why" someone died. This mod isn't one of them, but when the same healer dies twice in a row to the same event announced in raid by Fatality, there is usually pained silence in vent. Haven't had a raid leader ask "what killed you" since I started running this. Don't let people goad you into bloating this into a monster, it does what it's supposed to, quite well. Keep up the good work.
Kogasu is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-31-2009, 02:56 PM  
oomp
A Defias Bandit
Interface Author - Click to view interfaces

Forum posts: 3
File comments: 10
Uploads: 3
Quote:
Originally posted by Skylinee
is it possible to implement some kind of system that lets you click a link to show how people died
Sending custom links to channels is not possible, attempting to do so (custom spell/item links etc.) will disconnect you from the server. GreedBeacon and SpamageMeters both require you to have the addons installed to be able to view the links.

Quote:
Originally posted by khurzog
is there a quick way to turn this on and off?
Added a simple slash command in v1.0.4 (/fatality or /fat) to toggle the addon on/off. Update to the latest version.

Last edited by oomp : 06-01-2009 at 10:35 AM.
oomp is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-31-2009, 02:33 PM  
Skylinee
A Kobold Labourer

Forum posts: 0
File comments: 166
Uploads: 0
1 request though: My guildies don't want ANY spam running anywhere, so is it possible to implement some kind of system that lets you click a link to show how people died instead? Similar to what Greedbeacon does with rolls.

Like this: [Fatality: Click to see who died and why.], and clicking this opens a tooltip with a list of people and how they died. This link could be sent when everyone has exited combat for example. This would really be awesome.


Edit: Here is another example that does this with Damagemeters: http://www.wowace.com/projects/spama...ers-in-action/

Edit2: Not sure if this would work though, i guess everyone would need this addon installed to see the link provided :/

Last edited by Skylinee : 05-31-2009 at 02:45 PM.
Skylinee is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-31-2009, 02:18 PM  
Skylinee
A Kobold Labourer

Forum posts: 0
File comments: 166
Uploads: 0
Love the addon, especially that it links what kind of spell was used on the kill. Lightweight and no errors so far, keep it up.
Skylinee is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Post A Reply



Category Jump:




The Network:
EQInterface | EQ2Interface | LoTROInterface | MMOInterface | War.MMOUI | WoWInterface | VGInterface | Allakhazam | Thottbot | Wowhead | Zam


©2009 MMOUI / ZAM Network
vBulletin - Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.