[bagelbite]

I made a wowwebstats parser to estimate tps which works for warriors, druids, and paladins. It works for english, spanish, french, and german reports.

WowWebStats Tps Calculator

I'm also building an index of tps reports by encounter/boss. I'm currently working on automatically filtering out bogus reports so it doesnt skew the aggregate statistics too much. The primary filters will depend on the wws calculated battle and dps time. Reports which dont have at least 30 seconds of dps time won't be indexed, as well as reports which have more than a ratio of 2:1 battle time:dps time. I also plan to have some minor class specific filtering to help identify reports where the player is blatantly doing dps or healing instead of tanking. I'm likely to tune these numbers and ratios.
Indexed Fights




If you have a bug to report, please include the url to the wws report which caused the bug.
Feel free to convince me of an added feature you have in mind.

I also need people to tell me which abilities shouldnt ever cause threat. For example, damage done from gruuls "Shatter", and healing from "Improved Leader of the Pack", I've completely filtered out from the results. Id like to do this for any other irrelevant entries as well. While you can filter these out of the calculation by using the checkboxes, if theres no reason they should ever be included, id like to just strip them out. List any you know of.

If someone wants to help with chinese/korean translation, let me know, I just need a some names of certain abilities as they appear in the combatlog.

*For those of you comparing this calc to the Coolyo[dot]org calc, I will explain the difference in results:
-The coolyo calc does not track arbitrary sources of threat, while this one tracks anything that wws can pick up, so naturally tps will be a bit higher(but this is more accurate).
-The coolyo calc uses an incorrect innate threat value for devastate. Devastate innate threat is 176 when 5 sunders are stacked. The coolyo calc uses 101, which is the old value before the devastate buff.
-The coolyo calc uses an incorrect innate threat value for heroic strike. Heroic strike innate threat is currently 196, which corresponds to heroic strike rank 10. The coolyo calc uses 220, which is the estimated innate threat for heroic strike rank 11, which has never been available on live servers yet.

[Ciderhelm]

Going to move this to Theory to hopefully get a bit more time at the top and feedback on the numbers.

[Khordam]

Still trying to find a calculator that works with localized reports... I was pleasantly surprised that WWS works pretty well with a german combat log, but haven't been able to find a TPS calc that does the same. Also, I'm too lazy to get the ruby script & runtime environment.

If, by any chance, you plan to localize this one, do tell. I'd be more than happy to help!

[bagelbite]

Source: Khordam Still trying to find a calculator that works with localized reports...

Try now, should work.
It will probably fail if the report gets queued when wws gets busy though. Any chance you can tell me the message they display when a report is queued? for example, in english they display "Your report is being loaded".

Whats the german message? be _exact_ please.

[bagelbite]

Question:
I've heard paladins generate 50% less threat per point of healing than other classes. Healing threat is already 50% of the amount healed. So, to properly calculate threat from pally healing effects while tanking(like, prayer of mending heals) would it be
effective heal of 1000
1000 x 0.5 x 0.5
result 250 threat?

[Leytur]

This is awesome. Can we get a frontpage announcement when we're sure on the accuracy of the results?

Did I mention this is awesome?

[Davi]

Hey, I noticed that the wws URL changes based on how you get to your personal report for a particular encounter. For example, if I choose the encounter first, and then click my name I get this link:

http://wowwebstats.com/mdgkjmybmhdhw?s=3791-4162&a=11

If I choose my name and then the encounter I get:

http://wowwebstats.com/mdgkjmybmhdhw?a=11&s=3791-4162

which gives me an error when I submit it to your calculator.

The only difference is "a=11" & "s=3791-4162" are transposed.

[bagelbite]

Thanks Davi. Should work now.

[Svotnick]

Ability Damage Ability Threat Total Threat Include
Heldenhafter Sto� 29228 0 43696
Schildschlag 22911 0 34252
Verwüsten 18618 0 27834
Swing 11864 0 17737
Rache 7862 0 11754
Romulos Gift 2000 0 2990
Dornen 1431 0 2139
Donnerknall 154 0 230

Ability Effective Heal Threat Include
Blühendes Leben 6401 4784
Gebet der Besserung 5604 4189

Total Threat Seconds TPS
140632 267 527


No Ablility Threat here

Svot

Sry for format

[bagelbite]

I should probably clarify what is meant by "ability threat". I think base threat would probably be a more suitable name. If the ability has a flat amount of threat, that never changes regardless of the damage done, that would be base threat. A lot of warrior abilities have base threat, but in my very brief searching for druids and paladins, I didnt find any abilities with base threat for paladins, only threat modifiers. I found 3 abilities with base threat for druids, Lacerate=285, Maul=322, Faerie Fire=108. Hope those are correct.

I'm trying to decide which statistics to show and which not. Im debating having that column at all.