Skada Damage Meter - WoW AddOns

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:

Skada Graphs: Adds graph display systems to Skada
SkadaScroll: Provides additional options for scrolling the bar displays
Skada Avoidance and Mitigation: Helps tanks benchmark their damage reduction performance via avoidance and mitigation
Skada for Tanks: Adds information useful for evaluating a tank's performance
SkadaEnsidiaFails: Display fails based on EnsidiaFails in Skada
Skada_FriendlyFire: Display friendly fire damage done by players
Skada Ability Tracker: Display abilities used and cooldown efficiency

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

You must login to post a comment. Don't have an account? Register to get one!

153 comments
← Previous
1
2
3
4
5
7
9
11
13
14
15
16
Next →

- Reply
- #146
lteke Feb 15, 2012 at 08:42 UTC - 0 likes
Death.lua line:94 typo?
- Reply
- #145
xingwang Jan 25, 2012 at 06:31 UTC - 0 likes
Thank you!

you can change under the following content?

Menus.lua

target = { "Whisper Target", "whisper"},->target = { L["Whisper Target"], "whisper"},

whisperbox:SetLabel("Whisper Target")-> whisperbox:SetLabel(L["Whisper Target"])

Add language file

L["Whisper Target"] = "密语目标"
- Reply
- #144
eridius Jan 25, 2012 at 03:48 UTC - 0 likes
@xingwang: Go

Sorry about that, looks like I missed the case of saved healing spells. Try r378.
- Reply
- #143
eridius Jan 25, 2012 at 02:38 UTC - 0 likes
@xingwang: Go

Are you still seeing this? I thought my commit 3 days ago would have fixed it.
- Reply
- #142
xingwang Jan 22, 2012 at 16:32 UTC - 0 likes
46x Skada-r376\modules\SkadaHealing\Healing.lua:50: attempt to perform arithmetic on field "absorbed" (a nil value) Skada-r376\modules\SkadaHealing\Healing.lua:50: in function <Skada\modules\SkadaHealing\Healing.lua:10> Skada-r376\modules\SkadaHealing\Healing.lua:81: in function "func" Skada\Skada-r376.lua:1402: in function <Skada\Skada.lua:1302> <string>:"safecall Dispatcher[19]":4: in function <string>:"safecall Dispatcher[19]":4 <in C code> <string>:"safecall Dispatcher[19]":13: in function "?" Libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:92: in function "Fire"
- Reply
- #141
angrysteel Jan 20, 2012 at 22:39 UTC - 0 likes
A: r375

4x SkadaHealing-r375\Healing.lua:50: attempt to perform arithmetic on field "absorbed" (a nil value)
SkadaHealing-r375\Healing.lua:50: in function <SkadaHealing\Healing.lua:10>
SkadaHealing-r375\Healing.lua:81: in function "func"
Skada\Skada-r375.lua:1402: in function <Skada\Skada.lua:1302>
<string>:"safecall Dispatcher[19]":4: in function <string>:"safecall Dispatcher[19]":4
<in C code>
<string>:"safecall Dispatcher[19]":13: in function "?"
Ace3-r1045\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:92: in function "Fire"
Ace3-r1045\AceEvent-3.0\AceEvent-3.0-3.lua:120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>

Locals:
nil
- Reply
- #140
rikscha Jan 16, 2012 at 05:26 UTC - 0 likes
Hi, is it possible, that i can change the option, so that i see in "dps at the moment" to see only the max DPS. That means i can change it so that i see only the highest DPS. My problem is i can't an won't see every timme to skada. Only after the fight i see to skada, but as firemage my dps is falling and get lower and i see no time, whats my highest dps. Ok i can show "dps for all" but thats not what i want. I need to see my highest dps at every fight.

Thanks
- Reply
- #139
heltonaugusto Dec 05, 2011 at 21:57 UTC - 0 likes
Missing

\locale\ptBR.lua

Last edited Dec 05, 2011 by heltonaugusto
- Reply
- #138
Zarnivoop Dec 03, 2011 at 13:39 UTC - 0 likes
@stencil: Go

Just found out the same thing after a lot of head-scratching. Notice how the combatlog you get from /combatlog does *not* reflect this change. Weird.

Commited a fix just now.
- Reply
- #137
stencil Dec 03, 2011 at 10:47 UTC - 0 likes
@ywfn: Go The cause of this error is a change Blizz made to the combat log event params passed for the _MISSED spell suffix. From: missType, amountMissed To: missType, isOffHand, amountMissed

So, no data would get collected for full resists. The one third of expected you're seeing is probably from partial resists. I've opened a ticket, #242 for this issue. Since the repository access type is open I also thought about checking in the fix, but thought that might a bit rude without asking permission first :)