issei

I've been using this for our timed ZA runs, and I love its functionality and ease-of-use. However, I'd like it even more if buff and debuff gains/losses (duration, amount of occurrences) were tracked so I could monitor things like Rampage uptime, rogues' SnD usage, and so on.

 

racy

They are tracked already, just not displayed in any comprehensible way :-) If you have any idea about how to present something like that please do.

 

racy

I added filters to the Show all events dialog so that the user can select which events to show based on source, destination and an extra filter for all fields. Thanks for the suggestion :-)

Btw, it is included in the 1.19 release.

 

issei

I suppose it might clutter things up a bit, but I'd like a table for buffs and debuffs that shows a column for amount of times gained, total duration, and % uptime of the fight duration.

 

Nekrataal

Maybe i'm just blind, but i just can't find the possibility to track incoming dmg on tanks. Ideally something like grimreaper, showing abilities/dmg against the tank and beneath a HP Bar.

 

Suran

Select the enemy (or more) you want in the left column, then right-click with your mouse and select 'show all events in list (merge)'
In the new window, put you MT's name in the 'destination' filter and hit 'apply filter'.
You now essentially see what grim reaper shows, adjust filters as needed.
Warning: due to a bug (?), events are separated into damage and non-damage events, which means the first part of the resulting table are all non-damage events ordered by timestamp, followed by all damage-events ordered by timestamp.
Because of that, it's not excatly what Grim Reaper shows. I already filled a bug-report on the official forum.

On a side-note: what about some more advanced filtering, like regular expressions? would it be hard to add something like that?

so long
Suran

 

racy

Nekrataal:
You can show statistics for all abilities and melee hits etc vs a tank. Just select a boss in the fight table, then select your tank in the participants table. Then right click and select "Merge and show details on received events" in the popup menu. If you want to see all events vs a tank then check out the "Show all events" dialog and use the filters as Suran suggested.

Your suggestion about a health bar and a list of damage events etc is pretty cool. Maybe I will make something like that.

Suran:
The sorting bug in the "show all events" dialog is fixed in the latest version.

 

racy

I just made a revamp of the automatic boss parsing system. I made it easier to maintain with encounters descibed better in an XML file.

The merging of fights is much faster now after finding a better way to do some technical stuff (Thanks Burnow for the inspiration).

Also its now possible to view more information about an event in the show all events dialog by double clicking it.

 

issei

Thanks for your continued work on this, racy.

 

racy

I started making an export to XML feature that is in a decently working condition. There is still no way to view the XML info in a browser though, except viewing it as raw XML :-P A few people have voiced an interest in making a viewer to show the XML files, but anyone is free to make their own viewer if they want to :-)

Added support for more languages when doing class parsing and automatic boss parsing. Right now there is a German and English version and a French is on the way courtesy of Venuziak.

I hope that the HTML export will no longer be needed in the future so nothing further will be developed on that.

 

racy

Just released a version with greatly reduced memory usage.

 

Unravel

Nice job on your parser, racy! Sorry for abusing your thread in this fashion, but...

I had a very idea for a log analysis tool, as I am not terribly interested in the statistics themselves, but how to display them nicely, with enough options to drill down into the details. The outcome a graphical analysis tool for World of Warcraft combat logs, called WowPlot. It is now at a stage where I feel it is
a) ready for some wider testing, and
b) good enough to be useful to people.
Its main focus lies in evaluating time-dependant combat performance in a very free-form fashion, which is in contrast to the mainly statistical approach of other tools.

WowPlot requires Mac OS X Leopard (10.5) and is a Universal application.

If that didn't turn you off, have a look at the page / app and I'd welcome any feedback.

 

racy

New version out.

1.24

Added a raid dps timeline graph to the fights table popup menu that shows raid dps for selected fights in the same graph.
Added a received healing timeline graph to the participants table popup menu that shows healing done for each healer, and damage done, to a player.
Removed the qnplot library and now only use JFreeChart.
Various XML export improvements.
Made some changes to the overhealing calculations (pretty minor).
Also various small changes here and there.

 

Elois

Where is version 1.24 distributed? I clicked on your link and it took me to Curse Gaming which listed version 1.23.

 

Borona

You can find it on his website. Wow Log Parser forums / Wow Log Parser 1.24 binary and source

 

racy

On both curse and my own webpage as listed earlier in this thread.
Curse is slow to approve my uploads sometimes. It's uploaded but they need to have someone at their place press the approve button or something.

 

NinJOu

Really great addon !

Thanks for the hard work !

One suggestion, though : is it possible to add a TPS graph like you did with DPS and HPS ?

It would be really great since TPS report only works on the whole fight currently.

In Felmyst, since a tank can only build in P1, we can't really see our instant TPS and where we failed to build constantly.

 

racy

I'm not sure that threat can be accurately calculated from log files since you need to know stances, talents, etc to get correct values. You also need to track buffs like blessing of salvation (which is doable).

So anyway, it's not straight forward to do.

 

Druitt

I've thought about programming a similar filter back in the day, and several things that may or may not be issues came to mind, so I put it on hold:

1. The logs have no indication of non-actions, including location, facing, and movement. So how will you know if the tank took a couple of steps backwards and stepped out of healing range at a critical time in the fight? All you'd see is that the healer took 4 or 5 extra seconds to get the heal off... a second or two to realize that something was wrong, a second or two to move forward, and then cast again. The log will not indicate movement or anything, just an actionless time gap -- healer's fault.

Not just actor locations, but mobs and things like totems and AoE. What if the Shaman dropped the totem 3 yards short and the MT gets feared? What if the OT parked his mob 5 yards the wrong direction, and that had a cascading effect?

2. How do you avoid the "blame the last domino to fall" syndrome? Most wipes, I'd guess, are not a single player's fault. (OK, I wiped a raid single-handedly with a stupid mistake, but it was while everyone was buffing before the pull.) That's why the typical PUG blame is either "poor tanking" or "not enough heals", when in fact the problem was more substantial than that. And I'm not talking something as simple as "group-wide DPS was low, meaning healers had problems, meaning the tank died", but longer chains of events.

It's not an excuse to not have a tool, but it's like a novice using R, SAS, or SPSS and "proving" something because statistical test XYZ indicates that ABC is statistically significant to the 95% confidence level. Did they use the correct test, given the type of data and ABC? Were the methods used to get the data correct? There's a very long chain and it's easy for an amateur statistician to really screw things up, but with authority, because the numbers come out of a Name Brand statistical package using a Name Brand statistical test.

In like manner, even a clever, well-informed Raid Leader could fail to account for all of the what-ifs and things like #1, and #2, above, and could come to an "irrefutable, based on the logs" proof that it was A's "fault" when in fact it was B's. (Or more probably, the logs don't give the proper information to tell who started the death spiral.)

3. How do you account for real-time judgement? The healer's making a bunch of real-time decisions in terms of locations, spell usage, spell rank, mana burn rate, etc. Looking back at only the recorded numbers won't give any feel for the issues that someone had to tradeoff in a half-second decision which might turn out to be "wrong". ("Wrong" in the sense of being the last in a series of decisions by multiple actors -- the one that the tool user happens to see and says "Aha!" and stops looking.)

Yes, you can see that the Shaman is dropping totems 3 seconds too early and wasting mana. You can see that the Druid is throwing a Wrath into his rotation when it should be an extra Starfire instead. Things that are cyclical, repeated through a fight. Things that are averaged together over 30 or 40 actions. It's like statistics, really only working with masses of data, not individual data points.

But will it be evaluated that way?

Perhaps this is interesting, but not really applicable... Give people a tool and while most will misuse it, many will not and after all "It CAN be done, so therefore SHOULD be done." Just my personal worries that I've not been able to resolve.

 

Moonblaze

great work!

I love this addon really

 

racy

Thanks a lot :-) I'm glad you like it :-)

I have started working on some kind of arena mode for the parser, but I'm mostly stuck in "idea mode". I start programming some classes, then I get stuck and stop for a few days, start over with some other idea and get stuck. So it's been kind of slow progress lately.

 

racy

I added a new dialog to the parser in version 1.25. It shows aura applications and removals from a player in a graph. Its quite easy to see how you manage your trinkets and short time buffs with it. The image below shows an example from one of my logs.



I also fixed a little problem with overhealing and health deficiency that occured when someone died. The health deficiency wasn't reset to 0 so when someone used food to get full health (which doesn't show in the log) the parser showed large negative values even though someone was full health. It now resets to 0 when someone dies.

I'll as usual try to get it up on curse but for now the latest version is only available on my site.

 

racy

Another update, this time a speed update. Parsing of large files should be much faster now with version 1.25.3.
I have problems uploading to curse at the moment though so the release is only present on my website for now.

 

racy

Version 1.26 is released. I added an experimental arena mode for the arena people to try out. 1.25.3 is finally available on curse after many strange errors when trying to upload. I'm still struggling to get 1.26 up there though.

1.26 Changes

Added an experimental arena mode, try it out, it can be found in the Tools menu.
Fixed a bug with dispell and spell steal events, they should now work.
Added scroll wheel zooming to the graphs.
Added a new events graph.

 

racy

My web server computer just crashed just so you know if you try to download any new versions...