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

Good to see progress on Recount 2.

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?

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.

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?

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.

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.

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

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.

Yep, many times. Nothin'.

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.