Get an Epic Experience with Premium

Skada Damage Meter

Combat Login to Add Favorites
  • 122 Likes
  • World of Warcraft
  • 75,518 Monthly Downloads
  • Supports: 5.4.1
  • 7,915,240 Total Downloads
  • Updated 12/04/2013
  • Created 02/12/2009
  • 4,540 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: Public Domain
  • Newest File: 1.4-15
or
Support development! **
Donate

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 modes listed below are all separate addons. Only the modes you load adds to the memory and CPU cycles used.

Features:

  • 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.

Usage:

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. All suggestions and bug reports are very welcome.

"Skada" is Swedish for "Damage".

------------------------------------------------------------------------
r463 | funkydude | 2013-12-04 21:06:33 +0000 (Wed, 04 Dec 2013) | 1 line
Changed paths:
   A /tags/1.4-15 (from /trunk:462)

Tagging as 1.4-15
------------------------------------------------------------------------
r462 | funkydude | 2013-12-03 15:57:09 +0000 (Tue, 03 Dec 2013) | 1 line
Changed paths:
   M /trunk/Skada.lua

encounter start/end prep for 5.4.2
------------------------------------------------------------------------
r461 | funkydude | 2013-12-03 15:37:28 +0000 (Tue, 03 Dec 2013) | 1 line
Changed paths:
   M /trunk/Skada.lua

don't bother passing args from the handler, we don't use them.
------------------------------------------------------------------------
r460 | funkydude | 2013-12-03 13:29:16 +0000 (Tue, 03 Dec 2013) | 1 line
Changed paths:
   M /trunk/.pkgmeta
   M /trunk/Skada.lua
   M /trunk/embeds.xml

Replace AceEvent with our own handler, unregister the combat log event when appropriate.
------------------------------------------------------------------------
r459 | funkydude | 2013-11-28 14:53:42 +0000 (Thu, 28 Nov 2013) | 1 line
Changed paths:
   M /trunk/Skada.lua

bump to grab latest LSM.
------------------------------------------------------------------------
r458 | cremor | 2013-11-03 11:30:43 +0000 (Sun, 03 Nov 2013) | 1 line
Changed paths:
   M /trunk/Skada.lua

Fixed activating Skada after joining a group if "Hide when solo" is enabled and "Hide in PvP" is disabled (was broken in r445).
------------------------------------------------------------------------
r457 | zarnivoop | 2013-09-21 19:17:36 +0000 (Sat, 21 Sep 2013) | 1 line
Changed paths:
   M /trunk/modules/SkadaHealing/Healing.lua

format HPS according to chosen format
------------------------------------------------------------------------

Comments

First Previous Page 55 of 75 Next Last
  • #492
    I presume those are addon message channels, and not chat channels. If so, no, Skada can not use them. Skada can only report to the standard chat channels (party, guild, etc), and custom chat channels.
  • #489
    Perhaps im doing something wrong but here is my problem. The damage part of my skada meters does not work. i have it set up to only display the damage for the current fight but i get nothing. i have 2 separate windows 1 for threat (im a tank) and 1 for damage so i can keep a eye on the dps in the group. Every once in a while it will work but ill bet 90% of the time i get nothing. Any thoughts or ideas on how i can fix this?
  • #488
    First full test of Skada tonight, r287 (actually a week ago, but no author input on the WowAce forums where I originally posted this or the project tickets for a long time). Set it up, changed Data Segments to Keep slider to the max of 30, among other changes. Encountered a bug, a problem and two design issues.

    --Bug: when trying to access one of the options in the Dewdrop-like right-click menu out of combat (either from the LDB feed or via the "gear" icon on the title bar):

    ["message"] = "Skada-r287\\Skada.lua:308: attempt to index local 'mode' (a nil value)\nSkada-r287\\Skada.lua:326: in function `click'\nSkada-r287\\BarDisplay.lua:99: in function \nSkada-r287\\BarDisplay.lua:227: in function \n\nLocals:|r\nwin = {\n metadata = {\n }\n history = {\n }\n bargroup = SkadaBarWindowSkada {\n }\n display = {\n }\n usealt = true\n dataset = {\n }\n db = {\n }\n}\nid = \"total\"\nlabel = \"Total\"\nbutton = \"LeftButton\"\nmode = nil\nfind_mode = defined @Interface\\AddOns\\Skada\\Skada.lua:87\n\n ---",
    ["type"] = "error",
    ["session"] = 349,
    ["counter"] = 1,
    }, -- [149]

    Occurred once in the session, did not repeat. But the same error as the above has occurred regularly when accessing things through the options tooltip (deleting fight segments to make the tooltip smaller, etc.). So it was not a once-off problem.

    --Problem: after setting the maximum fight segments retained to 30, went into the Dewdrop-like menu to try to select one of them after combat. Only the first 10 or so segments were selectable, all the rest under the first 10 or so were grayed-out and not selectable.

    --Design issue 1: relating to the above, when that Dewdrop-like tooltip gets to be too large (as can happen when you choose to retain a large number of fight segments), it can become very difficult to access selections at the top (or bottom) of the tooltip. That is, until you move the LDB display or Skada title bar someplace else on your screen. Which is often a big hassle.

    For example, have the Skada title bar sitting at the center-right of your screen, with a LDB display feed for it in the to the top-right-center of your screen. In both cases when the tooltip is displayed with 30 fight segments, it extends and is cut off at the top of the screen. The selections at the top of the tooltip become become inaccessible.

    Thus you cannot choose "Damage" or similar from the selections near the top of the tooltip until you move one of the tooltip-spawners (title bar or LDB display) someplace on your screen where the tooltip is able to be displayed completely. Again, a hassle.

    To fix this (other than completely redesigning where to put those options), should add a scrollbar to the tooltip when someone chooses other than the default number of fight segments to show. As, for example, Broker_HitCrit has.

    --Design issue 2: The Absorbs and the Absorbs & Healing meters are great.

    One thing that is not as great as it could be, though. Unlike Recount and the rest of the meters in Skada is the lack of a "xPS" measure for those meters on the right of the bars. They only measure total absorbs/absorbs+healing. Would be nice to see a "xPS" measure as well for Absorbs and Absorbs & Healing.
  • #487
    Hi, is it intended that the threat meter does not display anything when I'm healing? I would like to see the threat meter when I'm leading raids. Am I overlooking something in the configuration menu?
  • #485
    Rogue vanishing mid-fight counts as a start of a new segment. So the meters at the end are not accurate in the sense that they are displaying the data for the last segment only (if set to "Last fight").
    Not sure if it works the same way for Feign Death, but it definitely poses a problem for rogues.
  • #486
    A little more on the issue:
    I have a single window set up to show DPS out of combat and switch to Threat otherwise.
    Since vanishing removes a rogue from the threat list, could it be that the described behaviour takes place only in this configuration?

    I will try to test it some time shortly.
  • #484
    For the love of God:
    - get pet/trap/snakes/firely/fart damage off my meters (put them with their owners)
    - When swapping between threat and damage/dps/healing/whatever, and you are in "grow up" configuration, have the meters display the top of the list, not the bottom.
  • #482
    I had been using Recount for a while; didn't like the massive amount of memory usage it caused - not to mention the DPS numbers being dead WRONG every time. Seriously, how do I get top damage but 8th DPS? A guild mate told me about Skada, so I downloaded it and tried it out.

    My favorite things:

    - It fits perfectly with my UI, unlike Recount. I had to manually go into the Lua code of recount and reprogram it to work with my current UI.
    - I've yet to see it anywhere near Recount's memory usage.
    - Far more intuitive menu navigation.

    However, when I tried to link the damage in chat today, I was a bit embarrassed. When I typed /skada report, it displayed the damage from the current fight. I tried to use the "mode" option by typing in "Overall," "Total," etc., but I couldn't figure it out. Because of the way I have my UI set up, I chose not to show the title bar, which means I'd use the slash command - yet I can't seem to make it work. Am I doing something wrong here?
  • #480
    I am having problems with Skada switching my settings from overall report to current fight. It will flip back and forth at times. When I open the skada menu the option to switch from current to overall, that bottom half is grayed out. What is causing this to happen?
  • #479
    Can you explain why Skada shows different results compared to Recount?

    Over the course of a 300 second testing period, Skada shows a 5% or more discrepancy in DPS alone, above Recount's. This may be attributed to using a different window of time to calculate average DPS, however, individual abilities are consistently reported as doing different amounts of damage which shouldn't be possible unless it's discarding information or simply not parsing it.
  • #493
    That reason for the discrepancy is simple: Recount is wrong about DPS almost 100% of the time.
  • #481
    For DPS, check the tooltip in the DPS mode. It will show the two variables, damage done and activity time. As for actual damage discrepancies, there should be none, other than what either meter measures is included in your test sample's window of time.
  • #498
    I'm not worried about the DPS number itself (I understand activity time and a host of other variables will always produce a different result). My issue is that either Recount or Skada will ALWAYS have different values for total damage.

    How is this possible? If I auto attack a training dummy for 300sec, there should be no question about how much actual damage I've done. Yet both mods record different numbers to the other. One of them has to be correct.
  • #477
    What happend with recount?
    i need a damage meter so i´l try this one instead..
  • #471
    Only thing that seems to work with the new update is threat. None of the other meters are working. any one have similar issues?
  • 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 »

The Sandbox: Godly Giveaway