Skada Damage Meter
Skada is a modular damage meter with various viewing modes, segmented fights and customizable windows. It aims to be highly efficient with memory and CPU.
"Skada" is Swedish for "Damage".
Note: I took a tiny break from WoW (a decade), but recently started playing SoD. Be aware that this addon may not quite work yet.
Usage
When you first start using Skada, there will be a window created by default. This window can be extensively customized in Skada's configuration panel; click the little cog icon to access a menu, and then click Configure. Depending on your user interface, there may also be a minimap button allowing quick access to this menu.
Skada supports multiple windows. To create a new window, click Windows in the addon's configuration panel. There are three built-in types of windows - Bar, Inline, and Data text. Bar is the classic damage meter window, and is very customizable. Inline shows the meter in a horizontal line, which can be useful for integration in custom user interfaces. Data text shows just one item at a time, and can also be displayed by any LDB display addon, such as Titan Panel, ChocolateBar, or ElvUI.
In the normal Bar window, you can left click on specific items for more detailed information, and right click for less details. At the very "top" is the list of all saved fight segments. Some data modes have several detailed information 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.
Plugins
Skada is easy to extend, and there were once many extra plugin addons out there that add functionality. However, there are unlikely to be any maintained ones currently.
There is a page with API information here.
Reporting issues
For now use comments.
Ah, It is really hard for me to see. Since I usually have the window locked I didn't see it before. Thanks, that works wonderfully.
Same here took off every add on then started one by one and it is skada for me that is droping me down in fps in org the fair you name it
Missing
\locale\ptBR.lua
Same here. Was wondering which addon caused it, turned out to be Skada. Disabled it, went from 40 FPS to 60FPS capped in 5man combat, from 15-20 FPS in 25man raid combat to 35-40.
My fps was like 1-2 fps in LFR, but seemed fine elsewhere. Removed all my addons including skada and its much better now.
Yes, Morchok and on lootship.
Im sitting at 60FPS, then boom blood of the whatever on Morchok and FPS crushed to 1. Ive seen people DC too, but I guess my PC comes back to its senses somewhat quicker.
Anyone had severe fps drop in 4.3? I had mine drop from 50-60fps to 3-5fps on entering combat with Skada enabled. And I have the most recent Skada version 1.3-1.0. Disabling Skada solves the problem. Please fix. Meanwhile I'll take a look if the same occurs with Recount, thank you.
I've got the same problem. Was hoping the recent updates would've fixed this problem, but as of 15 minutes ago I'm still getting big FPS spikes with Skada upon entering raid combat.
Ok, I finaly made it myself. It's exact term is "Clamp to screen"
Modifying a library is involved, which I guess prevents the author of Skada to do it officialy.
Howerver this is how its done:
edit a file: ..\Skada\lib\SpecializedLibBars-1.0\SpecializedLibBars-1.0.lua
find: list:SetClampedToScreen(true)
change it to: list:SetClampedToScreen(false)
This will allow you to drag Skada window off screen
..working like a charm (and I'm happy again)
Sorry, but i'll insist :)
I'd really need to be able to move Skada window outside the visible area.
Opened a ticked @wowace - please everyone who would like to see this funtionallity to vote/bump the ticket up.
http://www.wowace.com/addons/skada/tickets/244-allowing-to-move-skada-window-outside-visible-area/
I've got the same issue. Would like to get some sort of feedback as to whether this issue is known and whether or not we'll see a fix. Thanks.
If you were using the "Save only boss segments" option, then this would indeed happen in Dragon Soul prior to the last release. It should now be fixed.
@stencil
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.
@ywfn 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 :)
I'm having the same issue. I can modify any/all settings and nothing happens. No data is being recorded that I can see.
Same for me.
You need to update the LibBossID library and it will start working properly again.
I manually installed the latest version (r74) of http://www.wowace.com/addons/libbossids-1-0/files/ and saving only boss segments works again.
Absorbs don't seem to be working too well currently in 4.3, with Skada 1.3-8. For a disc priest in our raid, Skada was only recording about 1/3 the raw amount of absorbs as compared to a WoL parse, and there was quite obviously a ton of absorbs missing when just looking at the breakdown by spell/player in Skada...as an example, a tank was shielded many times, but Skada recorded no absorbs at all on him for the disc priest. WoL's parse reflected it correctly, though.
2x SkadaDamage-1.0\Damage.lua:316: attempt to index local 'player' (a nil value)
Skada-1.3-8\Skada.lua:1913: in function `AddSubviewToTooltip'
Skada-1.3-8\BarDisplay.lua:145: in function <Skada\BarDisplay.lua:122>
Skada-1.3-8\BarDisplay.lua:251: in function <Skada\BarDisplay.lua:251>
@Zarnivoop
Afaik, it is its own event. Would it be just as simple as adding something like below to the SpellHeal() CL event (can't really say, I'll give it a try and see what happens ;p)