Get an Epic Experience with Premium

Skada Damage Meter

Combat Login to Add Favorites
  • World of Warcraft
  • 949,350 Monthly Downloads
  • Supports: 6.0.3
  • 11,225,450 Total Downloads
  • Updated 12/21/2014
  • Created 02/12/2009
  • 5,314 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: Public Domain
  • Newest File: 1.4-25
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".

r596 | zarnivoop | 2014-12-21 22:19:10 +0000 (Sun, 21 Dec 2014) | 1 line
Changed paths:
   A /tags/1.4-25 (from /trunk:595)

Tagging as 1.4-25
r595 | zarnivoop | 2014-12-21 21:31:37 +0000 (Sun, 21 Dec 2014) | 1 line
Changed paths:
   M /trunk/modules/Healing.lua

temporary fix for cases where spellname is null - unknown cause, though
r594 | oscarucb | 2014-12-15 13:25:45 +0000 (Mon, 15 Dec 2014) | 6 lines
Changed paths:
   M /trunk/modules/Deaths.lua

Fix the killing blow spell label added to the death summary screen in r591
Each deathlog is a circular queue prior to sorting (which for efficiency is intentionally delayed until deathlog:Update()), so on initial display of the summary screen, the prior algorithm was choosing an essentially random damage event from the log for the label.
Also for consistency, ensure we report the KB for the appropriate death, namely the one that is used to time sort the summary screen.
Finally, don't muddy the already-too-long detail title with the spellname, since that information is already obvious in the detail rows.

r593 | zarnivoop | 2014-12-14 15:19:59 +0000 (Sun, 14 Dec 2014) | 1 line
Changed paths:
   M /trunk/modules/Healing.lua

handle SPELL_ABSORBED in healing module (experimental)
r591 | zarnivoop | 2014-12-09 13:17:42 +0000 (Tue, 09 Dec 2014) | 1 line
Changed paths:
   M /trunk/modules/Deaths.lua

show last hit on deaths summary view
r590 | zarnivoop | 2014-12-06 13:24:07 +0000 (Sat, 06 Dec 2014) | 1 line
Changed paths:
   M /trunk/modules/Damage.lua

fix for arithmetic error on absorb
r589 | zarnivoop | 2014-12-05 21:15:11 +0000 (Fri, 05 Dec 2014) | 1 line
Changed paths:
   M /trunk/modules/Damage.lua

capitalize that function call, dude
r588 | zarnivoop | 2014-12-05 19:33:43 +0000 (Fri, 05 Dec 2014) | 1 line
Changed paths:
   M /trunk/modules/Damage.lua

fix for untested stuff
r587 | zarnivoop | 2014-12-05 18:13:51 +0000 (Fri, 05 Dec 2014) | 1 line
Changed paths:
   M /trunk/modules/Damage.lua

super-untested fix for spell_absorbed events (Ko'ragh)
r585 | zarnivoop | 2014-12-02 10:04:26 +0000 (Tue, 02 Dec 2014) | 1 line
Changed paths:
   M /trunk/Skada.lua
   M /trunk/modules/Damage.lua

fixes for "only keep boss segments" option, MS


First Previous Page 43 of 82 Next Last
  • #1091
    I can't find to se healing taken stats, is there anyway of doing this or something to add for the next version maybe? recount has it and it's imba, but I can't find it in Skada? Am I missing something?
  • #1103
    No, Skada has no Healing Taken mode. It would be fairly trivial to write one though. A guildie actually asked for it just the other day, so I may add one.
  • #1087
    Im getting the similiar to mkcorp.

    I used to use Recount, but switched to Skada since 4.1. However, Im finding that Skada maybe a stripped down version of Recount, therefore sharing the same problem. Both Recount and Skada just stop working. At the end of fights, the first 1 or 2 encounters are fine. After a bit, they BOTH do the same thing, fails to display anything after the encounter.

    The author for Recount is just a bad author for not letting people post comments and therefore IMO is an ass. This author for Skada, well, hes headed in the same direction. Quite a few posts about issues and he fails at acknowledging the users.

    Either authors need to acknowledge users, or just stop putting things out there!
  • #1089
    I've been using Skada for a while, and I have noticed an issue, it keeps de-selecting the display option I have selected, making it appear to not be working right. I'm not getting a lua error, so I am not sure why the settings aren't sticking, but since this is a new 4.1 feature its most likely something Blizzard did. You might look into your settings and see if they are displaying correctly.
  • #1088
    Since you are not making this addon and you are not paying for it. Since people take there time to do this and not get paid I thank them. If something doesnt work right now but it gets fixed I will be happy. Also DMG Meters are great to see were you are not needed to do the game.
  • #1086
    No matter what I do, still getting error:

    Date: 2011-05-16 12:23:06
    ID: -1
    Error occured in: Global
    Count: 1
    Message: ..\AddOns\SkadaDeaths\Deaths.lua line 44:
    attempt to index field '?' (a nil value)
    (tail call): ?
    (tail call): ?
    SkadaDeaths\Deaths.lua:58: func()
    Skada\Skada.lua:1762: ?()
    [string "safecall Dispatcher[13]"]:4:
    [string "safecall Dispatcher[13]"]:4
    [C]: ?
    [string "safecall Dispatcher[13]"]:13: ?()
    ...UD3\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()


    when I'll catch myself mouse-overing skada window during fight, errors similar to this one pop out:

    Date: 2011-05-16 18:09:57
    ID: 2
    Error occured in: Global
    Count: 2
    Message: ..\AddOns\SkadaDamage\Damage.lua line 272:
    attempt to index local 'player' (a nil value)
    (tail call): ?
    [C]: ?
    SkadaDamage\Damage.lua:272: Enter()
    Skada\Skada.lua:2220: AddSubviewToTooltip()
  • #1094
    I seam to only get this if I am rezed with Mass Resurrect


    find me on twitter @scotepi

  • #1085
    Problem found when cascading the bars above the title bar; if the raid has more than 5 people dealing damage the bottom 5 bars are displayed and I have to scroll up to see the top bars. This isn't problem for the damage meter but I also use Skada for threat now and I need to see the top bars. The only way round it is to displayed 40 bars but this can get messy.

    Despite this I much prefer it too recount, nice mod :)
  • #1084
    How to display the count of miss or parry of someone?
  • #1083
    Hi there,
    got an error for you.

    2x SkadaDeaths-1.0\Deaths.lua:44: attempt to index field '?' (a nil value)
    SkadaDeaths-1.0\Deaths.lua:58: in function `func'
    Skada-1.2-32\Skada.lua:1762: in function `?'
    CallbackHandler-1.0-6:147: in function

    : ?
    :"safecall Dispatcher[13]":13: in function `?'
    CallbackHandler-1.0-6:92: in function `Fire'
    AceEvent-3.0-3 (TomTom):120: in function
  • #1081
    Using 1.2-32, I'm getting this error when a battle rez happens. (The advice below to "reset data" doesn't help. This is a freshly reset Skada with every random pug, there is no preserved data. Certainly none from pre-4.1.)

    1x SkadaDeaths-1.0\Deaths.lua:44: attempt to index field '?' (a nil value)
    SkadaDeaths-1.0\Deaths.lua:58: in function `func'
    Skada-1.2-32\Skada.lua:1762: in function `?'
    CallbackHandler-1.0-6 (Ace3):147: in function

    : ?
    :"safecall Dispatcher[13]":13: in function `?'
    CallbackHandler-1.0-6 (Ace3):92: in function `Fire'
    AceEvent-3.0-3 (Ace3):120: in function

  • #1079
    Debuff uptimes is a nice plugin. would there be a buff uptime tracker as well?
  • #1077
    I have to disable it during raids otherwise I get 1 fps even when ppl are buffing.
  • #1078
    From time to time I get "paused" for several seconds, sometimes even disconnected. When Skada is disabled this doesn't happen. Occurs in 25man raids. :(
  • #1074
    First I have to say Skada is pretty awesome. Got it configured to show Threat, DPS, and Healing but I have a problem and it pertains to the DPS part of Skada. Now, if this question has been answered somewhere, I couldn't find it so please don't kill me :D That said: I've noticed that sometimes Skada will not...I guess read the combat log correctly. I was sitting on either Chimaron or Atramedes...maybe Magmaw but I noticed all the DPS was ~4.6k. ALL of them. Then other times the DPS is correct (values ranging between 20k+ and 8k). I've even tested this on the Raid Dummy. I can DPS it and show about 13k. I can then stop, wait a few seconds and start again OR I can tell Skada to reset. Either way it will then show DPS down (in the raid dummy's case about 5-6k). Is there something I need to set Skada to do or is this a bug? Other than that: Once again this is a VERY sweet add-on!
  • 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 »

Plantronics GameCom Commander Headset Giveaway!