Yeah, the tanks auto-seating in siege engines part kind of gets me... What if the tank's average iLvl is the highest in the raid? Wouldn't you want that scaling going to a demolisher for rolling pyrite stacks? I know I've done it for that very reason a few times when we're running alts and such, or running with lesser geared guild members.
Hmm... From that link, I'm not quite sure how I feel about that yet. Please tell me it will be an optional module that can be disabled without having to manually alter or delete files...?
Not that I'm saying the idea above was good or bad, just interesting. But just to play a little devil's advocate, his idea seems like more of just a aggregate overview of all the data Recount is offering. I.E.: another "tool" built on top of the "tool" you already admit Recount is. Things like DamageMeters/Recount/Skada/Assessment/etc. are directly responsible for people requesting "link dmg meters" after every boss to see where their epeen lies in the first place.
Abuse of the system doesn't mean there's no merit in his idea to me, whether I'd decide to try it or not myself.
Sounds interesting, to say the least. Just curious for tanks, how you'd handle that "subtract damage taken" being a... penalty, for lack of a better word? Makes sense for DPS to be judged in that regard if they're, say, pulling aggro and getting face-smashed, but as a tank, that's part of our job (getting face-smashed). :P
Yeah, at this time, I think this was a false alarm. Likely ue to the current Curse Client not handling disembedded libraries properly in the latest builds. Went back later and picked up the missing libraries, and seemed to be working after that from a very quick test.
Newest ZOMGBuffs release seems to be generating an error upon login with Skinner. Sorry, I have no further details to provide at the moment, as I was just on for a short time to check mail, and forgot to copy the error message.
I seem to recall, at least, the people in cannons for the siege engines showing this issue. Unless I unmerged the pets, I usually wouldn't see the data from people manning the cannons. I'm in the process of moving, so likely not going to get a chance to test this myself further for another week or so, to make sure my memory of it is indeed correct. :P
The latest Skinner and Recount don't seem to be interacting together, the close button and the title aren't in-line with the other buttons.
Probably, in part, due to the recent addition of being able to hide the close button that changed something. Hiding the close button also seems to cause the rightmost button hang outside of the frame slightly now.
There used to be a discrepancy between what the shaman saw and other party members saw. Party members would only see damage of 1 spirit wolf, or 1 treant. So ideally someone who sees the shaman installs the beta and checks if the damage recorded for the wolves/treants matches that of the shaman/druid.
Thanks!
Hm.. so that would explain the big dicrepancy in numbers between my enhance shaman and a guildie's moonkin druid numbers between our reports from a recent H-HoL run. I'm not usually one to mess with alphas, but will mention the possible fix in guild and maybe get a couple more bodies (including myself) to run some further comparisons with the alpha. For that run in question, there was around a 600dps difference in the report for her moonkin for the fight vs. what my list showed. It will be interesting to see how much closer this brings the 2 reports.
The "memory allocation error: block too big" errors/crashes are a known and long-standing problem with CowTip. There are dozens of threads about this problem, dating back well over a year. The solution has generally been "switch to another tooltip addon".
CowTip apparently wasn't the only one triggering it, because I used to see this as well (as I've stated before) and never touched CowTip. /shrug
0
/shrug
0
0
0
Abuse of the system doesn't mean there's no merit in his idea to me, whether I'd decide to try it or not myself.
0
0
0
0
0
0
Probably, in part, due to the recent addition of being able to hide the close button that changed something. Hiding the close button also seems to cause the rightmost button hang outside of the frame slightly now.
0
0
Hm.. so that would explain the big dicrepancy in numbers between my enhance shaman and a guildie's moonkin druid numbers between our reports from a recent H-HoL run. I'm not usually one to mess with alphas, but will mention the possible fix in guild and maybe get a couple more bodies (including myself) to run some further comparisons with the alpha. For that run in question, there was around a 600dps difference in the report for her moonkin for the fight vs. what my list showed. It will be interesting to see how much closer this brings the 2 reports.
0
0
CowTip apparently wasn't the only one triggering it, because I used to see this as well (as I've stated before) and never touched CowTip. /shrug
0