WWS and 2.4 sample logs - Page 2

Morwen · 02/13/08, 3:52 PM

Is there documentation somewhere on the actual meaning of all the values in the PTR logs? It doesn't seem to be something we are just meant to figure out on our own, but I haven't been able to turn up anything on the official forums.

Machinator · 02/13/08, 3:58 PM

Originally Posted by Malan

Suggestions:

The ability to view Graphs of DPS vs Time, etc, not just a bar chart
The ability to display DPS/Healing by phase of an encounter - ie, 'splitting' an encounter into phases that can be viewed independent of one another
The log browser is incredibly limited and very difficult to search for specific events. It would be more helpful if I could search for things like "[Everyone] [Death] [Ability: Doom Fire]" or "[Everyone][Damage Taken][Flamestrike]" so that you can locate your problem areas.

I'll echo these as being most important to me. I don't think you get enough information for it, but graphs of a Tank's HP or a DPS warriors AP would be cool.

Edit: "An expiration type report showing last X events before a player died would be useful too." This is already in there, I think I knew that a long time ago and forgot. Whoops.

Docjowles · 02/13/08, 4:04 PM

Originally Posted by Morwen

Is there documentation somewhere on the actual meaning of all the values in the PTR logs? It doesn't seem to be something we are just meant to figure out on our own, but I haven't been able to turn up anything on the official forums.

If you follow the trail of Blue posts through this thread, there is at least some info: WoW Forums -> Upcoming 2.4 Changes - Concise List

Docjowles · 02/13/08, 4:05 PM

Originally Posted by Machinator

I'll echo these as being most important to me. An expiration type report showing last X events before a player died would be useful too.

This exists already, if I understand you. Click on the player, click on Summary, click on the time of their death. You'll see the last 10 seconds or so before they died.

Edit: Apologies for posting twice in a row, I will say 300 Hail Kaubels

Fola · 02/13/08, 4:31 PM

Originally Posted by Machinator

I'll echo these as being most important to me. I don't think you get enough information for it, but graphs of a Tank's HP or a DPS warriors AP would be cool.

Edit: "An expiration type report showing last X events before a player died would be useful too." This is already in there, I think I knew that a long time ago and forgot. Whoops.

A TPS Graph over time or simply a bar chart of the average TPS for a fight would be helpful. There is a tool currently that calculates the TPS based on the WWS parse for the warrior listed here:

Kenneth Gant Niebuhr - Online portfolie

Possibly just incorporate the backend used for it?

Koosha · 02/13/08, 5:01 PM

Originally Posted by jusion

From what I've heard, WWS Scoreboard manually updates their stuff. Thats why only guilds with Top 100 kills, non-anonymous and non-'cheating' logs get added.

4. Why is my report missing?

* We only pull data from WWS on a limited schedule. New reports may take a couple days to appear.
* We check each report to verify it is valid. This is done by comparing the amount of damage done to a known baseline. Reports with bad splits/merges will report too much or too little damage and be marked as invalid.
* We require that your guild WWS reports include a link to your guild's homepage. Reports without this will appear as "Unknown - No Website Listed".
* Guilds that have repeatedly edited their combat logs will have all future reports marked as invalid.
* We only pull the top 200 reports for character parsing. If you have an exceptional player DPS in an encounter that does not make the top 200 reports, we can parse it manually. In that case, please allow 2 days from the time the report was posted and if the player DPS still has not appeared, send us an e-mail at the link below with the reason for requesting a manual parsing, the guild name, server name (including US or Europe), and a link to the WWS report.
* Please remember to recalculate your DPS based on damage/time and ensure that this would place in the top 25 of character reports for the class on that boss.

From WWS Scoreboard

• Miles · 02/13/08, 9:37 PM

Not really on-topic but since I can't make new topics yet (I'm a read everything before making a noise guy), I guess I'll reply here. I've reverse engineered the default Blizzard Combat Log to create a complete list of events and parameters. As far as I can see, this new system is *very* easy to parse. Too bad they didn't picked the ParserLib-x format instead of rolling their own, but it's miles (no pun intended) ahead of preg_match or java.util.regex.Pattern.

The list can be found at devel:wow_combat_events_in_2.4 [DokuWiki], license is CC-BY-SA so feel free to repost, edit and extend it.

If you have any captured logs, please link them in this thread too. The WWS-forums kinda failed to load here. I'm interested in verifying a rewrite of one of my mods (WoW24 broke MCL as expected) and getting some data into one of my pet projects, a log analyzer (read: shinier version of WWS). The last one was kinda abandoned when Blizzard announced the CL change, now I just can't wait for the patch to go live.

Macked · 02/14/08, 11:00 AM

Macked here, one of the programmers for wwsscoreboard.com

If you have any questions about our methodology or general suggestions, please contact us at wwsscoreboard@gmail.com

We try to answer as many e-mails as we can.

@fola

For a fight that has a healing factor the numbers will be off, there is nothing that we can do about this. We rank raids by dps, so even if a guild takes slightly longer to kill a mob, but their dps is higher, they will be ranked above a guild that takes less time to kill the boss, but has a lower dps.

@Malan

Yes, we do have a valididty check. Multiple layers actually. As stated in the faq, we compare each kill to a known baseline that's correct. After this we see if there were dual reports uploaded that have the same kill time/dps time. We find a lot of people upload anonymous reports, and then instantly upload a guild report. This is all done automatically. Some stuff still gets through and we have a secondary check that we run ourselves to validate/invalidate reports.

If a guild has two reports for the same boss on the same day with different times. We take the one that has a longer time, since it contains more data. If both times are the same, but the dps is different, same thing as before, we take the one with the higher dps since it has more data in the combat log.

I hope this helps, and as i mentioned, email us (or post on our brand new forums!) any questions you may have.

Cheers
-Macked

Kyth · 02/15/08, 6:33 AM

Originally Posted by SOaD!

If you have suggestions, we'll keep an eye on both threads, so feel free to post ideas.

It's very confusing, when you're looking at the details for a caster, that it only shows the number of non-crit, non-miss nukes cast. This has caused huge amounts of problems for most people I know who use WWS, because it's non-intuitive that what you need to do is click on the line to get a drop-down of the details, add those together, and then do the same for the person you want to compare them to.

No one is ever comparing "number of non-crit nukes" that two people cast, and that summary line could be far better used if it at least combined crit and non-crit.

A simple calculation of "uptime" for dots would be very nice to have in the detail. Fight length divided by the number of dot ticks basically. I do this manually now.

Finally, it's easy to calculate what VT should have returned (based on spriest dps and fight duration) versus what it did (based on number of ticks), and having this efficiency percentage easily viewable would also be awesome.

I don't know if this matters/is fixable, but: it seems lifetap isn't counted as a combat action for locks, so a destruction lock ends up with an oddly low combat percentage (and higher dps) as a result because "shadowbolt, lifetap, lifetap, shadowbolt" takes more than 5 seconds between supposed-combat actions.

If I'm wrong, ignore me

.

ninor · 02/15/08, 6:54 AM

When you search for fights vs a specific boss it would be nice if the default view listed total damage done in addition to what is there now (Date, Raid DPS, Guild name and Class setup). Would be helpful in sorting out at a glance which parses not to bother looking at in certain fights.

rooppa · 02/15/08, 7:22 AM

Originally Posted by ninor

When you search for fights vs a specific boss it would be nice if the default view listed total damage done in addition to what is there now (Date, Raid DPS, Guild name and Class setup). Would be helpful in sorting out at a glance which parses not to bother looking at in certain fights.

Forgive me for this, but on damage done, wouldn’t this be exactly the same for virtually all kills where the boss does not heal? (allowing for a slight varience in over killing the boss at the end of the fight)

Boss has X health, so cause X damage on boss, boss dies.

• Chicken · 02/15/08, 7:34 AM

Originally Posted by rooppa

Forgive me for this, but on damage done, wouldn’t this be exactly the same for virtually all kills where the boss does not heal? (allowing for a slight varience in over killing the boss at the end of the fight)

Boss has X health, so cause X damage on boss, boss dies.

It's mostly meant so you don't open up a kill thinking "Whoa, these guys do bad ass DPS!" only to find out that they included some NPCs as pets; that does still produce the same overall health on most fights, but it makes a difference on Teron Gorefiend for example.

alkis · 02/15/08, 7:54 AM

Originally Posted by Chicken

It's mostly meant so you don't open up a kill thinking "Whoa, these guys do bad ass DPS!" only to find out that they included some NPCs as pets; that does still produce the same overall health on most fights, but it makes a difference on Teron Gorefiend for example.

Or even worse they added (using a script) X amount of damage on each of their attacks to make their dps look awfully high.

rooppa · 02/15/08, 11:23 AM

I understand now then, in that case then the addition would certainly make sense for ease of perusing the latest updates.

Trouble · 02/15/08, 4:34 PM

This doesn't have anything to do with the parser itself, but it would be great if the top dps list on WWS wasn't filled with garbage parses. Adding a few filters should go a long way towards cleaning those lists up:

- Figure out an acceptable total damage range for each fight. A lot of the bad parses are simply ones that have bad merges and have double total damage. Very easy to filter these.

- Don't show anonymous logs. A large portion of the bad parses also happen to be anonymous. For top ranking purposes people are usually more than happy to take credit for their kills.

- Don't allow parses that are obviously duplicates. The combat log provides date and time, this should be pretty simple to do.

Those simple changes would go a long way towards getting workable top dps lists, rather than the garbage that's up there now for nearly every boss.