I'm not seeing any boss kills in the reports anymore; are they still working for anyone else? I believe they were showing up in version 1.07, but they haven't in 1.08 or 1.09. Headcount just doesn't seem to recognize any boss kills.
On a related note, if this is a common problem, what about using the same boss recognition (or at least falling back on it) as BigWigs? BigWigs already does all the boss detection, and knows when a boss is successfully killed; perhaps it would be possible to hook onto that for logging bosses, for people who are running BigWigs.
I've come across some interesting behavior in the HeadCount2 addon, that I actually saw previously mentioned in a thread but I never saw a resolution or fix posted.
The issue that I'm having is that when I log on and start a raid (or even without a raid started) Headcount doesn't seem to be available. If I go to Interfaces > Headcount2 the only thing I see available is the "Debug" checkbox. However, if I log off this particular character and swap to another account (same computer & WoW installation) Headcount2 is there (skull icon, Enable Minimap Icon checkbox, frames with options, et cetera).
What would be preventing me from accessing Headcount2 from one account but not the other, as they both reference the same WoW and WoW Interfaces folder? The toon I want to access this from but can't happens to be the guild leader/raid leader toon, thus the need for Headcount2 on this particular toon. Let me know what I might need to delete, modify or provide and I'll be happy to assist (I'm relatively computer competent if you need something specific).
I can't maintain this addon, but I did make it work with mists. All I did was a search and replace. If something is broken beyond that then we're out of luck till someone comes along to really work on it.
Unpack these files into the root of your headcount2 folder found in interface/addons.
Was there an option added to record 5-mans in Headcount2? And, if so, can it be disabled? Last night, after we finished our raid, I disbanded the raid, logged out and back in (to close wowcombatlog.txt), and then went on a 5 man. Headcount2 activated to record the 5-man information as a new raid, which it had never done before and surprised me. The 5-man was only ever a party, we never switched it to raid.
I doubt any new features are being added to headcount, but some things.
Once in a while headcount2 causes a lot of fps lag, not sure why.
Easier to use. When you want to display the queue you have to go into the addon pulldown menu's. Same with announceing queue.
These things should also be done thru whisper command. So you could /w <player> wl waitlist. This would show the waitlist.
/w <player> wl shout. This would tell people to queue.
I figure these two should be really easy to do by the author.
The lua errors were reported on curseforge and curse.com where the addon is found.
Also be nice if the addon tracked loot thru news. Since all loot is reported there and all it has to do is pull the loot from there and check to see if the player is in the raid. This way you don't have to be a close to the looter to track loot.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
On a related note, if this is a common problem, what about using the same boss recognition (or at least falling back on it) as BigWigs? BigWigs already does all the boss detection, and knows when a boss is successfully killed; perhaps it would be possible to hook onto that for logging bosses, for people who are running BigWigs.
I get an error every time i log into the game
HC2 looks like an ideal addon for us. Perhaps anyone could let me know if it's project is still alive?
thanks :)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNope. Thanks for that i forgot completely :-)
I've come across some interesting behavior in the HeadCount2 addon, that I actually saw previously mentioned in a thread but I never saw a resolution or fix posted.
The issue that I'm having is that when I log on and start a raid (or even without a raid started) Headcount doesn't seem to be available. If I go to Interfaces > Headcount2 the only thing I see available is the "Debug" checkbox. However, if I log off this particular character and swap to another account (same computer & WoW installation) Headcount2 is there (skull icon, Enable Minimap Icon checkbox, frames with options, et cetera).
What would be preventing me from accessing Headcount2 from one account but not the other, as they both reference the same WoW and WoW Interfaces folder? The toon I want to access this from but can't happens to be the guild leader/raid leader toon, thus the need for Headcount2 on this particular toon. Let me know what I might need to delete, modify or provide and I'll be happy to assist (I'm relatively computer competent if you need something specific).
I wonder if this addon is abandoned or will update ?
Thanks
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumUnpack these files into the root of your headcount2 folder found in interface/addons.
I've got some chatter fixes to get done first
Thank you so much, Kagaro! My entire guild depends on HeadCount2; we would be nowhere without your awesome addons!!
Looking forward to the update :)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI am using 1.12 as distributed by Curse.com.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOnce in a while headcount2 causes a lot of fps lag, not sure why.
Easier to use. When you want to display the queue you have to go into the addon pulldown menu's. Same with announceing queue.
These things should also be done thru whisper command. So you could /w <player> wl waitlist. This would show the waitlist.
/w <player> wl shout. This would tell people to queue.
I figure these two should be really easy to do by the author.
The lua errors were reported on curseforge and curse.com where the addon is found.
Also be nice if the addon tracked loot thru news. Since all loot is reported there and all it has to do is pull the loot from there and check to see if the player is in the raid. This way you don't have to be a close to the looter to track loot.