Loggerhead didn't work for me last night in Flexible Raid difficulty of the first wing of SoO. (It worked when I zoned into an old 5-man for testing.) Is fixing it as simple as adding the missing difficulties to the difficulty lookup table? There are a couple of gaps in Blizzard's numbering scheme.
Was there an option added to record 5-mans in Headcount2? And, if so, can it be disabled? Last night, after we finished our raid, I disbanded the raid, logged out and back in (to close wowcombatlog.txt), and then went on a 5 man. Headcount2 activated to record the 5-man information as a new raid, which it had never done before and surprised me. The 5-man was only ever a party, we never switched it to raid.
It's been about 4 weeks since we've been raiding (holiday time). So I don't know if it stopped working in between then and now. It was correct about 4 weeks ago.
In last nights raid, items that I marked as "disenchanted" or "bank" were recorded as going to the person doing the DE/banking, and not as DE or Bank. I'm also not able to change the note to show items as disenchanted. I can click the minibutton but it still records the person; I can choose Disenchanted from the dropdown and it changes . It used to record items correctly; I am using the version updated a couple days ago (v1.0.4).
In the Sindragosa encounter (normal-25) the 5 frost beacon targets weren't being marked with their raid icons. Up until the 7471 version, they had been being marked. I looked over the settings, and could not see any that had changed (the raid icons and broadcast boxes were still checked), and I was raid leader. Was there a change in the 7471 version, or is there something that changed?
There are a host of other addons that are adding talent inspection, so whatever you find out may apply to more than TipTop. I'll look for a replacement to TipTop in the meantime.
Well, no errors with r250 last night, but it was only 10 man raiding and I don't think there was any talent switching. My next 25-man isn't until Wed...so I'll let you know more on Thursday. :) Thanks again.
I've downloaded r250 and will try it. I did make the change for last night's raid to extend the time on the talent checks as you suggested a page or two back and didn't get an error.
I looked at the error message referenced above, and both that person and I use TipTop. There are several other mods in common, of course, but TipTop also does some talent inspection. Perhaps there is some conflict?
Date: 2009-06-03 20:26:35
ID: -1
Error occured in: Global
Count: 8
Message: ..\AddOns\RaidBuffStatus\Core.lua line 858:
attempt to compare number with nil
Debug:
(tail call): ?
RaidBuffStatus\Core.lua:858: code()
RaidBuffStatus\Core.lua:1785: ReadRaid()
RaidBuffStatus\Core.lua:1401:
RaidBuffStatus\Core.lua:1383
(tail call): ?
[C]: ?
[string "safecall Dispatcher[1]"]:9:
[string "safecall Dispatcher[1]"]:5
(tail call): ?
...ce\AddOns\Acheron\Libs\AceTimer-3.0\AceTimer-3.0.lua:160:
...ce\AddOns\Acheron\Libs\AceTimer-3.0\AceTimer-3.0.lua:132
The first time, we were just finished with Razorscale, and some people were probably changing specs. I'm not sure on the second, one priest might have been switching specs. I'm using the latest version, it reports itself as:
People were running back after a wipe in Ulduar, it occurred while I was approaching the transport disk in the first room, but I had not taken it yet. Some people were repairing, some summoning pets, some had transported in deeper already. I don't think anyone was changing specs.
Do you want me to try both r243 and the time change at once? Or just r243?
0
0
I am using 1.12 as distributed by Curse.com.
0
0
0
0
0
Thanks again for your help.
0
There are a host of other addons that are adding talent inspection, so whatever you find out may apply to more than TipTop. I'll look for a replacement to TipTop in the meantime.
0
0
I looked at the error message referenced above, and both that person and I use TipTop. There are several other mods in common, of course, but TipTop also does some talent inspection. Perhaps there is some conflict?
0
Date: 2009-06-05 21:40:29
ID: -3
Error occured in: Global
Count: 130
Message: ..\AddOns\RaidBuffStatus\Core.lua line 858:
attempt to compare number with nil
Debug:
(tail call): ?
RaidBuffStatus\Core.lua:858: code()
RaidBuffStatus\Core.lua:1785: ReadRaid()
RaidBuffStatus\Core.lua:1401: DoReport()
RaidBuffStatus\Core.lua:2843: ?()
...Bar\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
...Bar\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
[string "safecall Dispatcher[1]"]:4:
[string "safecall Dispatcher[1]"]:4
[C]: ?
[string "safecall Dispatcher[1]"]:13: ?()
...Bar\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
...ace\AddOns\Bagnon\libs\AceEvent-3.0\AceEvent-3.0.lua:119:
...ace\AddOns\Bagnon\libs\AceEvent-3.0\AceEvent-3.0.lua:118
0
0
Date: 2009-06-03 20:26:35
ID: -1
Error occured in: Global
Count: 8
Message: ..\AddOns\RaidBuffStatus\Core.lua line 858:
attempt to compare number with nil
Debug:
(tail call): ?
RaidBuffStatus\Core.lua:858: code()
RaidBuffStatus\Core.lua:1785: ReadRaid()
RaidBuffStatus\Core.lua:1401:
RaidBuffStatus\Core.lua:1383
(tail call): ?
[C]: ?
[string "safecall Dispatcher[1]"]:9:
[string "safecall Dispatcher[1]"]:5
(tail call): ?
...ce\AddOns\Acheron\Libs\AceTimer-3.0\AceTimer-3.0.lua:160:
...ce\AddOns\Acheron\Libs\AceTimer-3.0\AceTimer-3.0.lua:132
The first time, we were just finished with Razorscale, and some people were probably changing specs. I'm not sure on the second, one priest might have been switching specs. I'm using the latest version, it reports itself as:
RaidBuffStatus, v3.108
0
0
Do you want me to try both r243 and the time change at once? Or just r243?