Source: Dragaan
Hmm.. I just did it again today, and its reporting what seems to be correct values now. I really don't know what I might have been doing wrong, as I am sure I tested it a few times yesterday. But disregard my last post. Sorry. |
I think I know what it was.
I started allowing urls to wws reports for the entire raid(including different bosses, attempts, and trash), whereas previously I only allowed urls to single boss attempts. If you weren't actively tanking the entire raid, your tps will be low because the duration of the parse will include downtime, bringing down your average. You probably submitted a url which was a summary of the entire raid.
For example, this parse spans 4 boss fights + trash
Sifr - WWS
same player, but this parse spans only the supremus death
Sifr - WWS
So, I added the ability to choose between how the calc will determine the amount of time to use to calc your tps. The default remains as battle time, but if you have javascript enabled you can now choose dps time instead. Calcing it off wws' dps time will result in higher tps figures, as you wont be penalized for periods of inactivity. This should allow more consistent comparison of tps between bosses, primarily with bosses where you cannot tank the entire time due to the encounter. for reference, wws uses dps time to calc thier dps numbers, and so do certain mods. hmmm....maybe dps time should be my default...