A general heads up on feedback given the changes to wowace. I prefer all feedback to be posted in this thread. I'll try to turn off comments and tickets to all recount related projects that I am managing if that's possible.
In short, post your comments, feedbacks, bugs, hopes, wishes etc here!
Another thing, numerous people have asked me if there will be a 3.0.x Recount. The answer is that the current download is already 3.0.x ready (except for a TOC update) while still working with 2.4.x.
Ok i will apologise ahead if this comes out rude and abru
Ok i am now using the new and flashy Curse Client. Set it up and had it download Recount. I logged into wow and errors galore.
i check the .toc and i am using version r47214, which i no is not the latest version. i tried downloading r81954, but the client downloads r47214 which is .toc 20100.
Now i am not sure wat is going on there but could anyone please help. Hopefully i have posted this in the correct place.
Ok i will apologise ahead if this comes out rude and abru
Ok i am now using the new and flashy Curse Client. Set it up and had it download Recount. I logged into wow and errors galore.
i check the .toc and i am using version r47214, which i no is not the latest version. i tried downloading r81954, but the client downloads r47214 which is .toc 20100.
Now i am not sure wat is going on there but could anyone please help. Hopefully i have posted this in the correct place.
Short answer would be to ignore recount in the curse client 'till it gets worked out (there are a few versions it seems on curse.com and none that I can find at the moment is the newest version). Manually install the newest version from http://files.wowace.com/ before that page gets shut off (it's already locked and won't be getting any updates but is current as of a few days ago). Try updating again in a weeks time and hopefully by then all of the merging will be over and done with, especially on projects as popular as recount.
I assume what happens is that it grabs the original curse project, which is quite old and certainly not working anymore. I'll see what I can do to resolve this. To grab betas I'd recommend downloading manually as a few have suggested.
After a little hiatus, my Curse client isn't finding the Recount (Preservation) project any more - but I'm confused as to which is the current iteration of Recount - the "Recount" project or the "Recount2" project? If they are different, what is the real difference between the 2 projects?
Recount (Preservation) got renamed plain "Recount" on curse and will not syndicate from wowace. For people who are used to updating from curse that only means that you should get Recount instead of "Recount (Preservation)".
Recount 2 is a separate addon, a complete rewrite with completely different underbelly and likely somewhat different feature set. It's still very much in development. If you want to help test it, please grab and post feedback in the Recount 2 thread.
I know this is a noob question, but I am stumped. I like recounts layouts so much better then damagemeters but I can't seem to figure out how to get it to give me total damage done verses damage done current fight only. I rotate between those two settings often.
Can anyone tell me how to set it up to read current fight only?
Also, Elsia. Will you be putting in the ability to chose which data type to cycle through with the rotation arrows?
There is a small paperpage like icon in the toolbar on the window, click it then you get a dropdown where you can choose between all data and the recent X bossfights and/or the current fight.
Yeah as KnTrack has said there is a dropdown menu. Right-click the title text showing the current display mode and you get the list, which is a faster way to switch modes than paging. Also you can bind keys to display modes (via blizz standard keybind interface), so if you find yourself frequently toggling between 2-3 modes you can make that quicker that way.
I can't seem to get Broker_Recount to work with StatBlockCore, it doesn't throw me any errors either. I've tried removing the mods and adding it back in, tried with a fresh WTF, still nothing. What other steps should I look into?
Most versions of Recount shows up as ''Incompatible'' ingame, such as r901 and r931. Only non-incompatible versions are r81640 etc. Also getting some very different numbers from people running compatible versions vs my r931 version (healing on mine shows people with 2k+ healing per second, while they have around 900 on the compatible versions).
I've noticed something odd with Recount when using it in beta, occasionally it will seem to forget me and I won't show up on previous boss fights in the history.
I had an odd occurrence too. Last night i whispered a report to someone and it wasn't the same as the report on my monitor. :confused: The person number one disappeared entirely. The other whispers were fine and it didn't produce an error.
@Fire: I'll look into it. Last time I tried it worked fine for me.
@skylinee: I committed a version that should not have that problem.
@mikari, elvindiva: There are pathological situations where that can happen, it depends on your data collection filter settings. I hope to add a group-based filter eventually, but for now this should be rare and really shouldn't happen if the data collection filter settings are sensible. I.e. you should only ever lose combatants if your filter tells you that no data is collected where you are.
tl,dr: I'll look into a fix.
@all: A few updates regarding patch day:
1) Recount itself should be ready. I will commit a trimmed version after the patch day maddness is gone. Current version is beta vetted and should work well. There is some polish to be had, but nothing severely functional. Mostly 3.0.x allows optimizations that I'll fold in over time.
2) RecountThreat: I have an alpha that doesn't work well. I hope to get that one up as soon as possible. The old RecountThreat will break horribly, so if you get errors from it, disable it for now and watch here for an announcement that the new version is out.
3) RecountDeathTrack: Should work fine.
Edit:
4) Broker_Recount should work. Funky discontinued Statblocks v1.0 hence Statblocks_Recount is discontinued as well.
5) If there are issues with RecountFu bring it up with its maintainer! ;)
In short, post your comments, feedbacks, bugs, hopes, wishes etc here!
Ok i am now using the new and flashy Curse Client. Set it up and had it download Recount. I logged into wow and errors galore.
i check the .toc and i am using version r47214, which i no is not the latest version. i tried downloading r81954, but the client downloads r47214 which is .toc 20100.
Now i am not sure wat is going on there but could anyone please help. Hopefully i have posted this in the correct place.
Grab it manually from the projects page :)
-
View User Profile
-
View Posts
-
Send Message
Forum Moderatorto the toc?
thx :)
P.S: You can remove X-Embeds btw!
work just like KLH, or at least similar?
So, which is the "real" Recount project?
After a little hiatus, my Curse client isn't finding the Recount (Preservation) project any more - but I'm confused as to which is the current iteration of Recount - the "Recount" project or the "Recount2" project? If they are different, what is the real difference between the 2 projects?
Recount 2 is a separate addon, a complete rewrite with completely different underbelly and likely somewhat different feature set. It's still very much in development. If you want to help test it, please grab and post feedback in the Recount 2 thread.
Can anyone tell me how to set it up to read current fight only?
Also, Elsia. Will you be putting in the ability to chose which data type to cycle through with the rotation arrows?
@skylinee: I committed a version that should not have that problem.
@mikari, elvindiva: There are pathological situations where that can happen, it depends on your data collection filter settings. I hope to add a group-based filter eventually, but for now this should be rare and really shouldn't happen if the data collection filter settings are sensible. I.e. you should only ever lose combatants if your filter tells you that no data is collected where you are.
tl,dr: I'll look into a fix.
@all: A few updates regarding patch day:
1) Recount itself should be ready. I will commit a trimmed version after the patch day maddness is gone. Current version is beta vetted and should work well. There is some polish to be had, but nothing severely functional. Mostly 3.0.x allows optimizations that I'll fold in over time.
2) RecountThreat: I have an alpha that doesn't work well. I hope to get that one up as soon as possible. The old RecountThreat will break horribly, so if you get errors from it, disable it for now and watch here for an announcement that the new version is out.
3) RecountDeathTrack: Should work fine.
Edit:
4) Broker_Recount should work. Funky discontinued Statblocks v1.0 hence Statblocks_Recount is discontinued as well.
5) If there are issues with RecountFu bring it up with its maintainer! ;)