HeadCount

Table of Contents

This project is abandoned and its default file will likely not work with the most recent version of World of Warcraft. Whether this project is out of date or its author has marked it as abandoned, this project is no longer maintained.

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

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.

Comments

_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#61 _ForgeUser724295

View User Profile

Send Message

Posted Jan 8, 2009
Thanks. The waitlist feature is scheduled for the 1.5.0 milestone. For more information on the tentative feature or for any comments:

http://www.wowace.com/projects/head-count/tickets/4-waitlist-management/

Rollback Post to Revision RollBack
_ForgeUser375785
- Join Date: 11/17/2007
- Posts: 0
- Member Details
#60 _ForgeUser375785

View User Profile

Send Message

Posted Jan 7, 2009
Hi!
This Addon is very good.
Please, I want Item loot in CSV format.
good luck.

Rollback Post to Revision RollBack
_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#63 _ForgeUser724295

View User Profile

Send Message

Posted Jan 8, 2009
The CSV format needs to be reworked entirely to add more information. The problem is that the CSV format is a rather limited one. I'll make a note to investigate this.

Rollback Post to Revision RollBack
_ForgeUser164584
- Join Date: 12/12/2006
- Posts: 3
- Member Details
#59 _ForgeUser164584

View User Profile

Send Message

Posted Jan 7, 2009
Is there anyway you could an "Add Loot" Feature for example if you miss loot or out of range when the item was looted?

Rollback Post to Revision RollBack
_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#62 _ForgeUser724295

View User Profile

Send Message

Posted Jan 8, 2009
This is in the works for the 1.5.0 milestone:

http://www.wowace.com/projects/head-count/tickets/13-manual-loot-addition/

Rollback Post to Revision RollBack
_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#58 _ForgeUser724295

View User Profile

Send Message

Posted Jan 6, 2009
Curse uploading/file synchronization is currently broken. The latest version of the addon is available for download. When Curse fixes their issue, the download will also be present on this page. Until then, download locations for HeadCount 1.3.9:

Latest stable and beta releases: http://www.wowace.com/projects/head-count/files/

WoW Interface: http://www.wowinterface.com/downloads/info8867-HeadCount.html#changelog

Version 1.3.9
* Added automatic group selection.
* Added note field under loot management.
* Added pruning feature to automatically delete old raids.
* Refactored localized resource bundle tables into constants.
* Fixed mismatched tags for phpBB export strings.

Some good features added to the most recent stable (1.3.9)...

1. Automatic group selection - Raid list and wait list groups will be automatically selected upon zoning into a supported raid instance. This configuration option is enabled by default. Users may disable the option via the configuration menu.

Examples:
Naxxramas: Raid list (1 and 2), Wait list (3 - 8)
Naxxramas (Heroic): Raid list (1 - 5), Wait list (6 - 8)

2. Loot note - Addon users can write small notes per piece of loot distributed. This information is included in the export strings.

3. Raid pruning - HeadCount will automatically delete raids older than a configurable amount of time. This configuration option is disabled by default, but can be enabled if desired. Automatic pruning (deletion) of old raids will only occur on startup of the addon for precautionary reasons. Please use with caution so you do not accidentally remove old data. When enabled, HeadCount will automatically delete all raids older than 12 weeks (approximately 3 months).

Rollback Post to Revision RollBack
_ForgeUser50246
- Join Date: 11/17/2005
- Posts: 0
- Member Details
#54 _ForgeUser50246

View User Profile

Send Message

Posted Dec 30, 2008
Does HeadCount include any sort of logging for failed attempts? Our points system awards points for attempts as well as kill, instead of time spent in the raid. I can't find it if there is.

Rollback Post to Revision RollBack
_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#55 _ForgeUser724295

View User Profile

Send Message

Posted Jan 1, 2009
No, HeadCount currently does not track boss wipes/attempts. It is possible to track this given the current implementation, but there is no current timetable in regards to this feature.

I am guessing the general idea is similar to a boss kill? Log the boss on a wipe and all who were in attendance for the wipe?

Rollback Post to Revision RollBack
_ForgeUser50246
- Join Date: 11/17/2005
- Posts: 0
- Member Details
#56 _ForgeUser50246

View User Profile

Send Message

Posted Jan 1, 2009
Correct. Is there any way of taking a "snapshot" of the raid for failed attempts so I can log it that way? Or is there a better workaround?

Rollback Post to Revision RollBack
_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#57 _ForgeUser724295

View User Profile

Send Message

Posted Jan 3, 2009
There's currently no workaround for this. I am almost done with the 1.4.0 milestone changes. After that, I'm going to see if I can finally get the integrated waitlist feature working. Once that's complete, I'll see what can be done in regards to event tracking which will cover a number of interesting features.

* Rollcall snapshot events - User can manually start an attendance rollcall to track attendance at periodic intervals.

* Boss kill rollcall - Addon can automatically take an attendance rollcall after boss kills to allow for users outside of the raid list groups to get credit for being in attendance for a boss kill.

* Boss wipes - Addon can automatically record attendees for a boss wipe. This would be similar in functionality to the boss kill tracking as it stands now.

I'm going to have to make this all configurable because event tracking can add an enormous amount of data beyond what is already tracked. I don't have a time frame for this type of feature, but I have already started work on the infrastructure underneath it.

Rollback Post to Revision RollBack
_ForgeUser984346
- Join Date: 7/27/2008
- Posts: 0
- Member Details
#52 _ForgeUser984346

View User Profile

Send Message

Posted Dec 29, 2008
I'm having a small issue with the XML export that I wasn't having with the previous version. There is an error with the xml each time it exports, it's missing a = in the first line. I can fix this in the code pretty easily but thought I would report so that you can get it corrected.

Awesome addon, we use it daily.

Rollback Post to Revision RollBack
_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#53 _ForgeUser724295

View User Profile

Send Message

Posted Dec 30, 2008
This issue is resolved in the latest version of HeadCount, 1.3.6 which is available for download.

Rollback Post to Revision RollBack
_ForgeUser159367
- Join Date: 12/10/2006
- Posts: 0
- Member Details
#50 _ForgeUser159367

View User Profile

Send Message

Posted Dec 28, 2008
The raids I am tracking are way too long. for instance the last raid I tracked was showing up as ending the next day, 11 hours later, when in all reality the raid was about 3 hours total. Is this something wrong I'm doing on my end, or is this a bug?

Rollback Post to Revision RollBack
_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#51 _ForgeUser724295

View User Profile

Send Message

Posted Dec 29, 2008
It sounds like you are bumping into the recovery system that is implemented. If you logoff/quit/crash WoW while in a raid, then rejoin WoW, HeadCount will attempt to recover the active raid at the time in order to continue tracking data.

This seems like the most likely culprit.

1. Player joins evening-based raid.
2. Raid leader calls the raid for the night.
3. Player logs off/quits WoW before actually leaving the raid.
4. Player relogs the next morning and last night's raid is still active due to recovery.

Leave the raid group once the raid is complete to end tracking for that raid.

Rollback Post to Revision RollBack
_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#49 _ForgeUser724295

View User Profile

Send Message

Posted Dec 23, 2008
Version 1.3.6
* Added cost label to phpBB export strings.
* Added difficulty label option for EQdkp export strings.
* Fixed defect in XML export where equals sign was missing from version attribute.
* Fixed missing battleground tracking configuration option.
* Fixed missing attendance delay configuration option.
* Fixed defect where 12-hour time formats were causing a nil error.

Rollback Post to Revision RollBack
Dariss
- Location: Anchorage
- Join Date: 12/23/2006
- Posts: 0
- Member Details
#46 Dariss

View User Profile

Send Message

Posted Dec 21, 2008
Error i receive immediately after logging in, while in a raid in 10 man naxx.

[2008/12/21 14:34:54-3609-x1]: HeadCount-1.3.4\HeadCountUtil.lua:92: attempt to index global 'displayDateTime' (a nil value)

---

When i click on the skull to open up the frame:
[2008/12/21 14:36:08-3609-x1]: HeadCount-1.3.4\HeadCountUtil.lua:92: attempt to index global 'displayDateTime' (a nil value)
HeadCount-1.3.4\HeadCountUtil.lua:66: in function `getDateTimeAsString'
HeadCount-1.3.4\RaidTracker.lua:732: in function `processAttendance'
HeadCount-1.3.4\HeadCount.lua:205: in function `RAID_ROSTER_UPDATE'
HeadCount-1.3.4\HeadCount.lua:467: in function `OnClick'
FuBarPlugin-2.0-90006:975: in function <...s\HeadCount\libs\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:972>

---

And the Others came consecutively, and dont really know what caused them.

[2008/12/21 14:36:41-3609-x1]: HeadCount-1.3.4\HeadCountUtil.lua:92: attempt to index global 'displayDateTime' (a nil value)
HeadCount-1.3.4\HeadCountUtil.lua:66: in function `getDateTimeAsString'
HeadCount-1.3.4\RaidTracker.lua:732: in function `processAttendance'
HeadCount-1.3.4\HeadCount.lua:191: in function `RAID_ROSTER_UPDATE'
HeadCount-1.3.4\HeadCountOptions.lua:358: in function `func'
Dewdrop-2.0-90320 (BugSack):732: in function <...face\AddOns\BugSack\Libs\Dewdrop-2.0\Dewdrop-2.0.lua:671>

---

[2008/12/21 14:36:41-3609-x1]: HeadCount-1.3.4\HeadCountUtil.lua:92: attempt to index global 'displayDateTime' (a nil value)
HeadCount-1.3.4\HeadCountUtil.lua:66: in function `getDateTimeAsString'
HeadCount-1.3.4\HeadCountFrames.lua:301: in function `HeadCountFrameRaidHistoryContentScroll_Update'
<string>:"*:OnShow":1: in function <[string "*:OnShow"]:1>
<in C code>: in function `Show'
HeadCount-1.3.4\HeadCountFrames.lua:120: in function `ShowUserInterface'
HeadCount-1.3.4\HeadCountFrames.lua:129: in function `ToggleUserInterface'
HeadCount-1.3.4\HeadCountOptions.lua:361: in function `func'
Dewdrop-2.0-90320 (BugSack):732: in function <...face\AddOns\BugSack\Libs\Dewdrop-2.0\Dewdrop-2.0.lua:671>

---
[2008/12/21 14:36:44-3609-x1]: HeadCount-1.3.4\HeadCountUtil.lua:92: attempt to index global 'displayDateTime' (a nil value)
HeadCount-1.3.4\HeadCountUtil.lua:66: in function `getDateTimeAsString'
HeadCount-1.3.4\HeadCountFrames.lua:977: in function `HeadCountFrameConfirm_Show'
HeadCount-1.3.4\HeadCountFrames.lua:1174: in function `HeadCountFrameRaidHistoryEndRaidButton_Click'
<string>:"*:OnClick":1: in function <[string "*:OnClick"]:1>

---

Rollback Post to Revision RollBack
Dariss
- Location: Anchorage
- Join Date: 12/23/2006
- Posts: 0
- Member Details
#47 Dariss

View User Profile

Send Message

Posted Dec 21, 2008
Only addons i add one were Bugsack, !buggraber, and Headcount.

Rollback Post to Revision RollBack
_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#48 _ForgeUser724295

View User Profile

Send Message

Posted Dec 22, 2008
Nice find. This is a defect that would occur for anyone using the 12-hour time format mode (AM and PM). I'll log a defect and try to get a fix out for this. For those who don't want to wait, convert the references in HeadCountUtil.lua:formatTime():

displayDateTime should just be dateTime

It's a null pointer error.

Rollback Post to Revision RollBack
_ForgeUser970577
- Join Date: 7/22/2008
- Posts: 1
- Member Details
#43 _ForgeUser970577

View User Profile

Send Message

Posted Dec 18, 2008
Do I need to install anything on my EQDKP site for HeadCount to work?

Rollback Post to Revision RollBack
_ForgeUser724295
- Join Date: 4/19/2008
- Posts: 2
- Member Details
#45 _ForgeUser724295

View User Profile

Send Message

Posted Dec 19, 2008
You need the CTRT Raidtracker Import plugin for EQdkp. The latest testing I have done was with plugin version 1.16.13. I also tested using EQdkp Plus. EQdkp Plus seems to be nice for end-users with more options and it is automatically bundled with the plugin when you download it which eases some pain.

Rollback Post to Revision RollBack
To post a comment, please login or register a new account.