SWstats is just a huge memory leak. The functions are awesome, but whenever using it, my memory used goes from 35 to about 40-42 and increases more and more with that 'saving old data' function. I like it better then good old damagemeters, but as most instances are already eating my fps alive these days, I can't really justify using it.
If you're looking to catch slackers, it doesn't really matter what damage meter you use. Either way, the players with the lowest damage/healing done are the slackers.
That's the more noobish thing it could possibly be said about damage/healing done.
Ok, maybe dps-ers with CC don't have to fall too much in the ladder cuz of the time "lost" on CCs, but damage output need to be considered togheter with the class max possible dps. I mean, i am shadowpriest and i usually do great in 5 man teams (usually 2nd in damage), but i presume in 10/25 man raid shadowpriest dps is not going to be one of the best in standard fights (with multiple non-aoeable mobs i think we can do great btw).
Also i would like to let u notice that if any "backup healer" switch to dps to healing mode on just a boss he will surely lose A LOT of positions in the DPS' ladder.
The worst part of ur sentence is the one concerning the healing done... i've raided up to AQ40 pre tbc, always as healing priest. Most of the time i was on top of the healing meter, but that did not mean anything. Considering hots canceling each other, overheal, main targets (if u r not random healing), etc. healing meter is totaly worthless (except for really evident slackers... but if u r not random healing than u'll spot them anyway cuz their targets will die really often if no one helps.
Considering an "healing ladder" to find who's good and who's not will only lead to wasting mana.
There will always be a "last in damage/healing" cuz the number of dps-ers/healers is finite. Last don't need to be equal to slacker.
Perhaps Renaldo worded it out a bit wrong (or simply forgot to add "pontial" on front of "slackers"), but I think you're somewhat missing his point. I think he's saying that the difference between various damagemeters (or combat loggers, if you will) is minimal for most of the users.
Ofcourse in many cases something important might not be presented fully in the statistic, and for those cases it's important for you to understand the encounter and the role each person is playing there. Like you said it's quite common for someone to be simply channeling and cancelling heals to quickly react to burst in that particular fight. However I hardly see a problem asking "Hey, McHealington, howcome you're always so low on effective healing" and then hearing "Well, I need to keep on channeling highrank Gheal here because occasionally the boss bursts tank down really low, and those are the REALLY important moments on this fight, so having me cover them is vital".
It's not "noobish" to read data from a fight. It's noobish to be ignorant slave to it perhaps, but surely we can respect eachother enough to not suspect such things of eachother here?
Ignoring the value of tracking statistics because they may be misinterprated is the real problem with how people view damage tracking addons. The "winners" of the damage meters are the people who have used the data gathered on a boss encounter to better understand what seperates the people at the top from the people at the bottom and how to improve either their own or the raids output, be it through group synergy, consumables, or innate class characteristics.
My combat log settings are at 2000 yards (I think DamageMeters did this, if I set it to 200 it gets put back to 2000). But all my meters still fail to get data from about 2/3 of the players I encounter. Its been like this since WoW 2.0. I can be standing on top of a mage and near a target, and get absolutely zero data bout them, yet still get all the data from the tank. I get data from almost all druids and priests, and almost never any at all from mages, hunters, and rogues.
Has anyone else seen this?
This happens with both SWStats and DamageMeters (I have not tried recap).
SWStats is nice, but does not show fight-by-fight dps in real-time which is critical for assessing my own performance on the fly. Well it can for raid-wide dps but who cares, I need per person dps per combat interval.
Last edited by TheOnly : 04/16/07 at 1:31 PM.
Reason: Added which meters are affected
I've thought about trying to work out a marginal value system for players (or "contribution" or "attributable damage" or whatever you like to call it) but the logic seems to be fairly complex. This obviously wouldn't be for the catching slackers type of situation but more for the "what happened when we added a shaman to group 2?" type of scenario. The reverse of the process (What was Rogue_003's un-modded dps?) would however be extremely useful for comparative evaluation over the present system of "well, hunter_001 had a spriest and a fury warrior so sure he's ahead of hunter_002 who is in group five spamming misdirection".
I like post-fight analysis tools and the more information the better. Even a barebones framework that posted buffs with uptime, non-dps activities and so on would be quite nice.
EDIT: Obviously this goes beyond the information available from the combatlog alone, which is a large part of why I abandoned the concept early on. Another issue that seems to crop up more for me lately though is lines of information that are just plain MIA from the combatlog. It seems that there is some throttling going on which causes some rare dataloss and while that's no huge issue statistically over a long fight, it plays absolute havoc with conditional logic for events.