Authors CurseForge

We have Recount and Skada, but they both behave more like a raid analyzer than a simple, pure damagemeter. What i would like to see is a ''reincarnation'' of Violation or a very similar type of damagemeter (http://www.wowinterface.com/downloads/info14412-FiendDamageMeters.html#info is also a Violation look-a-like, but also outdated and no longer maintained unfortunately).

I've been searching everywhere, and there aren't a single lightweight damagemeter that only shows damage/dps in simple bars instead of tracking loads of other information like misses/crits/abilities used etc. If anyone would like to start a project like this i'd be very happy, and i guess i'm not the only one.

I agree that there is definitely a niche in the market for just a straight up damage meter. It seems to me resurrecting Violation would be the easiest. I think Violation was great except that it didn't properly treat misses in its DPS formula. Aside that Violation really did fit the bill of a no-non-sense, give-me-bars-that-rank-accumulated-stats damage meter.

Violation actually should generally work fine except for minor adjustments if that.

There are some minor bugs like counting overkill as damage, so it wouldn't require that much to fix i guess. I'd do it myself if i had any experience in coding, but sadly i don't.

That's because of a blizz bug. All damage to target dummies is reported as overkill, which is why I don't know many addons that faithfully remove overkill damage. It's too much of a pain to write special code for target dummies and too many people tune their rotations on dummies, so generically overkill is left in (as it was before overkill was even reported).

I wouldn't consider that a flaw in Violation, but a flaw in the way Blizz implemented their target dummies/overkill reporting.

Violation also lacked the support of having several windows at once (one to show current damage, one to show total for example).

Quote from Seerah

(I still use Violation)

I am happy with just one window (who needs more to clutter your screen?) and just cycling through the reports.

How does it compare when comparing numbers with Skada and/or Recount? Also, Violation does not properly reset data between fights if you set up a window to show current damage done. The configurations you make are global, not per window. Violation also lacks the option to not record while not in a raid and it still uses Ace2.

Quote from Skylinee

We have Recount and Skada, but they both behave more like a raid analyzer than a simple, pure damagemeter. What i would like to see is a ''reincarnation'' of Violation or a very similar type of damagemeter (http://www.wowinterface.com/downloads/info14412-FiendDamageMeters.html#info is also a Violation look-a-like, but also outdated and no longer maintained unfortunately).

If you are happy with Skada, you can just disable all but the Damage module. It will not track (collect combat log events) for anything else then. If it is still too much you could make a stripped-down version of the Damage module, removing the bits you do not want.

Quote from Zarnivoop

If you are happy with Skada, you can just disable all but the Damage module. It will not track (collect combat log events) for anything else then. If it is still too much you could make a stripped-down version of the Damage module, removing the bits you do not want.

Yeah, i'm only using the Damage and Enemy module, though it would be perfect if i could disable the data collection of abilities used, amount of hits/crits etc.

Quote from Skylinee

Yeah, i'm only using the Damage and Enemy module, though it would be perfect if i could disable the data collection of abilities used, amount of hits/crits etc.

Those bits add very little to the event processing required, as it is all passed in one single event, which would need to be processed anyway. It does add to memory usage of course.

I was a bit bored at work so I butchered the Damage module. http://www.wowinterface.com/downloads/info15537-Minimaldamage.html

Thanks, i'll try it out at the next raid. Another thing i noticed though is that Skada uses around 600kb on login, with no reports saved or anything. What's causing this memory usage, as i have no fights saved? I noticed the memory gained a little bit after every update.

Quote from Skylinee

Thanks, i'll try it out at the next raid. Another thing i noticed though is that Skada uses around 600kb on login, with no reports saved or anything. What's causing this memory usage, as i have no fights saved? I noticed the memory gained a little bit after every update.

That memory usage is from the actual addon; basic functions, configuration, libraries, etc.

Quote from Zarnivoop

I was a bit bored at work so I butchered the Damage module. http://www.wowinterface.com/downloads/info15537-Minimaldamage.html

Working great, the damage module is using ~25kb instead of 1-2 MB like the standard one.

Quote from Skylinee

Working great, the damage module is using ~25kb instead of 1-2 MB like the standard one.

Does this module also include a DPS "frame" behind the damage displayed?

Quote from Mercu

Does this module also include a DPS "frame" behind the damage displayed?

Yeah, it shows damage done and dps in the bar, just like the normal module does. The exception is that it doesn't track any abilities used, how many crits you had etc, so you get no information on mouseover.

Loosk good so far, but is it right that Skada eats up the same memory amount as Recount if doing nothing? (1,3mb in my UI)

Quote from Mercu

Loosk good so far, but is it right that Skada eats up the same memory amount as Recount if doing nothing? (1,3mb in my UI)

No, Skada starts at 600kb when i clear everything and relog, though it climbs up to 1.3-1.4 after a few hours of combat.

Strange, I guess it happens due to Skada being my only Ace Addon in my UI.