What I would really like to see is that recount saves the color settings for each char and not global.
I'm not using the same UI for my different chars and so for my warlock I want to have a purple recount but for my shaman I'd like green windows.
Sorry, perhaps the request is a bit silly, but I like looks that fit together :)
@stan: I'm unable to reproduce the priest color problem. Can you kill your WTF/*/Recount.lua files and see if the problem persists?
@orson: Make sure that Show is checked for Self in the Filter settings.
@Baghwan: i'll see what I can do.
@nude: The problem is not bammod specific, any mod that uses parserlib but fails to have it in its "## OptionalDeps: ParserLib" will cause this problem. So look through your addon and check which use ParserLib, then check the addon.toc file and see if the optionaldeps are set correctly. If you find which one it was please post here so people don't have to do the same again! ;)
@Mindrila: Yep reworking the db is on my list already. I really think everything should be .profile. so each character can have their own, or two can share or everybody can have the same.
Ouch, alright I hope I can find a way to reproduce this one.
Edit: Did some streamlining of the color db code. Was a bit redundant (i.e. there was an entry both in char and profile dbs). Now there is only one entry. I hope as a side-effect it got that bug (I didn't find a way to reproduce it).
This mod looks great, but I am having an issue with conjured pets like water elems. Hunter pets seem to be merging fine, but I don't see pets like water elementals getting merged correctly.
Also, is this supposed to be able to sync with swstats? I thought I saw something somewhere
Summoned equal-named pets are a problem as they are all called the same, i.e. there is nothing in the combat log that differentiates them. The situation may improve with 2.4 when we get IDs rather than names - though, to be seen.
And Recount doesn't sync with anything but Recount.
Finally find the problem of the recount not working...
New recount has switched to libGraph-2.0 since 28th Jan, however my WAU doesn't download that library automatically. So I download it just now myself and the problem is solved...
@nude: Thanks for letting me know. It's odd actually because embedded or not embedded you should have gotten the lib. If you go with standalone libraries do you have "!!!StandaloneLibraries" installed?
Summoned equal-named pets are a problem as they are all called the same, i.e. there is nothing in the combat log that differentiates them. The situation may improve with 2.4 when we get IDs rather than names - though, to be seen.
And Recount doesn't sync with anything but Recount.
There has to be a way to do this, because SWStats does already.
SW Stat merges, but it knows it's flawed. Find what the [url=http://"[url]http://forums.sw-stats.com/viewtopic.php?t=323&highlight=water+elemental"]author[/url] had to say about it here[/url].
There is hope that 2.4 will allow us to do this properly, currently we can't, as said. If Blizz doesn't do the combat log as we hope we may be stuck with the situation we currently have.
And yes I still hope that they'll add originator data to effects, i.e. whose sheep got broken or who originally cast that lifebloom or earth shield.
With those two changes to the combatlog we could do most things that I can currently think of we can't do properly now, which is trace sources of combat-log entries properly (i.e. whose water elemental did that damage).
My wild guess (from [url=http://"[url]http://forums.worldofwarcraft.com/thread.html?topicId=2968233433&postId=35473184024&sid=1#102"]what[/url] Slouken wrote[/url]) we will be stuck with a suboptimal solution though and some effects will remain impossible to trace back to source reliably. Unless you agree that the warrior healed himself via earthshield and whoever cast it originally doesn't matter ;)
More info on 2.4 is coming in as we speak so soon we'll know a lot more about this.
Edit: Actually [url=http://"[url]http://forums.worldofwarcraft.com/thread.html?topicId=2968233433&sid=1&pageNo=10"]Slouken[/url] already answered the summoned pet question[/url] in a recent self-written Q&A:
Q: Why didn?t you include information about who owns <Summoned Pet Name Here>?
A: This was one we considered for a while, but decided to leave out for the sake of simplicity. We?re going to be watching how the new combat log plays out before adding new features or making additional changes.
Doesn't look like we get this with 2.4. It does sound like they are aware of this though and maybe we'll get it in a later patch, who knows...
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
on in-fight login.
Another bug is that Recount keeps resetting the color for "Priest" to a pink-ish Value. I change the color and it resets on /rl
/signed
I just click the Fubar plugin to show/hide... anything that can be removed from the window is welcome :)
The recount is not recording data, and instead, on all the bars, there is a "test" text on it.
And I don't have bammod installed..
What I would really like to see is that recount saves the color settings for each char and not global.
I'm not using the same UI for my different chars and so for my warlock I want to have a purple recount but for my shaman I'd like green windows.
Sorry, perhaps the request is a bit silly, but I like looks that fit together :)
@orson: Make sure that Show is checked for Self in the Filter settings.
@Baghwan: i'll see what I can do.
@nude: The problem is not bammod specific, any mod that uses parserlib but fails to have it in its "## OptionalDeps: ParserLib" will cause this problem. So look through your addon and check which use ParserLib, then check the addon.toc file and see if the optionaldeps are set correctly. If you find which one it was please post here so people don't have to do the same again! ;)
@Mindrila: Yep reworking the db is on my list already. I really think everything should be .profile. so each character can have their own, or two can share or everybody can have the same.
Nope, that fixed it.
@nude: Another thing: Make sure that all your addons use the latest parserlib too.
Well I was wrong...it lasted for one /rl but then it went back to pink :(
Edit: Did some streamlining of the color db code. Was a bit redundant (i.e. there was an entry both in char and profile dbs). Now there is only one entry. I hope as a side-effect it got that bug (I didn't find a way to reproduce it).
Also, is this supposed to be able to sync with swstats? I thought I saw something somewhere
And Recount doesn't sync with anything but Recount.
New recount has switched to libGraph-2.0 since 28th Jan, however my WAU doesn't download that library automatically. So I download it just now myself and the problem is solved...
Anyway, thank you Elsia for your great job :)
There has to be a way to do this, because SWStats does already.
There is hope that 2.4 will allow us to do this properly, currently we can't, as said. If Blizz doesn't do the combat log as we hope we may be stuck with the situation we currently have.
And yes I still hope that they'll add originator data to effects, i.e. whose sheep got broken or who originally cast that lifebloom or earth shield.
With those two changes to the combatlog we could do most things that I can currently think of we can't do properly now, which is trace sources of combat-log entries properly (i.e. whose water elemental did that damage).
My wild guess (from [url=http://"[url]http://forums.worldofwarcraft.com/thread.html?topicId=2968233433&postId=35473184024&sid=1#102"]what[/url] Slouken wrote[/url]) we will be stuck with a suboptimal solution though and some effects will remain impossible to trace back to source reliably. Unless you agree that the warrior healed himself via earthshield and whoever cast it originally doesn't matter ;)
More info on 2.4 is coming in as we speak so soon we'll know a lot more about this.
Edit: Actually [url=http://"[url]http://forums.worldofwarcraft.com/thread.html?topicId=2968233433&sid=1&pageNo=10"]Slouken[/url] already answered the summoned pet question[/url] in a recent self-written Q&A:
Doesn't look like we get this with 2.4. It does sound like they are aware of this though and maybe we'll get it in a later patch, who knows...