HeadCount
Overview
HeadCount is a configurable World of Warcraft add-on that automatically tracks raid attendance, loot, and boss kills.
HeadCount answers the following questions:
- How long is a player active in a raid?
- How long is a player on standby for a raid?
- How long is a player offline during a given raid?
- What loot dropped during a raid and who received it?
- What boss kills occurred during a given raid and who was there for the kill?
Downloads
Curse
http://wow.curse.com/downloads/wow-ad.../head-count.aspx
WoW Interface
http://www.wowinterface.com/downloads/info8867-HeadCount.html...
WoW Ui
http://wowui.worldofwar.net/?p=mod&m=6819
Information
HeadCount forum thread: http://forums.wowace.com/showthread.php?t=12225...
Project page: http://www.wowace.com/projects/head-count/
Wish list
All defects and enhancement requests (wish list) items can be filed and/or reviewed on the HeadCount work ticket page:
http://www.wowace.com/projects/head-c.../tickets/
Features
Raids
- Raid creation: Automatically creates a new raid as you join or start a raid.
- Raid finalization: Automatically ends an existing raid as you leave a raid.
- Raid management: The user can end raids, remove raids, or remove all raids on demand.
- Raid zone tracking: Zone name are automatically added to raids as you zone into a raid instance for the first time.
Player attendance
- Player tracking: Players are tracked based on their timed participation in the raid. Players can be tracked based on configurable raid groups for raid list activity (active raiding players) and wait list players (queue/standby players).
- Player removal: The user can remove tracked information for specific players on demand.
- Player history: View specific player history for a raid to see how and when a player moved from activity to standby to offline and back during a raid.
- No list tracking: Players can be tracked as non-raid list and non-standby players as needed. Players that go offline are automatically taken out of the raid and wait list groups for tracking purposes.
- Integrated wait list: Receive whispers from members outside of the raid group in order to track them.
Boss kills
- Boss kill tracking: Tracks the world bosses killed during the course of a raid and the raid list members present for the kill.
- Boss kill removal: The user can remove tracked boss kills on demand.
- Manual boss kill: The user can add a boss kill to the current raid at the current time with the current roster via /hc boss add [bossname]
Loot
- Loot tracking: Tracks loot received during a raid based on configurable item level quality (default: Epic item level or higher)
- Loot removal: The user can remove specific pieces of loot on demand.
- Loot exclusion: The user can manage loot exclusion which will prevent certain pieces of loot from being tracked during a raid. (e.g. - Emblem of Valor)
Export
- Export: Users can export current raid attendance and received loot information to one of a number of formats (CSV, XML, Text, EQdkp XML string, phpBB forum post, phpBB with ItemStats forum post).
Reporting
- Boss kill broadcast: The user can optionally broadcast when the raid kills a boss to a configurable chat channel.
- Loot broadcast: The user can optionally broadcast when a player receives a valid piece of loot to a configurable chat channel.
Performance
- Fault tolerance: If the mod owner quits WoW, restarts WoW, or reloads their UI during a raid and returns to the game, HeadCount will attempt to gracefully recover from the outage to continue tracking the active raid.
- Attendance delay: Configure how often HeadCount should manage attendance updates to increase or decrease performance and/or accuracy.
Sorry man, but there is nothing you can do if you don't have a backup of your WTF folder.
Anyway I appreciate the reply and the empathy. Forgive me, but I am not too programmer savvy. Are you saying I corrupted the file by letting it get too big and so WoW's solution to that was to just dump it all? If I have it right, then why doesn't either WoW or HC warn you before that happens? Could make a few ppl's lives a bit easier.... just a thought.
We want a way of tracking 'when' the last time a person attended a raid was (we often have low signups but pug people out of /g). We reset loot positions on members that haven't attended raid in 10+ weeks.
Does this addon track AFK's? we have some members that seem to think its OK to vanish between bosses, but without evidence of how long specific members spend not at the keyboards it proves a bit difficult to chastise and punish.
Tracking raid attendance should be done on some kind of external source. Headcount really is designed to integrate well with several web-based systems that do a fantastic job of keeping track of all this.
Headcount does not track AFKs at the moment, but that is something I would like to add myself so once many of the other pressing issues are handled, I will look into that.
1. Manual control over it creating raids, as you end the active one and the next one starts it's a fiddle deleting the extra ones later.
2. We are using guildlaunch.com for our site hosting and whilst we can import an eqDKP log it doesn't work brilliantly (their issue I believe) so an export for Guild Launch would be awesome, although unlikley.
Anyway great work I plan on using this for a long time to come.
2) Something to hope for in the future if Blizzard decides to stop breaking Headcount every time they release a new wing or new patch :)
3x HeadCount-1.7.3\HeadCountFrames.lua:2065: attempt to index field '?' (a nil value) <string>:"*:OnEnter":1: in function <[string "*:OnEnter"]:1>
Locals: self = HeadCountFrameContentWaitListButton { 0 = <userdata> } motion = true
In zhTW WOW. Could I manul fix time and join person?
Thank you!
However, we manage this from the website. EQDKP Plus has the ability to define aliases. This way when someone logs on and off his/her main and bevy of alts, it knows to assign DKP and attendance to the main as defined on the website.
Any solution for this?
Everyone that is in the waitlist is not getting credit. I think the main problem is that there is no “End run time” in the waitlist. If I looked at the times, there is only the “Start Run”, but there is no “End Run time”, that’s why I guess it doesn’t take into account those people in the total time.
Just as a note, if I want the total time (Raid+waitlist) I chose the following options:
• “Date and Time” -> “Time Options”: I clicked everything there (Raid List Time, Wait List Time, Offline Time).
• “Bosses” -> “Group Management” : I clicked everything there (Raid List Time, Wait List Time, Offline Time, No list time).
Is it correct?
I can paste one log here (or somewhere else) if you want to take a look.
thanks!