HeadCount2

This project is abandoned.

Whether this project is out of date or its author marked it as abandoned, this project is no longer maintained.

If you wish to take this project over, please report it and state your intentions.

Main Screen

HeadCount2

Re-Write of the original HeadCount. This rewrite is to move to Ace3 and WoW 4.0

HeadCount2 is a configurable World of Warcraft add-on that automatically tracks raid attendance, loot, and boss kills.

HeadCount2 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?

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 the config UI

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.

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, HeadCount2 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.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of kagaro kagaro Nov 12, 2010 at 23:06 UTC - 0 likes

    The export funciton is done, but no ui access to ti yet. ill be working on it more tommarrow.

  • Avatar of zars123 zars123 Nov 12, 2010 at 06:17 UTC - 0 likes

    Hi Kagaro love the work U put in to it

  • Avatar of kurrgan kurrgan Nov 11, 2010 at 17:37 UTC - 0 likes

    First of all, love the client - and the config window seems to be working - what would be the command to export the data?

  • Avatar of carlosgr carlosgr Nov 11, 2010 at 01:04 UTC - 0 likes

    Not working the GUI menu. I can't access through /hc2, LDB, or mini-map. Maybe is an error for the client languange. Mine is spanish. No error also.

  • Avatar of Ketrew Ketrew Nov 08, 2010 at 19:44 UTC - 0 likes

    Thank you Kagaro!

  • Avatar of kagaro kagaro Nov 07, 2010 at 20:08 UTC - 0 likes

    The tracker window should now show you a lit of raids, no details are impleented yet, but you can alteast see if now. Ill be making a few more custom widgets for the display so the scroll highlights and looks smooth.

  • Avatar of Hitmehard Hitmehard Nov 07, 2010 at 07:20 UTC - 0 likes

    Thanks for your very hard work and endless updates Kagaro! Everyone keeps posting bugs and errors and that's all fine but a thank you should not be forgotten.

  • Avatar of kagaro kagaro Nov 06, 2010 at 01:45 UTC - 0 likes

    I push an update it should package in a few mins.

  • Avatar of SirTreek23 SirTreek23 Nov 06, 2010 at 01:35 UTC - 0 likes

    I'm getting this error in ICC atm.

    1x HeadCount2-1.0\RaidTracker.lua:266: attempt to index field 'db' (a nil value) HeadCount2-1.0\RaidTracker.lua:483: in function `processAttendance' HeadCount2-1.0\RaidTracker.lua:942: in function `?' CallbackHandler-1.0-6 (Ace3):147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147> <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4> <in C code>: ? <string>:"safecall Dispatcher[1]":13: in function `?' CallbackHandler-1.0-6 (Ace3):92: in function `Fire' AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>

  • Avatar of kagaro kagaro Nov 05, 2010 at 23:44 UTC - 0 likes

    the tracker should be working, the gui for tehtracker isnt done yet so there wont be a popup. if you turn debug on you will see teh debug output that it is working. im gonna try toknock out the gui over the weekend if I can. Im starting a new job onTuesday and need to go buy some new clothes for it so ill try to get done what I can. So to summariez it should be tracking everything just no gui for it right now. i know waitlist whispers are working i tested those out in voa the other day. When you create a raid it should start the raid tracking process.

Facts

Date created
Oct 22, 2010
Categories
Last update
Sep 14, 2012
Development stage
Abandoned
Language
  • deDE
  • enUS
  • esES
  • esMX
  • frFR
  • koKR
  • ruRU
  • zhCN
  • zhTW
License
All Rights Reserved
Downloads
45,648
Recent files

Authors