Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
I ignore the Enslaved Fire Elemental before General Vezax, but when marking up the groups, they are assigned to be tanked. Only had a few groups to really test this on though.
Marix, it still works. You need to record Ulduar and also manually enter tank and CC priorities of your guild. This can take quite some time.
I'm probably going to do it for my guild (again, thanks to no backup) and then I'll upload a copy here. I've got all the mobs from Ulduar, just not my crowd control setup.
I really like the concept of this addon, but I appear to be having some trouble with it on the 3.1 servers.
These bugs have been found by testing Prescription in a 2-man raid group. I am a druid and my friend is a mage and we were both idling in Ironforge.
1. It seems to check for all four categories even if I only tick off eg. flasks.
2. I had Prescription tell me locally who was missing buffs, but it never reported what buffs my friend was missing nor did it ever whisper him.
3. Checking only for flasks and buffing myself with Mark of the Wild would stop the feedback from appearing. The feedback is the message I receive after a check with who is missing what. It is like the buff would stop the check. Might be the same with other buffs.
Additionally, it would be really nice if I was able to disable all raid chatter from Prescription. The whisper notification should be fine for having forgetful raid members redo their buffs.
Do you have Recount? - And if yes, if you set it to save more fights than the default 5, I usually receive an error like yours when relogging with 5+ fights saved.
[2009/03/08 18:54:10-361-x1]: Recount-1012\Tracker.lua:1148: attempt to concatenate global 'RecountFightingLevel' (a nil value)
Recount-1012\Tracker.lua:1414: in function `AddDamageData'
Recount-1012\Tracker.lua:309: in function <Interface\AddOns\Recount\Tracker.lua:279>
Recount-1012\Tracker.lua:634: in function `?'
CallbackHandler-1.0-3 (Ace3):146: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[21]":4: in function <[string "safecall Dispatcher[21]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[21]":13: in function `?'
CallbackHandler-1.0-3 (Ace3):91: in function `Fire'
AceEvent-3.0-3 (Ace3):73: in function <Interface\AddOns\Ace3\AceEvent-3.0\AceEvent-3.0.lua:72>
When people leave the raid from group 6-8 (wait list groups) and then whisper me "wl add", Headcount often replies to them that they are already on the waiting list.
I've tried making them wait 10 seconds, which is how often Headcount updates, but Headcount will still report them as already on the wait list.
I should of course have mentioned that I am exporting to EQDKP Plus, which is causing me some trouble, as it only has 1 list for who attended a raid when exporting to it.
This means that in a raid that lasted the whole evening, if someone was only in for one or two bosses, I've experienced them not being exported.
Do you have any ideas for how to solve this, except for ending each raid after a boss and starting a new one?
Does anyone know how Headcount handles a situation where for example the raid has killed two bosses during a raid lasting one hour.
Player A was with the raid on the first boss, but not on the second.
Player B was with the raid on the second boss, but not the first.
And Player C was in the raid the whole time.
When exporting this raid, what players will be in the log?
I am pretty sure that Player C will be there, but what about A and B?
Ah, thanks for telling me that. I thought basically all loadondemand addons were broken.
Grid2Options worked fine after that, I did however have some nasty black areas around the frame covering parts of it, but I haven't tried the latest build.
0
I ignore the Enslaved Fire Elemental before General Vezax, but when marking up the groups, they are assigned to be tanked. Only had a few groups to really test this on though.
0
I'm probably going to do it for my guild (again, thanks to no backup) and then I'll upload a copy here. I've got all the mobs from Ulduar, just not my crowd control setup.
0
0
These bugs have been found by testing Prescription in a 2-man raid group. I am a druid and my friend is a mage and we were both idling in Ironforge.
1. It seems to check for all four categories even if I only tick off eg. flasks.
2. I had Prescription tell me locally who was missing buffs, but it never reported what buffs my friend was missing nor did it ever whisper him.
3. Checking only for flasks and buffing myself with Mark of the Wild would stop the feedback from appearing. The feedback is the message I receive after a check with who is missing what. It is like the buff would stop the check. Might be the same with other buffs.
Additionally, it would be really nice if I was able to disable all raid chatter from Prescription. The whisper notification should be fine for having forgetful raid members redo their buffs.
Keep up the good work Starinnia.
0
I am using v3.1b of both Recount and RecountDeathTrack (and RecountFailBot)
0
0
0
I've tried making them wait 10 seconds, which is how often Headcount updates, but Headcount will still report them as already on the wait list.
0
+1
Eventually as "wl add <note>"
0
I'd like to suggest a feature from NRT; The option to ignore 10-man raids.
0
This means that in a raid that lasted the whole evening, if someone was only in for one or two bosses, I've experienced them not being exported.
Do you have any ideas for how to solve this, except for ending each raid after a boss and starting a new one?
0
Player A was with the raid on the first boss, but not on the second.
Player B was with the raid on the second boss, but not the first.
And Player C was in the raid the whole time.
When exporting this raid, what players will be in the log?
I am pretty sure that Player C will be there, but what about A and B?
0
0
Grid2Options worked fine after that, I did however have some nasty black areas around the frame covering parts of it, but I haven't tried the latest build.
0