Elsia, currently it's possible to disable recording depending on "zones" BGs, Arenas, instances and so on, would that be possible to also add an option to hide the window depending on the same thing ?
If i'm not recording/displaying datas, i don't need the window to be visible :)
And to add to that... why do I get the "do you want to reset" warning when I enter an arena where I'm not collecting any data? Well I know why (I entered a raid group), but it would be nice if you could check for the arena/bg option so that you could hide the dialog.
I don't understand why wow needs to save all gathered data once again if I just log in and log out without hitting anythng. It would be reasonable to save only the new data but I assume you can't change this by an addon...
I don't understand why wow needs to save all gathered data once again if I just log in and log out without hitting anythng. It would be reasonable to save only the new data but I assume you can't change this by an addon...
WoW doesn't save any data while it's running, only if you log out or quit the game. And it always saves the whole data of every addon, not only changed parts.
You can't change this behaviour with an addon.
Got a question regarding these check boxes...more specifically the last 3 (record time data, record deaths, record buffs/debuffs). What do they do? Whats the ungrouped and hostile boxes for, what data does it record? And the mobs section, does that just record data for the type of mobs? I'm just confused because it seems everyones recount info is ALWAYS different. Then I notice when I die on a boss fight, I won't even move on the damage meters. And after boss fights I'll notice peoples meters still moving. Just want to make sure I got the check boxes clicked that I need to have clicked to make sure the damage meter is taking data correctly, thanks.
@all: Added a "Hide when not collecting" toggle that will hide the main window for zone types for which we are not collecting (or when the global switch is turned off).
@Lind: Added that auto-delete per zone is only active if one collects data for the zone type one enters.
@nykspree:
From left to right:
*) Eyeball (Show) is show data collected for this combatant type
*) Paper folder (Collect) is collect standard (main bars, detail views) data for this combatant type
*) Watchclock (Time data) is collect time data for graph view (very memory intensive)
*) Skull (Death Log) is collect death log data
*) Axe (Buff/Debuff) is collect buf/debuff data, currently not implemented
Ungrouped is checked for Show but not Collect because you want to see former raid members after they leave raid.
If you see inconsistent data between recounts that can be due to various reasons. One is that there are still bugs ;) Another is that the inconsistency is with the data of people who do not themselves use recount, recount only syncs data from people who use recount. Third is that some recount users have turned sync on.
If you never look at the graph windows I recommend turning Watchclock off btw. It's just a lot of memory used that you never look at in this case.
I hate posting vague errors, but the screenshot one of the folks using my UI sent me isn't clear enough to make out completely. He has messages being spammed to guild and whispers to himself. I can't see much but I am able to make out the word "RECOUNT" in all caps at the beginning of the private messages (the guild spam doesn't appear to have it, but does conincide with the whispers and appears to be similar alpha-numeric strings. Have you seen a problem similar to this before and have any inight to it's cause? I'm inclined to think it's a localization issue or perhaps he updated some or all of the mods and goobered it up somehow.
@Lind: Added that auto-delete per zone is only active if one collects data for the zone type one enters.
I haven't tried this yet, but I see one problem right away. You also enter a raid group when you enter the BGs and Arenas, so that may still trigger the autoreset (unless you let the data collection check have priority... wasn't clear from your note since you only mention auto-delete per zone).
The way I see it noone really needs all these auto-delete features at once, either use the per zone in feature or the per join raid group one. They are both there so people can pick their preferred method. If you don't want deletion in BGs at all turn the join raid one off and use the zone one for your raid-auto-delete needs.
Same for the popup. There is a toggle there in case people always confirm deletion requests anyway and you'll never get bothered by a popup again.
@arkive: I had someone else report that they got addon message related bugs when guildies join wow. This is very peculiar because recount doesn't send addon messages to guild, it only sends to raid and via whisper. The whispers ought to only go to people in raid and not random guildies.
I don't experience these issues myself and would love to figure out what this is. Well it could be that in fact the guild ones are not recount (there should be a recount string showing up first for those).
I suspect that it's a generic problem somehow. Because addon channel messages simply shouldn't show in the chat window. Do you happen to have addonspamfu installed and have it report to chat or something?
P.S. Hmm saw this on the wiki API SendAddonMessage: "As of 2.1.0 whispers sent cross-server in battlefields will be sent as regular whispers and aren't hidden by the addon channel."
But this still doesn't explain why people see spam in the guild channel.
I'm back with the same problem. I can't reset the data. Every two or three logins I have to manually delete the lua files (Recount.lua and Recount.lua.bak) filed under account/realm/character. If I do not remove them, recount will hang. /recount reset or resetting by clicking the button won't work.
I'm on a Vista computer, don't know if that has something to do with it.
Can someone help with this very annoying problem? Thank you in advance.
I'm on a Vista computer, don't know if that has something to do with it.
Depends do you have WOW installed to your Progam Files folder ?
If so then you would effectively have 2 WTF folders - one in the wow folder the other in a user store folder. I would check the permissions on your WTF folder to make sure it isnt read only or something
This is a vague description of a supposedly bug, I hope its a bug tho.
I have a elem shaman which according to DrDamage should do about 1.4kdps in raids. Soloing she would do about 1.1k dps. This was about for a week ago true in recount too (slightly less as it should). However the last week w/o any gear/rotation changes shes doing about 200-300 dps lower, around 950 dps in raids and 750 soloing w/o buffs/totems where as it were 1kish before (DrDamage reports the same values). Before she was around 5th in damage. Now shes doing around 15th (last) on the same fights (Im rly throwing everything I got and burning pots as hell, which was not the case before). And its not that my guildies suddenly got better/gear. They have the same dps. I use wowaceupdter and update frequently. Im going to get a WWS log of 2nites fight (forgot on the last one).
As a followup to the randome guild/whisper messages, the user I mentioned posted this:
I refreshed all the addons via wau (Update all installed addons) and I still had the random text show up. After disabling the Threat-2.0 and LibHealComm-3.0 the random guild messages stopped.
I cracked open the Threat-2.0.lua file and I noticed something very interesting....
If you expand the photo in my thread alittle lower you will see guild message that contains "TL2!1^SR|^N73137^SThreat-2.0^N67545". Starting at line number 144 in the Threat-2.0 you will notice these lines:
starting at line number 36:
local LAST_BACKWARDS_COMPATIBLE_REVISION = 67545
all of these values are showing up in the guild messeges.
The whisper messages stopped for some reason whether recount was enabled or not. The only consistent messages left are the guild messages containing the HealComm and Threat-2.0.
EDIT:
I change the Threat-2.0 line to:
ThreatLib.prefix = "HAT"
ThreatLib.userAgent = "Threat-2.0"
and "HAT" was displayed in the guild message.
I hope this breadcrumb leads to something useful.
After further digging I came upon this chunk of code in the Threat-2.0.lua file starting on line # 201:
if IsInGuild() then
self:SendComm("GUILD", "REQUEST_CLIENT_INFO", self.MINOR_VERSION, self.userAgent, LAST_BACKWARDS_COMPATIBLE_REVISION)
end
Well commenting out that line seems to have fixed this guild message... I'll look and see If I can locate the one in the HealComm lib.
Hopefully this helps.
*Edit* I realize this places the blame on the libraries and not your addon, but I thought you might wanna know, and perhaps knew the next best course, or who to contact.
And to add to that... why do I get the "do you want to reset" warning when I enter an arena where I'm not collecting any data? Well I know why (I entered a raid group), but it would be nice if you could check for the arena/bg option so that you could hide the dialog.
WoW doesn't save any data while it's running, only if you log out or quit the game. And it always saves the whole data of every addon, not only changed parts.
You can't change this behaviour with an addon.
@Lind: Added that auto-delete per zone is only active if one collects data for the zone type one enters.
@nykspree:
From left to right:
*) Eyeball (Show) is show data collected for this combatant type
*) Paper folder (Collect) is collect standard (main bars, detail views) data for this combatant type
*) Watchclock (Time data) is collect time data for graph view (very memory intensive)
*) Skull (Death Log) is collect death log data
*) Axe (Buff/Debuff) is collect buf/debuff data, currently not implemented
Ungrouped is checked for Show but not Collect because you want to see former raid members after they leave raid.
If you see inconsistent data between recounts that can be due to various reasons. One is that there are still bugs ;) Another is that the inconsistency is with the data of people who do not themselves use recount, recount only syncs data from people who use recount. Third is that some recount users have turned sync on.
If you never look at the graph windows I recommend turning Watchclock off btw. It's just a lot of memory used that you never look at in this case.
I hate posting vague errors, but the screenshot one of the folks using my UI sent me isn't clear enough to make out completely. He has messages being spammed to guild and whispers to himself. I can't see much but I am able to make out the word "RECOUNT" in all caps at the beginning of the private messages (the guild spam doesn't appear to have it, but does conincide with the whispers and appears to be similar alpha-numeric strings. Have you seen a problem similar to this before and have any inight to it's cause? I'm inclined to think it's a localization issue or perhaps he updated some or all of the mods and goobered it up somehow.
I haven't tried this yet, but I see one problem right away. You also enter a raid group when you enter the BGs and Arenas, so that may still trigger the autoreset (unless you let the data collection check have priority... wasn't clear from your note since you only mention auto-delete per zone).
Same for the popup. There is a toggle there in case people always confirm deletion requests anyway and you'll never get bothered by a popup again.
I don't experience these issues myself and would love to figure out what this is. Well it could be that in fact the guild ones are not recount (there should be a recount string showing up first for those).
I suspect that it's a generic problem somehow. Because addon channel messages simply shouldn't show in the chat window. Do you happen to have addonspamfu installed and have it report to chat or something?
P.S. Hmm saw this on the wiki API SendAddonMessage: "As of 2.1.0 whispers sent cross-server in battlefields will be sent as regular whispers and aren't hidden by the addon channel."
But this still doesn't explain why people see spam in the guild channel.
I'm on a Vista computer, don't know if that has something to do with it.
Can someone help with this very annoying problem? Thank you in advance.
Depends do you have WOW installed to your Progam Files folder ?
If so then you would effectively have 2 WTF folders - one in the wow folder the other in a user store folder. I would check the permissions on your WTF folder to make sure it isnt read only or something
When I delete those files, nothing happens. They just go to trash bin... no big deal.
I knew about this problem prior to installing WoW. It is not installed under program files, but somewhere else...
This is a vague description of a supposedly bug, I hope its a bug tho.
I have a elem shaman which according to DrDamage should do about 1.4kdps in raids. Soloing she would do about 1.1k dps. This was about for a week ago true in recount too (slightly less as it should). However the last week w/o any gear/rotation changes shes doing about 200-300 dps lower, around 950 dps in raids and 750 soloing w/o buffs/totems where as it were 1kish before (DrDamage reports the same values). Before she was around 5th in damage. Now shes doing around 15th (last) on the same fights (Im rly throwing everything I got and burning pots as hell, which was not the case before). And its not that my guildies suddenly got better/gear. They have the same dps. I use wowaceupdter and update frequently. Im going to get a WWS log of 2nites fight (forgot on the last one).
As a followup to the randome guild/whisper messages, the user I mentioned posted this:
Hopefully this helps.
*Edit* I realize this places the blame on the libraries and not your addon, but I thought you might wanna know, and perhaps knew the next best course, or who to contact.
I commented out the following starting on line #1282
--if (IsInGuild()) then
-- commSend("999" .. tostring(MINOR_VERSION), "GUILD");
--end
I'll take a peak at the recount files later on tonight.
Klotus
@Moonfall: I meant why can't you delete in game. What happens if you hit the reset data button on recount?
Well, nothing happens. I hit yes, and the reset question box just stays on the same spot. When clicking on no, it does go away tho....
Well... cannot get bugsack to load.