Get an Epic Experience with Premium

Skada Damage Meter

Combat Login to Add Favorites
  • World of Warcraft
  • 793,267 Monthly Downloads
  • Supports: 6.0.3
  • 10,262,974 Total Downloads
  • Updated 11/11/2014
  • Created 02/12/2009
  • 5,122 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: Public Domain
  • Newest File: 1.4-22
Support development! **

About Skada Damage Meter

Skada is a modular damage meter with various viewing modes. It is inspired mainly by Assessment, but also by Recount.

Skada sports segmented fights and detailed views, while being highly efficient with memory. This is accomplished by aggregating data on fight segments.

Skada is entirely modular. The built-in modes can all be toggled on/off.


  • Automatic mode switching when entering combat. For example, you can have Threat mode be shown in combat. Skada can switch back after combat ends.
  • Specific fight segments can be kept indefinately.
  • Multiple windows. Each window can be configured fully.
  • Threat mode can warn on high threat.
  • Modes: Damage done, DPS, Threat, Enemy damage done, Enemy damage taken, Healing, Overhealing, Total healing, Absorbs estimated, Damage taken, Dispels, Mana regen, Debuff uptimes, and more.
  • Reports can be done everywhere. For example, you can report a certain player's Debuff uptimes.
  • Summary information for most modes (DPS, HPS, Fails, etc) in a LDB view/minimap button.
  • LDB data feed can show personal/raid DPS or personal threat.
  • Support for SharedMedia and Class Colors.

Skada is very easy to extend, and there are many "plug-in" addons out there that add functionality, such as:

There is a page with API information here.


Navigation in Skada is done by "drilling down" to the information you want. You go to a lower level, showing more detailed information, by clicking on it, and you go to a higher level by right-clicking.

The top level is the list of all saved fight segments. The second level is the list of all available data modes, such as Damage Done. The third level is one of these modes. Most modes let you drill down for further details. Some modes have several detailed views. In this case you choose alternate views by holding certain keys pressed while clicking. For example, in Damage mode, you can Shift-click a player to see what enemies the player caused damage to. Tooltips will display how to reach the different views.

You can also use window buttons for selecting fight segment and mode directly.

Scrolling in Skada is done with the mousewheel.

New Skada windows can be created from the configuration screen. Each window can be separately configured. A popular feature is "Mode switching", which lets Skada automatically switch to a specific mode on entering combat.

There is a forum thread for discussion on Skada.
Suggestions and bug reports here. Bug reports in comments will be deleted.

"Skada" is Swedish for "Damage".

r584 | funkydude | 2014-11-11 21:35:06 +0000 (Tue, 11 Nov 2014) | 1 line
Changed paths:
   A /tags/1.4-22 (from /trunk:583)

Tagging as 1.4-22
r583 | funkydude | 2014-11-11 21:32:37 +0000 (Tue, 11 Nov 2014) | 1 line
Changed paths:
   M /trunk/modules/Damage.lua

Damage: fix prismatic crystal guid format.
r582 | nebula169 | 2014-11-05 03:48:12 +0000 (Wed, 05 Nov 2014) | 1 line
Changed paths:
   M /trunk/Bindings.xml

only use one Binding header
r581 | funkydude | 2014-11-01 12:55:14 +0000 (Sat, 01 Nov 2014) | 1 line
Changed paths:
   M /trunk/Bindings.xml

Fix binding header.
r580 | nebula169 | 2014-11-01 08:02:03 +0000 (Sat, 01 Nov 2014) | 1 line
Changed paths:
   M /trunk/Bindings.xml

move keybinds to "AddOns" category
r579 | nebula169 | 2014-11-01 07:54:04 +0000 (Sat, 01 Nov 2014) | 1 line
Changed paths:
   M /trunk/Bindings.xml

move keybinds to "AddOns" category
r578 | zarnivoop | 2014-10-26 16:09:06 +0000 (Sun, 26 Oct 2014) | 1 line
Changed paths:
   M /trunk/modules/Damage.lua

count multistrikes separately (fixes #381)
r576 | oscarucb | 2014-10-19 20:41:02 +0000 (Sun, 19 Oct 2014) | 2 lines
Changed paths:
   M /trunk/modules/Damage.lua

tweak add_detail_bar to be less error-prone, fixing a bug introduced in r568

r575 | oscarucb | 2014-10-19 20:22:00 +0000 (Sun, 19 Oct 2014) | 2 lines
Changed paths:
   M /trunk/Skada.lua

ticket 377: avoid timeout errors in combat because GC can run too long

r574 | zarnivoop | 2014-10-19 20:19:10 +0000 (Sun, 19 Oct 2014) | 1 line
Changed paths:
   M /trunk/modules/Deaths.lua

don't choke on cleu multistrike parameter for misses
r573 | zarnivoop | 2014-10-19 20:17:40 +0000 (Sun, 19 Oct 2014) | 1 line
Changed paths:
   M /trunk/modules/DamageTaken.lua

test multistrike value for nil before doing arithmetic
r571 | funkydude | 2014-10-14 20:03:14 +0000 (Tue, 14 Oct 2014) | 1 line
Changed paths:
   M /trunk/Skada.toc

bump toc
r570 | nebula169 | 2014-08-08 18:38:16 +0000 (Fri, 08 Aug 2014) | 1 line
Changed paths:
   M /trunk/locale/enUS.lua
   M /trunk/modules/Damage.lua

WoD quick fix for Mage's Prismatic Crystal talent


First Previous Page 44 of 81 Next Last
  • #1056
    Update fixed the frame rate issues. But now it seems that pet damages is not being recorded? Neither my imp nor felhunter are included in my damage done.
  • #1064
    Not for me.
  • #1053
    4.1 seems to have broke the addon. Could anyone confirm or deny this?
  • #1055
    Change line 1661 in Skada.lua to this:

    function Skada:COMBAT_LOG_EVENT_UNFILTERED(event, timestamp, eventtype, hideCaster, srcGUID, srcName, srcFlags, dstGUID, dstName, dstFlags, ...)
  • #1057
    doesnt work.
  • #1054
    yep its broke
  • #1049
    Please fix the shadowy apparitions are not displaying to other people except their master shadowpriest!:(
  • #1048
    hi, is it possible to make skada able to view the spells that are interrupted? not just the number of interupts, but detail of who interrupted which spells.
  • #1047
    Is there any way I can link the damage meter numbers into chat without typing them?
  • #1046
    Healers badly need a damage meter that can parse damage-taken-per-second. In my experience, even if I'm blasting at full throughput and people are dying to threat loss - total damage taken won't provide useful information. The person taking unneccessary damage dies faster, so he might even wind up with LOWER overall damage taken.

    'lol no heals?' - flip to damage taken per second - You took an average of 11k DTPS. You're not the tank. My efficiency rotation does 6k. Please don't break aggro.

    Not a single damage meter has this option! recount comes close but only shows a real-time graph of raidwide dtps. All you'd have to do is add another mode that divides damage taken by the player's activity time. I know activity time is already recorded.

  • #1071
    A damage taken per second number has been added on the alpha version. Note that this is just as simple as Skada's "DPS" numbers. Activity time is simply first time action was done/taken until last action was done/taken. No arbitrary accounting for pausing in action.
  • #1050
    All you have to do in that case would be to look at the last 10 second report for their death in recount... if they're taking melee from the boss or damage from a mechanic they're failing to, it will show it.
  • #1051
    Looking back at the last 10 seconds of life after the fact is absolutely nothing like watching damage taken per second in real-time. You obviously didn't get what Zakaluka15 was talking about.
  • #1045
    Is there any way to pause data collection without disabling Skada completely and reloading the UI? When I am in really large battles in Tol Barad, for example, Skada impacts my framerate pretty severely. I have tried /skada toggle, and I have the option set which says data collection will be paused while hidden. This does hide the window, but Skada still collects data in the background. I can see that it did when I toggle it back on again later. I would prefer that Skada didn't collect any data at all when I do battleground PvP. Thanks in advance for help:)
  • #1044
    I fixed a bug with mode displays that contain icons:

    In the BarDisplay you kind of hack it and do:

    if icon then

    But what you should do is supersede and ShowIcon on the bargroup itself, so I modified the CreateBar function in BarDisplay with:

    if icon then
    if not window.bargroup:IsIconShown() then
    elseif window.bargroup:IsIconShown() then window.bargroup:HideIcon() end

    Which fixes the width bug (the bug is the bar hangs off by a width of the icon) in icon displays, so the former icon check is no longer needed.

    Hope this helps.
  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Win an Alienware Alpha!