Cryect

Recount 2 like Recount 1 tries to innovate again in the means of stat tracking. Where Recount 1 was trying to innovate via graphs. Recount 2 instead tries to innovate by storing data similar to a database. This means instead of the fixed data views people are used to in combat stat addons; you are able to create your own views and perform drilldowns however you like.

Recount 2 is still not feature complete but I'm looking for feedback. Its been in development for a while due to my busy schedule so I'm unable to estimate when it should be ready for real use (started around 2.4 PTR). At the moment its not been ensured to work on 3.0 but will hopefully get to that shortly.

Recount2 - World of Warcraft - WowAce.com

To Do Still (Plus Many More):
-Selecting fight datasets
-Tracking stats only during combat
-Configure For How Recount 2 Looks
-Autodeleting/resetting/filtering of recorded data
-Syncing
-Polish
-Saving of Window Positions/Settings between sessions

Quick walkthrough on Recount 2.



These are the main windows which you display views on. You can create additional ones by using "/recount2 show". Right clicking on the title bar allows you to change the view, configure the views, or report the current view. Left clicking on bars lets you examine the details for what exactly makes up the number shown for that entry.



Here is the damage details in specific for the bar labeled Zulander. The detail window works through a drilldown technique where you select what you are grouping on by the buttons on the left side and then clicking on one of the bars. This brings up then a new section right below the previous one with you will notice the same buttons on the left minus the one that was selected from the previous one since you just drilled down on that grouping on the selected row. You can continue to drill down till there is only one button on the left side.



Here we have the main tab for configuring a view. The name entry is the label used for the window titles and selecting of the view. Bar value is the expression used to determine the width of the bar and sort. Left text is the label applied on the left side of the bar and right text same for the right side.

Expressions can use the below variables for the Bar Value.

cTotal - Total amount for the group
cCount - Number of entries for the group
cMin - Minimum number that matched the view for this group
cMax - Maximum number that matched the view for this group
cResist - Total resisted amount for this group
cAbsorb - Total absorbed amount for this group
cBlock - Total block amount for this group
cOver - Total overage amount for this group (at the moment only used for overheal but later for overkill)

For the tags in Left Text and Right Text the below variables are also available.

cName - Name for this group
cPos - Number in the sort
lTotal - The total amount of all the bars added up
lCount - The number of bars
lMaxValue - The value of the first bar

For GUID groupings you also get the below.

cClass
cRace
cClassification
cType
cFamily
cFaction
cSex
cLevel

Tags work by using square brackets "[]" then comma delimited expressions. If you want to format the expressions how they are displayed then use a ':' which lets you specify formatting same as string.format (basically printf from C). You can also add a $ right after the colon which means it goes right to string.format instead of doing a replacement with any nils it finds with '-' unfortunately if you have an expression that evaluates to nil while using ':$' then it will throw an exception (might change it to catch the error and then go through other code though).

Lua 5.1 Reference Manual
printf - C++ Reference



Here is the main filters that can be set for the view. You check the items you want it to track (if a column is completely unchecked its equivalent to checking all of them). So say you only cared about Crit & Crushing damage that is fire damage then you can check damage on the info filters, Crit/Crushing on the type filters, and fire on the school filters.



Here is the source/target filtering where you can restrict classes, races, or faction that is being displayed. Maybe you want to see only damage done by alliance against horde so would check Alliance on the source tab and Horde on the Target tab. There is several other potential filters that exist that haven't been added yet.



Here is where you select what you are grouping on. Normally you will be grouping on either Source/Target GUID but potentially you might be interested in consolidating all names together or grouping on class, ability or anything else available.

Anyways curious to see what people have to comment on the current version.

Recount2 - World of Warcraft - WowAce.com

I need to do something useless.

 

Andrast

Do you need anyone testing this on 3.0 (the beta more correctly)? I'm happy to provide feedback for this since this type of analysis tool is extremely useful for progression.

 

Xtek

Good to see progress on Recount 2.

 

Quaunaut

Noticing on the damage details page, I can't completely read between the two kinds of Windfury Attacks, and extending the window does not stretch the categories away from one another.

Randomly: Are those separations of MH or Offhand, or did I really forget to put WF on my weapons for that long?

 

Cryect

Hmmm, no idea on the difference between the two. I need to add resizing of columns I see.

Regarding 3.0 testing, I just need to login myself but mainly I'm looking for design issues and bugs that exist on live.

I need to do something useless.

 

Moogul

Finally a damage meter that can rank players on total damage dealt to Gnomes!

Looks great, I switched from recount to Assessment a while back, but since Assessment broke this looks like it should become my meter of choice again. I'll by trying it out tonight hopefully.

Ijago <Casual Jerks>

 

Malan

Based on the min/max/avg damages of the 2 WF entries I'd say that's exactly what it is. If he's using the new combat log spell IDs for the spell names, they can be distinguished by hand.

Has anyone tried this out on beta yet to see if it works?

Shitting up every single thread on EJ since '06

 

Arakan

Maybe a bit silly to suggest, but one thing a lot of people loved of Assessment was it's flat death list.

With flat death list I mean a encounter specific list of who died when, ordered by default first to last. Clicking on a name in the list resulted in a Grim Reaper like report, allowing you to quickly figure out why somebody died, and adjust accordingly.

With assessment being more or less discontinued at this time, Id love to see this feature implemented in a wellworking data tracking addon like Recount.

 

Malan

Also the ability to turn off tracking of anything you don't care to know about. ie, melee might want to turn off all calculations related to mana consumption, over heal, etc. By which I mean not just hiding the data, but actually turning it off so that we aren't using CPU time and memory to compute things we aren't interested in.

Shitting up every single thread on EJ since '06

 

Quaunaut

My biggest issue right now is that I just can't figure out how to limit my view. I really don't care how much damage the mobs I'm killing are doing ranked against my own party, and the config views aren't saving anything at all. But I don't think its implemented yet, right?

 

Malan

Doesn't seem to be able to filter out by group or solo either, its picking up everything around me.

Shitting up every single thread on EJ since '06

 

Cryect

Did you press Save?

Next feature I'm planning to add is filtering based on Self, Pet, Party, Raid, Others. After that will be looking at adding selecting the type of events you want processed (Damage, Healing, Misses, and Energy Gains for now) and then examining how to extend for interrupts.

I need to do something useless.

 

Quaunaut

Yep, many times. Nothin'.

 

Malan

I noticed yesterday that the size of the window seems to reset every time I login to the game, it isn't respecting the window size that I adjusted it to.

Shitting up every single thread on EJ since '06

 

Cryect

Window settings aren't saved at all. You will notice if you close it or happen to have multiple windows that those aren't respected either.

I need to do something useless.

 

Andrast

I did a ZA run with both Recount and Recount2 running and reset Recount2 at the start of the instance. Raw damage appeared very similar however it was disconcerting to see that the percentages were wildly different. It wasn't until later that I realised it wasn't filtering out all the damage that the mobs did to us and this skewed the percentage values.

I haven't tried it on the beta yet so I'm not sure if it works. Do you want that sort of feedback yet? Or are you slowly working on 3.0 compatibility?

 

Cryect

New Version up!

Editing Source/Target Filtering works now. Adds tracking of affiliation and reaction and can filter by them as well for the source/target.

Haven't gotten to 3.0 compatibility though will shortly but I know there is some issues.

I need to do something useless.

 

Mordekhuul

Cryect,

If you didn't already, would you consider adding a feature that allows Recount2 to tie in with BigWigs or some other source and automatically save off boss fight segments for later perusal?

This was my number one favorite feature in Assessment, and the only reason I resisted abandoning it for a good while, even after patch 2.4 broke most of its functionality.

I am now a Recount convert, but truly miss the ability to have boss fights saved for later perusal.

In an ideal world, configuration options would let you decide whether to save off every attempt, just the kills, the kills plus last few fights, etc. I'm sure you have a better idea how something like that could work than I do, with you the UI developer.

I can't wait to try out Recount2, regardless.

EDIT- To be clear, I am used to and do use Recount's current option to save only boss fights, but it is limited in that it both automatically saved every pull and only saves the last 4. One option to save every boss kill until manually deleted, and a second option on whether to save the failed pulls as well, would be amazing.

 

Cryect

I plan to have a feature like that at some point unknown when.

Just added prefiltering of events based on event type and affiliation.

I'm curious on CPU usage in a raid situation compared to Recount if anyone can get me some figures.

I need to do something useless.

 

Andrast

Did you want exact values (I shudder at running CPU profiling in raid) or more of a "It feels okay"

 

Cuer

To tie together requests listed above: is it eventually possible to store specific "boss fights" data, that can be shared around the raid after the fact? I really enjoyed using the original Recount, but had to eventually turn it off because I wasn't able to run it during laggy fights.

Basically, because I have a slower PC, I don't like running these sort of mods during fights. But I sometimes do like to look at the data after boss fight attempts. Ideally, it would be great if there was a way to run the addon in a "sleep mode", that pulled down data from other people in the raid only after combat is over, to allow perusal after a wipe and see just who did what.

 

Cryect

Heh, hoping for someone who has a beefy computer who could get some numbers in like a 10 man raid. I don't have time to raid myself really so unable to check myself. I believe it should be in general at least half the CPU usage of Recount 2 but its hard to tell if this will be true in a raid situation (though you can have it actually be higher if you had a lot of windows open to really large). You will also notice it uses absolutely nothing when nothing is going on unlike Recount.

Potentially eventually it will be possible to share fight data, but for now I'm not considering how to sync the data but I would like it to be able to possible to share a fight.

I need to do something useless.

 

Andrast

If I were to run karazhan/za would you want me to test with both Recount and Recount2 running and CPU profiling enabled and then give you the results? Or would you prefer a consecutive test?

Any tips on the methodology apart from enabling CPU Profiling and noting down values every so often?

 

Quaunaut

I should be able to get some data tomorrow night, if the raid doesn't cancel. It'll be from a 25 man though.

 

Kogayon

I have used Recount from the day it was launched.
I'm definitely gonna try this one. I'll report any "bug" i might encounter.

EDIT:
As I said I tested it and I'm still amazed (even if is not complete yet). The test was made on Brutallus.
First of all it uses about 25% of the memory Recount 1 use at the moment and this is a big step in my opinion. Apart from the way the data are collected and how you can customize it to do whatever you want to do, the memory usage is a strong point of this new recount version.
The way the whole addon behave is innovative. I guess it might need some small help section included (in the future). There might be confusions regarding the new Expressions for Texts and the GUID (something similar to CowTip help maybe).
One more new thing are the details structure and navigation and I love it, but are we going to be able to report those?

Overall this new version is great and i guess when the Lich King will be out we can fully use this new version.
Good luck and thank you.