It can mess up slightly in the multi priest situation because it assumes PoM's travels are instant but they aren't so depending on the distance it has to travel its possible who it really belongs to gets swapped with another one. This seems acceptable though and is in general an improvement over previous tracking.

I have the shared media libraries installed to gain access to more bar textures. I set it to Banto bar and it works just fine, but anytime I log out and back in, the texture resets to the default. I open options and check, but Banto is highlighted. I have to click on it again in order for the bars to change back to the selected texture.

Any idea what's causing this? Am I alone in this bar texture mishap?

To be clear. My arena team had 0 priests. I was seeing the debug messages for the opposing team's priest.

The way you are describing PoM seems good enough, especially since no syncing is required.

I used to have this problem as well, but it fixed itself recently. Not sure what the cause is.

The only thing I can think of is that your BantoBar texture doesn't get loaded until after Recount has loaded (Thus causing a reset to the default Blizzard bars), but that seems doubtful considering how many mods use BantoBar as default.

I've been running Recount side by side with a couple other damage meters and overall I have been pretty pleased. One thing I have noticed though is it does not appear to be parsing crushing blows. I use recap for combat statistics and when I pull up the details windows side by side Recount always has none for crushes.

Anybody else notice this? Using the latest version as of this post.

When the name of the mob extends underneath the buttons on the title bar, it becomes almost impossible to click on the buttons again to change views, reset data, etc etc.

Is there a way to make the Recount window wider?

I have played with the scale option, but i dont have a lot of vertical room where i want to put my recount window, was hoping that i could make it wider so text doesnt overlap etc and it isnt massively tall at the same time.

there used to be iirc, just wondering if it was taken out?

I am using Hawksey's latest version.

OK... I logged in and did a quick fight and really, really started poking around. And it looks like Recount does provide most of the data that Recap does. Much of my impression was because of the presentation.

For one, Recap shows all the details it can show, with zero or "-" entries where things don't apply. So you can see up front that it tracks things like the various Partial Resists and Missed Details, even if you haven't encountered all the possibilities.

Recount, on the other hand, doesn't show "Crushing Blows" in the details if you did not have any. Which is better, actually. (Does Recount track 25%, 50%, 75% partial resists?) But it does allow the (probabbly erroneout) impression that Recap tracks more.

Recap does have a more intermediate "Incomng/Outgoing/Misc" table that Recount does not, which provides nice color-coding and sub-totaling to give you a more at-a-glance view of each of these major categories, while Recount forces you to immediately jump down to particular areas (Damage In, Damage Out, Healing In, Healing Out). I like Recap a bit more on that one. Of course, Recount has graphs and Recap does not, so it evens out I guess.

Speaking of Miscellaneous, Recap can track all auras/buffs/debuffs/procs in its Misc page, and I don't see that Recount does anything similar. That would be on my wish list for Recount 2: a way to see what percentage of a fight my trinket's proc-chance-on-hit aura was active. And other misc procs and auras as well.

And Recap tracks intervals and durations for most events, too. So you can see how often you're Shredding, etc. I don't think Recount does this.

Anyhow, after comparing things closely, it looks like I'll stick with just Recount from now on, as it pretty much does everything except my trinket/proc curiosity. Thanks!

I've never seen a mod hog more memory than FuBar until I got Recount. GG?

Turn off the gathering of Time data?

Same here, and my system is best described as "not good". Recount uses a lot of memory because it stores a lot of data, but it doesn't use a lot of CPU time unless you go completely crazy on real-time graphs. In practice, CPU time is generally a lot more important to be optimized than memory is.