This is exactly why we created wwsscoreboard.com. I was sick of trying to cut the wheat from the chaff every single time we posted a report. It started as an internal guild project to make my life easier (Thanks for thinking of me Macked) and grew into a pretty good tool for digging into WWS.

It is also something that Lossendil is looking at. Wow Web Stats • View topic - This website might be sapping your bandwith

99% of bad damage parses are caused by bad merges where nothing actually gets merged. These consistently show as 200% damage of every other report. I won't give away our exact methodology for wwsscoreboard, but the band we use is much smaller then anything less then 190% of the baseline is good. However, I'd bet that we'd eliminate 99.5% of what we eliminate if we just used 190% of baseline as our standard.

I've never understood why people continue to post anonymously. Death and Taxes is taking 16 minutes to kill Illidan still, yet they posted it. Trust me, even the best guilds wipe. We all know this, we experience it and we move on. Take anonymous off. Seriously. Or at least give us a simple option to remove it from the rankings.

While there are some parses that are duplicates, a surprising number are actually caused by bad inserts into the WWS top reports, where a report is being placed in twice. 30-40% of the duplicates fall into this category. Look at how many duplicates point to the exact same raid id. I was frankly surprised by that. Fixing this is simple though. If the same character appears in the same boss kill for the same guild on the same server on the same day (Adjusted to UTC), don't display it a second time. This even takes care of separate guildmates posting their own logs. If there are two reports with different damage and kill time, accept the longer report as valid (As it will capture more data) and if time is the same, accept the higher damage (As it will also capture more data) provided it falls into the damage band set for that encounter.

Finally, give guilds the ability to place reports on WWS that will not appear in rankings. This will allow those guilds that post edited logs (Such as removing Teron Ghosts or erasing the first few seconds of a pull) to post reports without skewing the rankings. A simple flag in the Report Settings would do.

The Death Replay is a fantastic feature, but it would be great if we could get something like Assessment's Flat Death List, which shows the deaths in the order they happened for a given attempt. When reviewing wipes, I find it extremely useful to be able to review the deaths in the order they happened, since there's often a cascading effect. This is currently somewhat difficult to do via WWS.

I've also noticed that the Death Replay will end up taking more than one page, and hitting the "next" link ends up with just a raw log page rather than one filtered by the player who died. Not a huge deal, but this confused me for a while (I couldn't figure out why the Death Replay missed the line "X has died.").

I am also interested in sample combat logs from the 2.4 PTR. I have a few short ones that I have used to make an offline log parser. I need longer ones from dungeon runs/raids etc to make sure it works correctly. The tool I am working on is on curse as Wow Log Parser.

Wow Log Parser | World of Warcraft Tools | Curse

I would appreciate it if someone could post one since I cannot get my character copy to go through, hehe.

Hi everyone,

Thank you for your suggestions.

If I sort them by number of requests, we currently have :

1. Sorting (Search engine)
2. Death management (Sorting deaths by time)
3. Graphs
4. Statistics presentation

• The search engine will be revamped from the scratch soon after the 2.4 client release. It includes everything that can be put into a search (comparing guilds, classes into a single report, cross-report comparisons, etc.)
• It's in the TODO list, but currently no release date.
• Graphs are on the work, and we do not plan to put bar charts when graphs are better (DPS, TPS, etc.)
• The render engine will be revamped from the scratch for the 2.4, and we're thinking about DPCS and things like that but nothing has been modelized yet (about new statistics).

The ability to split phases is not that easy to build in a generic way, because phases are not declared in the CL. If you have ideas feel free to post them.

Erroneous reports are not that easy to find. Each combat can be easily analysed, but a generic engine is really harder. Nevertheless we have some good ideas (that has been listed for the majority of them on most forums). As a side note we don't like exceptions treatment because the current WWS overall engine is a huge load yet, and will be increased in some ways at the 2.4. But don't worry, it is planned, we can't keep cheated reports longer.

I'm sorry to answer so late, but the 2.4 take us much time because we have to rebuild everything from the scratch (parser, network communications, server apps, and many other things). As many things have to be recoded it's the best time for us to restart on better bases. So put every relevant ideas you have else if it has been said before.

If the experience is fine, I think I will stay closer with the EJ community in the future for the enhancement of WWS. And I want to thank the EJ guild for its help.

Nevertheless, any poll we'll do regarding new features or modifications to WWS will be done on our forum because I can manage them easier, so stay tuned.

Don't forget that we need logs and logs and logs, and bigger is better but everything is okay. Currently we're particularly interested in different points of view of the same encounter (raids are the best for that) and as many as you can.

Malan, the problem with shouts usually is ... they don't show up in the combat log. So unless you have a parallel log of the chatlog or a mod logging boss yells, you are kinda lost.

Well that was just the easy division. If the shouts aren't in the log then Phase 4 begins when Kael begins to cast a Fireball or is hit for the first time, and phase 5 begins at the first gravity lapse being cast.

It would be nice to be able to do a "custom split" of an encounter not based upon "time line of the raid" but being able to select actual events in the combat log as the start and stop points of the split.

90% of erroneous reports are not cheated. They are generally caused by combat log snippets or bad merging. These show up quickly when you band a known good kill and only accept kills in that range. I can't do moroes in WWS Scoreboard, and I can't pull the damage done to just moroes himself without a second pull, which I won't do. You however can.

If you filter reports on the following 2 criteria
1. Damage to the boss within 20% of a known baseline
2. Time of the fight > 15 seconds.

You will eliminate 99% of the junk. If 2.4 combat logs record entering combat (Or you trap entering combat through the WWS Addon) you should be able to eliminate almost everything by verifying that an entering combat was seen before (Or within a few seconds of) the boss being engaged. That would eliminate almost everything except for the few groups of idiots that think that editing logs and uploading them to WWS to show how great they are, actually makes them great.

For duplicates, you just check if a player has been seen already for that boss for that day and time (Converted to UTC) and allowing +- a couple of hours for bad clocks. Since you have that for everything (I don't because of anonymous reports), it should be a lot easier when building the top reports for a boss. That would take care of almost every case where multiple people in the same guild upload a report. The WWS Addon should also be able to capture guild name and server, so that should eliminate people that can't set their guild name to the same thing as their guildmates.

Feel free to send me an e-mail if you want more details. I've offered them to Lossendil as well. I know your busy and this is at the bottom of your list right now.

In other news, the first 6k sustained boss DPS report occured yesterday. 6824 sustained for the encounter. (Damage/Time). WWS Scoreboard

Speaking of which, your guild has quite a few cases of multiple same-day same-fight same-player reports uploaded.
Wow Web Stats

No, those are a bug in the ranking code. The URLs are identical. No idea why that is happening.

So, have anyone done any raids lately on the ptr, it would be really nice to get a log from a real raid to work with :-)