Recount - A Graphical Damage Meter/Raid Analysis Tool - Page 16

Borack · 06/28/07, 10:15 AM

Got another error last night after running Kara. No one could report "Overhealing". When anyone tried all it would do was print out the header "Repost Report for Overhealing" then pop out an error. I'm sorry, I don't recall the exact error, but can get it for you tonight. Several people had this problem.

In other news, the Poly breaker report is great! Could you add a Shackle/Trap breaker as well?

Iquark · 06/28/07, 10:46 AM

I'm having a rather strange reaction with recount and some other ace2 mod. Bug stack's error reports are as follows:

[2007/06/28 08:36:39-30-x1]: Recount\Recount_Modes.lua:154: attempt to index field '?' (a nil value)
AceAddon-2.0-40905 (Ace2):483: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:460>
<in C code>: ?
AceEvent-2.0-40601 (Ace2):269: in function `TriggerEvent'
AceEvent-2.0-40601 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>

[2007/06/28 08:36:48-30-x112]: Recount\Recount_Modes.lua:154: attempt to index field '?' (a nil value)

[2007/06/28 08:36:48-30-x18]: Recount\Recount_Modes.lua:359: attempt to index local 'data' (a nil value)
Recount\GUI_Main.lua:24: in function <Interface\AddOns\Recount\GUI_Main.lua:24>

These errors were from r-41840. Nothing shows up after loading except 5 different test bars, and a guildie who is running it is receiving the same errors. We both run a TON of ace mods, and another guildie who runs almost none is getting no errors.

We also get errors if we switch from externals to embedded libraries if that matters.

Hope this helps you out as we would really love to run recount as our main damage meter sometime soon!

EDIT: 1 more error showed up in bug sack while I was copying the previous ones into this post:

[2007/06/28 08:40:36-30-x408]: Recount\Recount.lua:695: bad argument #1 to 'pairs' (table expected, got nil)

Cryect · 06/28/07, 10:48 AM

Originally Posted by Dement

I've been slowly getting people to generate logs for use with WWS.

However, I've had a few people tell me enabling the combat log while using Recount led to some nasty problems that required them to remove/reinstall a lot of ACE stuff.

I personally don't use ACE (SWStats and WWS offline), but does using "\combatlog" mess this stuff up? I'm asking because more and more guildies are going to ACE (and Recount) and I don't want to cause any more headaches than needed...I just need their combat logs.

Is there a way to export combat logs from Recount?

Huh? Recount can't break /combatlog the only thing that evens touch/alters it is SWStats

Originally Posted by Borack

Got another error last night after running Kara. No one could report "Overhealing". When anyone tried all it would do was print out the header "Repost Report for Overhealing" then pop out an error. I'm sorry, I don't recall the exact error, but can get it for you tonight. Several people had this problem.

In other news, the Poly breaker report is great! Could you add a Shackle/Trap breaker as well?

Originally Posted by Iquark

I'm having a rather strange reaction with recount and some other ace2 mod. Bug stack's error reports are as follows:

[2007/06/28 08:36:39-30-x1]: Recount\Recount_Modes.lua:154: attempt to index field '?' (a nil value)
AceAddon-2.0-40905 (Ace2):483: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:460>
<in C code>: ?
AceEvent-2.0-40601 (Ace2):269: in function `TriggerEvent'
AceEvent-2.0-40601 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>

[2007/06/28 08:36:48-30-x112]: Recount\Recount_Modes.lua:154: attempt to index field '?' (a nil value)

[2007/06/28 08:36:48-30-x18]: Recount\Recount_Modes.lua:359: attempt to index local 'data' (a nil value)
Recount\GUI_Main.lua:24: in function <Interface\AddOns\Recount\GUI_Main.lua:24>

These errors were from r-41840. Nothing shows up after loading except 5 different test bars, and a guildie who is running it is receiving the same errors. We both run a TON of ace mods, and another guildie who runs almost none is getting no errors.

We also get errors if we switch from externals to embedded libraries if that matters.

Hope this helps you out as we would really love to run recount as our main damage meter sometime soon!

EDIT: 1 more error showed up in bug sack while I was copying the previous ones into this post:

[2007/06/28 08:40:36-30-x408]: Recount\Recount.lua:695: bad argument #1 to 'pairs' (table expected, got nil)

Argh, I've been having a hard time replicating these errors. Any idea what leads it from working to breaking? Also Poly Breaker tracks breaking of Frost Traps not sure if shackles were added or not to dispel messages but it will track them if they are now included (haven't had a chance to test them since no priest with shackle personally).

• frmorrison · 06/28/07, 11:32 AM

I get the same errors as Iquark when logging into WoW.

I assume it has something to do with the savedvariables (The 5 test bars is strange), I will delete the recount one later and see if that fixes anything.

Borack · 06/28/07, 11:37 AM

Originally Posted by Cryect

Argh, I've been having a hard time replicating these errors. Any idea what leads it from working to breaking? Also Poly Breaker tracks breaking of Frost Traps not sure if shackles were added or not to dispel messages but it will track them if they are now included (haven't had a chance to test them since no priest with shackle personally).

I'm not exactally sure about the Overhealing one. I just know about half way though the raid I tried to post them and they did not work, then at the end, a Paladin tried to post them and it didn't work. I'll get you a list of my addons and any other variables if that'll help?

Iquark · 06/28/07, 12:06 PM

Originally Posted by frmorrison

I get the same errors as Iquark when logging into WoW.

I assume it has something to do with the savedvariables (The 5 test bars is strange), I will delete the recount one later and see if that fixes anything.

I don't think it has anything to do with saved variables actually. Reasoning is that I had to get a BT attunement done for a guildie on Tuesday, and after copying my variables over to that account Recount ran just fine, no errors whatsoever.

I guess it's time to do an addon by addon test and find out where it is.

EDIT: After trying with various addon setups, from nothing but the libs that it needs, to installing it with externals, I still get errors. No idea here as to what in my setup is killing your addon, but hopefully soon it'll be fixed!

Phall · 06/28/07, 12:34 PM

I'm not sure this will help a whole lot because I didn't capture the error message verbatim. The error I got was that the global variable 'thr' was already in use. I run a number of Ace2 addons including Omen and BigWigs. The error popped up during first load and then again on first combat and then again on our first boss encounter. Recap appeared to be functioning correctly but Omen was not. After disabling Recap the error message went away and Omen returned to normal.

I will try to grab the error message when I get home and post it here as an update.

kharen · 06/28/07, 12:59 PM

I ran into the inability to report overhealing last night - just testing it now with the saved data (which was actually still there, cheers - could have sworn i'd tried toggling that option and it hadn't worked...), the error is: Interface\AddOns\Recount\GUI_Main.lua:617: bad argument #2 to 'format' (number expected, got string)

Dement · 06/28/07, 1:54 PM

Originally Posted by Brettness

I used both Recount and also parsed a combat log for WWS and I can say no problems at all occurred, and that no discrepancies occurred in the data between both of these. Not sure what your guildies are having problems with

.

How do you get your prsed combat log for WWS? Manually use \combatlog then process it with the WWS Client? Use a mod to automate starting it and stopping it?

Cryect · 06/28/07, 4:07 PM

Ah, thanks I know whats wrong now.

Added in the summary mode now (somewhat incomplete no tooltips, can't report, etc). On the detail window click the Magnification Icon (don't really like it but was best I could find in a few moments, open to other suggestions).

Borack · 06/28/07, 4:15 PM

Hey Cryect, just wondered if you had a chance to look at this:

Originally Posted by Borack

Just wanted to ask about something that I came across last night. I was trying to test out the Threat Meter portion of Recount with someone that did not have Recount, but had KTM. I had both KTM and Recount.

Now, the issue was this. She would show up on my Recount Threat Meter at first, but when we would change target, neither of us would. However, when I changed frames then back into the Threat Meter we would both show up again, even if it was mid fight. Is this an issue with KTM and Recount?

Thanks!

Amy I doing something wrong or is this something with KTM?

Cryect · 06/28/07, 4:18 PM

When you change threats there is no threat on the target is whats happening or I think whats happening. Threat tracks threat on multiple targets though I don't personally use Recount's threat window (I mainly use it for threat data in graphing).

You might want to check Omen instead for actual use as a threatmeter.

Borack · 06/28/07, 4:32 PM

It's more so that when we changed targets, no threat would register at all until you went out and back in on the frame. I was just hoping for an all in one solution to the meters and threat

Thanks for the response though!

Cryect · 06/28/07, 4:35 PM

Originally Posted by Borack

It's more so that when we changed targets, no threat would register at all until you went out and back in on the frame. I was just hoping for an all in one solution to the meters and threat

Thanks for the response though!

Strange, I will look into it just haven't tested it much as I said.

Papajan · 06/28/07, 5:05 PM

I know it's a little awkward (in the sense of replacing another mod), but any chance of conforming to Expiration's HP formatting on the saved combat log snippets for dying? Expiration places the HP at the beginning of the line (easy to glance at) and formats it by color, where 100% HP is one color (bright green I think) and the color fades to another color (red I think) as it goes to 0%. Having it formatted that way makes it really really easy to glance at which damage was the most significant. (Alternatively, if the HP wasn't colored but the damage was colored by how big it is, that'd help for glancing too. Or still alternatively since Expiration has custom filters, maybe if Recount used Expiration for those reports when it's available.)

Also, it's a little bit of a stretch, but would it be possible to have some very loose method to determine the killing blow and then report how much more HP you would've needed to survive it? I realize that it's something I can do manually, but it'd be wonderful to see at a glance that someone only needs to wear like 10 more stamina to not have died, or alternatively to see that no realistic amount of stamina would've helped and that they either had to avoid damage or healing needs to step up.

As for the icon for the detailed report, I think a snapshot of the damage type background would be easy to remember (sortof like a square rainbow icon with those colors)