start making suggestions, im going to be starting HeadCount2 shortly. ive been slammed at work so havent had a chance yet to really crush out the changes ive got working on my desk.
start making suggestions, im going to be starting HeadCount2 shortly. ive been slammed at work so havent had a chance yet to really crush out the changes ive got working on my desk.
1. Ability to broadcast the waitlist to guild or officer chat (and to automatically broadcast when someone is added or removed from the wl)
2. Ability to export xml string for individual bosses
3. Syncing with other raid officers using the addon (item drops/attendance/current waitlist)
4. Ability to send WL broadcasts to a custom channel and recieve checkins from out of guild alts for their main
5. A plain text/bbcode export that summarizes the combined attendance time and wl time for each person for the night:
Name (Time in Raid/Standby)
Larry (4:05)
Moe (4:03)
Curly (4:03)
Tom (4:03)
Jerry (4:03)
Joe (3:15)
Bob (2:55)
Jay (1:05)
...
etc.
Only thing I can advise if you want to use EQDKP plus and Headcount to use time-based stuff is the following: Add an event that has the complete DKP (IE: 4 hours + bonus for on time). Upon importing you add a new raid that has all those people in that raid. After that just add a DKP adjustment if somebody only attended 2 hours.
Granted, I adjusted EQDKP to only count that starting raid for attendance and also automatic makes that starting raid upon importing.
There is also DKPLogParser project.. But it is a very powerful and complex app.
Only thing I can advise if you want to use EQDKP plus and Headcount to use time-based stuff is the following: Add an event that has the complete DKP (IE: 4 hours + bonus for on time). Upon importing you add a new raid that has all those people in that raid. After that just add a DKP adjustment if somebody only attended 2 hours.
Granted, I adjusted EQDKP to only count that starting raid for attendance and also automatic makes that starting raid upon importing.
Sounds like just as much work, but coming from the other side of things.
I hope Kagaro gets some ideas for HC2 from my use case example :p
Also, I'd like to third the syncing suggestion: it's a must. We lose NRT data at least once a month due to our guild leader DCing before she can export it to eqDKP.
Good question. It should probably have options to go on either a selection of guild ranks, and/or people with Raid Leader / Assist access in the raid, and/or a specific list of people by name.
Maybe the addon could use the raid and guild addon communication channels to discover who else is using the addon, and then query the user as to whether they should be allowed to sync data for the current raid.
I raid with an alliance of guilds using eqdkp 1.3RCC. Currently, all data is entered manually which is causing a lot of errors, etc. I'm promoting the use of Headcount as a better management tool, but they have some questions.
Will it work in a multi-guild alliance environment?
Is anyone using eqdkp 1.3 today with headcount successfully?
Suggestion for the loot tracking part of it: find a way to identify loot that was DE'ed as such. It can be marked as such, or we could enter a specific name for the deisgnated enchanter at the start of every raid. Though that last part assumes there'd be a way to differentiate between valid loot that the enchanter won and loot that's just being DE'ed (prompt user whenever that person gets loot?).
Clearly it's something that applies to my guild only, not everyone, but yeah I have a need for it. The difference being that the guild gets the shards and nobody gets loot (no bids). For tracking purposes, it's easier for me. No big deal, either way.
Has anyone managed to make the Caches in Ulduar track the kills of Hodir, Freya, Mimiron and Kologarn reliably? I've tried the 'patch' from WoWI but we're still having issues with it.
I did'nt found any code for boss yell triggers inside. For me it look like HC is not possible to detect boss enconters, which are no boss kills (Hodir,Thorim, Freya, Mimiron), atm.
For this there are some cache/box names, localized too, but the "mousover" part to detect them is still TODO.
As workaround I am stop/starting a new raid ahead of these Boss fights. So I only have to rename the Trash mob to the boss's name (Inside EQDKP Import Plugin, using one Raid per Boss).
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
1. Ability to broadcast the waitlist to guild or officer chat (and to automatically broadcast when someone is added or removed from the wl)
2. Ability to export xml string for individual bosses
3. Syncing with other raid officers using the addon (item drops/attendance/current waitlist)
4. Ability to send WL broadcasts to a custom channel and recieve checkins from out of guild alts for their main
5. A plain text/bbcode export that summarizes the combined attendance time and wl time for each person for the night:
Name (Time in Raid/Standby)
Larry (4:05)
Moe (4:03)
Curly (4:03)
Tom (4:03)
Jerry (4:03)
Joe (3:15)
Bob (2:55)
Jay (1:05)
...
etc.
There is also DKPLogParser project.. But it is a very powerful and complex app.
Synchronise with other people in the raid.
Those are my only two wishes for the new version.
Sounds like just as much work, but coming from the other side of things.
I hope Kagaro gets some ideas for HC2 from my use case example :p
Also, I'd like to third the syncing suggestion: it's a must. We lose NRT data at least once a month due to our guild leader DCing before she can export it to eqDKP.
To clarify, this should be Raid Leader or Assists, correct?
Maybe the addon could use the raid and guild addon communication channels to discover who else is using the addon, and then query the user as to whether they should be allowed to sync data for the current raid.
Will it work in a multi-guild alliance environment?
Is anyone using eqdkp 1.3 today with headcount successfully?
Any help would be appreciated.
Yes, I am. I've reinstalled the 'patch' and will try again this week and perhaps take a few screenies if I remember.
Didn't see that. I'll check again. Thanks.
For this there are some cache/box names, localized too, but the "mousover" part to detect them is still TODO.