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.
I don't have access to an EQdkp site currently which makes this difficult to verify.
Also, I am digging for an EQdkp site I can play with to test some of these features. Anyone willing to hook me up with an admin account on an EQdkp site? I promise I won't break anything. :) If not, I'll see what I can do about setting an EQdkp setup locally.
http://www.wowace.com/projects/head-count/tickets/
I am looking for one or two additional developers to join me in addon maintenance as well as for feature development. The developer should preferably have previous experience with WoW lua addon development. Someone with a good base of coding/scripting experience in other languages may work as well. If interested, please send me a private message.
Once I hit level 80 (depending on my intensity level, this should occur within the next 1-2 weeks), I'll take a look at the addon to see what is involved in getting the existing feature-set to correctly work with the expansion. Until then, as bane32 mentioned in a previous comments, there is a fan update of the addon to get basic functionality working.
I am looking for another developer to contribute to HeadCount project for addon maintenance and feature development. This person would preferably have experience writing other lua addons for WoW. Someone with a base of coding/scripting experience in other languages with an enthusiasm for addon development or just HeadCount may work out also. :)
The official discussion thread
to get the file! Enjoy!
I really like this addon, but was thinking, what about combining it with recount so alot of info on the raid is gathered in one place?
Otherwise, nice work!
Any change it can import from another user?
It already has the export function so it would be nice to be able to pass the information of a raid to another player to maintain a master list of all guild raids.
Maybe even provide general statistical data, like how many raids per month/week, attedance % per player, etc.
Keep up the good work.
yeah I know about those zone-event-change-mod thing,very annoying ...we had the same problems when we made InstanceTime (http://www.curse.com/downloads/details/3699/). @ace: I'm on wau anyway...
@wishlist:
PassLoot: http://www.curse.com/downloads/details/4127/
Master Looter: http://www.curse.com/downloads/details/12830/
RemindMe: http://www.curse.com/downloads/details/12154/
including those three mods would be great^^
Essentially, what is occurring is that WoW sends event information that a zone change has occurred and states that you have exited a battleground via several notifications (for example, you are in Shattrath City and not in a PvP or Arena instance anymore), but still considers the previous battleground players in your raid. This is a concurrency event bug in Blizzard's WoW event code and is something the WoW developers need to manage and fix.
I wouldn't hold my breath regarding this fix, but I will try to look into it. I may be able to create a hack to get around this.
Altering the look and feel of HeadCount is on the wishlist, but is not planned in the near future. I am currently working on getting a loot management popup window feature as well as a rollcall feature to allow other players outside of the raid to whisper to be added into the wait list.
For the most recent development release, please visit:
http://files.wowace.com/HeadCount
For more information and current wish list items, please visit the HeadCount wiki page:
http://www.wowace.com/wiki/HeadCount
although bg-tracking is disabled alterac and arena are still often consired as raid,could you fix this ? and maybe an option to enlarge the window,it's pretty small...
Version 1.0.4 (74167 | seppyk | 2008-05-17)
* Initial code cleanup/refactoring.
* Fixed defect where UI frame was sometimes not refreshing after a loot query.
* Added toggle for battleground tracking.
* Added phpBB export (Credit: impish | nogudnik)
Version 1.0.3 (r73143 | seppyk | 2008-05-08)
* Added loot management (ability to set DKP cost per loot).
* Revised boss kill tracking for better accuracy.
* Made item icons slightly smaller in the raid loot UI frame.
* Loot icons or loot links can now be shift-clicked to link items in text chat.
* Added item level text to loot tooltip.
* Fixed a defect where an extra parameter was being passed to the raid tracker loot update.
* Fixed loot frame UI button hit coordinates.
Upcoming features:
* Loot source tracking
* Automatic raid group selection