As we traverse through SSC we're having alot of people die to alot of abilities that I'm fairly sure the mobs don't even have but unfortunatley I cannot see whether the "omg he bolt me for 9k then roundhouse kick for 6k!" claims my raid gives me are true. Basically I need a mod that I can use to see how raid members die and if possible bring up anything I like from their combat log. I'm fairly sure their is one out there(kungen from nihilum uses one, and an old officer in our guild had one) but as Kungen doesn't reply to tells and our old officer is MIA I need you guys to help!

It's been suggested I use recap but I'm fairly sure that isn't the mod I'm thinking about. I've got recap downloaded to try it out though.

EDIT

Forum poster SLAKE has had a crack at this mod, initial reports are good.

http://files.filefront.com//;7405958;;/

Sw stats can do that.. you can make it show the dmg x person in your raid took from abilities/magic schools (shadow, fire etc)

as a raidleader myself I used ct raid in former times but as in tbc it went too laggy when ppl died etc. pp.

Therefore i switched to xraidstatus and grid to watch the raidstatus.

Grid itself to see "the raidheal" overall and for xrs i have modified it to show the dead people.

Of course it doesn't give you the exact info you are looking for (why people died) - but you can easily "learn" if people beat about the bush or tell you "the truth"

Some people dislike the layout of grid so I can also recommend perfect raid as an ideal overview addon.

regards
rOb

swstats we use and could make do with probably but I'm just fishing for a specific mod.

I'm using perfectraid right now and its great. What I'm looking for specifically is a mod that I can use that is easily tracking how a raid members dies, maybe the last 10 seconds of bobthemages log before the line "bobthemage has died" which is then saved for me to view easily. It sounds like it wouldnt be so hard to do but as far as I know(not very far) there isnt a specific mod for this kind of thing.

I think RDX6 does the combat log stuff, but it costs money

Wow web stats is what you are looking for. If you do the server version of the report it will generate death reports for each person detailing the last 30 seconds of their life.

http://www.lossendil.fr/serendipity/ is the website for it

Edit: yes it doesn't quite do it inside wow which would be prefered, however doing it inside wow isn't available as far as I know.

I know something like this is possible, because a guild on our server used a mod on C'Thun that mocked people for dying to the retard beam. They may have shared it with us; I'll see if I can dig it up.

Posting something like "You got GLARED!" isn't that hard (simply watch for anything that reads 'xx takes 50k damage from dark glare', but reconstructing the last 30 seconds before someone died requires keeping 'state/memory of everything that's happened in the last 30 seconds.

That sort of task is generally better accomplished with post-facto processing like WWS, trying to keep in memory everything that's happened in the last 30 seconds will just lag your machine.

I direct you to this announcement: http://elitistjerks.com/f15/a5-a/ .

I have been thinking about this for a couple of hours, and I don't imagine it would be that difficult, or consume too much memory.

Making a couple of assumptions;

1. Don't keep 30 seconds, keep a set number of records (maybe 5,10,15,20) of both incoming and outgoing damage/healing

2. Restrict these entries to "text strings", which would tend to have a maximum size of 80 characters.

I think that most people could work out what went wrong examining the last 10 timestamped entries.

Assuming 25 people in the raid, with 20 entries each of 80 characters, that's only 40k of data. Bump up the number to 100 entries each, and that's still only 200k. Given that there is also a logical datastructure associated with this, add a 20% overhead, and I can only see a maximum of 250k of memory used.

You could also apply simple filters to stop VE spam obscuring the results.

I've already written one AddOn, I'll have a look at what it would take to do this (probably by ninja-ing another combat log parsing tool) but I don't see this being a particularly difficult tool to write. The hardest part (for me anyway) would be to write the UI that would display the results.

If you want to watch tank/mob interaction specifically you can create a window and set filtering rules to only show stuff happening to that particular tank. This can be done with a mod such as SimpleCombatLog. You will need your log range to be set to 200 to be sure to get everything, and you will want in game timestamps showing tenths of a second.

I modified my chat mod to show tenths of a second timestamps. There are probably existing mods that do this.

You can wait for RDX-EMU to be updated post patch 2.1. It is from few devs that worked on original RDX, from what I understood and best of all its free. No idea if they got combat-log polling in free version.

the problem is, to make this work you have to log any combat output and discard anything older than 10 seconds and save the time-span if someone died. thats a HUGE memory hook

Please re-read what I wrote.

There is a fixed maximum size of the data set based on the number of people in the raid, and the number of events you want to keep per person. The information can be keyed on the person in the raid.

My rough estimates are that for 100 records per person in a 25 man raid, that would work out to be 250k. 100 records per person is a very large number given that most heals take 2-3 seconds, most attacks take 1-2 seconds and most mob attacks are 3+ seconds.

Zerohourman: I've been looking at the code for Recap and DamageMeters and seeing if any of them provide "hooks" to just enable this functionality via a plug-in. They already have the parsing and event allocation code, and it makes sense (me being lazy) to just reuse all that and hook in a series of buckets that can be examined. No luck so far.

Good to hear, I had suspected that mods are kind of doing this already but as nobody has done it yet I distress that as wow has been out a long time I'm suprised that a mod like this doesn't exist(or is widely known). Recap is effective but a trigger of "Mageman has died" then the last 10 seconds of his actions saved into some sort of output that I could see would be invluable and I imagine it'd become a very popular mod for alot of raiders.

The person that runs our WWS logs and converts them wrote a little parser that scans through the combat log. The output looks as follows:

96.42 Teez 3894 Melee The Lurker Below 9984 Melee 4532 Melee

What that means in this specific case is:

I died 96.42% through the duration of the combat log segment, the killing blow on me was made by The Lurker Below and was a Melee hit. He also implemented the last two damaging abilities that hit the target so you can track back a bit - in that particular example the crushing (9984) that happened just prior to the killing blow would be the culprit.

Example output, exactly the way his script prints it:

This has given us pretty much the easiest way of discovering who's dying to what specifically (he creates a log of this after every attempt). It allows us to approach people directly knowing what their problem was, and rectify it much quicker. This definitely shows you more accurate information than the basic WWS can, and more accurate information than SW_Stats, DamageMeters or even Recap could, too.

I can try and see if he'd be willing to post the script he uses - I believe he frequents these boards too.

You are now officially my new best friend.

Thanks Shalas.

I would really enjoy a parser like this.

Yes, that parser would be alot of help for now. Checking after each attempt is fairly painless though I'd still prefer a ui mod for it.

Any joy pewsey?

This strikes me as the kind of thing that's like those inventions that make everyone say "duh, why didn't I think of that?".

Anyway, this intrigued me so I whipped up a mod to do it real fast; you don't even need Parserlib, really. I call it.... Expiration.

Commands should be fairly intuitive, uses the standard Ace2 Console library, so it works with DeuceCommander etc.

Let me get this right; Expiration does what the OP described? You Sir, should probably make a bit more fuss. If this works it's genious; a bit of a waste to bury this so 'delicately' here ;-)

Code looks good, sound thinking anyway. I shall be trying this out later on. If it works - cookies may be involved. Thanks for your effort.