WowAce

They define what counts as being "in-combat" differently. Skada's numbers are more in-line with what you'd see on World of Logs.

Not sure if it's Skada or Recount that's bugged, They're not calculating the same damage on fights etc, 1 of them are not correct atleast. any tips of what it could be?

hey, can you add a dispels counter?

2x SkadaHealing-r407\Healing.lua:432: "<name>" expected near "local"

Removing the recently added "local" declaration fixes both errors and restores the two broken modes (Healing and Healing taken).. I don't know why they were added in the first place, you don't declare a variable initialized in a loop as local ever..

Its not specific to Skada. I get it all the time with various add ons. Just ignore and /rl and it fixes it.

From time to time, when I try to change my glyphs, the game says that Skada is bloking me from do çing it and needs to be disabled.  How do I fix that?

Been getting this since the last update.

105x Skada\Skada-1.4-4.lua:1816: attempt to concatenate field "playername" (a nil value)
Skada\Skada-1.4-4.lua:1816: in function "FixPets"
SkadaDamage-1.4-4\Damage-Damage.lua:118: in function "func"
Skada\Skada-1.4-4.lua:1417: in function <Skada\Skada.lua:1317>
<string>:"safecall Dispatcher[25]":4: in function <string>:"safecall Dispatcher[25]":4
<in C code>
<string>:"safecall Dispatcher[25]":13: in function "?"
Libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:91: in function "Fire"
Archy-1.8.37b\Libs\AceEvent-3.0\AceEvent-3.0-3.lua:120: in function <Archy\Libs\AceEvent-3.0\AceEvent-3.0.lua:119>

Locals:
nil

My Skada doesn't reset after joining a instance. I checked my configs (turned this option off and on) but it still dont work. Anybody same problem?

HOW DO YOU RELOAD IT ??? AS IT'S NOT SHOWING UP IN THE GAME, THOUGH IT IS ON MY CURSE CLIENT AND  IN THE ADDON SECTION OF THE CHAR LOADING SCREEN

Hey, am not sure why but Skada has stopped recording any sort of healing for me...not changed any of the configuration settings. (it records everything else)

Any idea what might be causing this? (Get no LUA errors either)

Cheers.

Hi, thanks for this great addon, just wondering why the 2nd line in skada has its bar pop out of the window often?

I have Skada in the bottom right corner of my screen.  Unfortunately The gryphons on the Blizzard UI cover it.  They didn;t used to cover Recount when I had it.  Is there anyway to resolve this?  I remember there used to be an option to remove the gryphons, but I am unable to find it anymore.  I would prefer Skada on top of the gryphons though.

THanks

Minor bug:  I keep Skada closed when solo, and the "Hide when solo" option checked.  But every time I take the portal from Stormwind to Jade Forest, it auto opens Skada. 

When killing some mobs in the Sumprushes in Townlong, something must've happened to set off Skada and it began tossing continual LUA errors. Looks like it has something to do with the Holy Paladin who was healing, perhaps, or the "Surrounding Mists" buff given in that area. Resetting Skada, and relogging and totally exiting WoW also did not stop these errors, and I think it might just be this location.

Message: Interface\AddOns\SkadaDeaths\Deaths.lua:98: attempt to concatenate a nil value
Time: 10/09/12 23:41:08
Count: 94
Stack: Interface\AddOns\SkadaDeaths\Deaths.lua:98: in function `func'
Interface\AddOns\Skada\Skada.lua:1417: in function <Interface\AddOns\Skada\Skada.lua:1317>
[string "safecall Dispatcher[19]"]:4: in function <[string "safecall Dispatcher[19]"]:4>
[C]: ?
[string "safecall Dispatcher[19]"]:13: in function `?'
...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: in function `Fire'
Interface\AddOns\Ace3\AceEvent-3.0\AceEvent-3.0.lua:120: in function <Interface\AddOns\Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>

Locals: timestamp = 1349844071.513
eventtype = "SPELL_PERIODIC_HEAL"
srcGUID = "0x0000000000000000"
srcName = nil
srcFlags = 1298
dstGUID = "0x06800000057D60B8"
dstFlags = 1298
spellId = 125668
spellName = "Surrounding Mist"
spellSchool = 1
samount = 0
soverhealing = 0
absorbed = 0
scritical = nil
(*temporary) = <function> defined @Interface\AddOns\SkadaDeaths\Deaths.lua:8
(*temporary) = <table> {
healingabsorbed = 0
dispells = 0
ccbreaks = 0
time = 0
interrupts = 0
damage = 512359
players = <table> {
}
deaths = 0
mobs = <table> {
}
shielding = 0
healing = 0
starttime = 1349844060
power = <table> {
}
overhealing = 0
name = "Current fight"
mobname = "Osul Mist-Shaman"
damagetaken = 11526
mobtaken = 512359
last_action = 1349844060
mobdone = 11526
}
(*temporary) = "0x06800000057D60B8"
(*temporary) = "Larrendias"
(*temporary) = 125668
(*temporary) = nil
(*temporary) = "'s Surrounding Mist"
(*temporary) = "Surrounding Mist"
(*temporary) = "attempt to concatenate a nil value"
Skada = <table> {
SetDefaultModuleLibraries = <function> defined @Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:383
displays = <table> {

Snipped some of it off since that error was pretty long.

since latest expansion I’ve had 2 problems with this addon, 1st off is that after every fight it auto toggles off unless I set it to hide during combat then it will appear after combat, also it will only display total damage, dps,hps and never current fight.

I have tried removing skada and deleting my WTF folder, neither made any difference.

Some errors.

3x Skada\Skada-1.4-3.lua:1816: attempt to concatenate field "playername" (a nil value)
Skada\Skada-1.4-3.lua:1816: in function "FixPets"
SkadaDamage-1.4-3\Damage-Damage.lua:118: in function "func"
Skada\Skada-1.4-3.lua:1417: in function <Skada\Skada.lua:1317>
<string>:"safecall Dispatcher[25]":4: in function <string>:"safecall Dispatcher[25]":4
<in C code>
<string>:"safecall Dispatcher[25]":13: in function "?"
Libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:91: in function "Fire"
Archy-1.8.31a\Libs\AceEvent-3.0\AceEvent-3.0-3.lua:120: in function <Archy\Libs\AceEvent-3.0\AceEvent-3.0.lua:119>

Locals:
nil

Great addon! But it could use a strata feature.

The damage module doesn't seem to be recording the damage caused by the Elemental Force weapon enchant, though it may just not be proccing.

It also seems to intermittantly miss the damage from Archimonde's Vengeance.