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.
One bit of good news with this is that a lot of people got really familiar with changing addons for this in 4.1, so it should be even easier in 4.2. ;)
Most important addons do get updated eventually; hopefully more addon authors will be able to make changes before 4.2 goes live, this time around. MSBT did eventually get officially updated for 4.1, too.
Perhaps, but it was possible before this patch or latest update, to use the raid markers out of combat while Mapster was active. That is now not possible; if it's possible to tweak the UI to still allow the raid markers to work, naturally that would be make the addon more useful.
Thanks for the updates to Mapster to keep it current.
I'm getting this error now, since patch 4.1, that prevents placing the raid markers on the ground. This can be tested by going into a raid, pulling out the pop-out from the right of the screen, and trying to place a raid marker.
Date: 2011-04-28 21:14:12
Error occured in: AddOn: Mapster
Message: Error: AddOn Mapster attempted to call a forbidden function (PlaceRaidMarker()) from a tainted execution path.
Debug:
[C]: PlaceRaidMarker()
...mpactRaidFrames\Blizzard_CompactRaidFrameManager.lua:146: func()
..\FrameXML\UIDropDownMenu.lua:638: UIDropDownMenuButton_OnClick()
[string "*:OnClick"]:1:
[string "*:OnClick"]:1
I'm not seeing any boss kills in the reports anymore; are they still working for anyone else? I believe they were showing up in version 1.07, but they haven't in 1.08 or 1.09. Headcount just doesn't seem to recognize any boss kills.
On a related note, if this is a common problem, what about using the same boss recognition (or at least falling back on it) as BigWigs? BigWigs already does all the boss detection, and knows when a boss is successfully killed; perhaps it would be possible to hook onto that for logging bosses, for people who are running BigWigs.
Thanks for all the work on LittleWigs, it's a huge help in the dungeons!
Here are some errors that came up when running ZA and ZG last night, using LittleWigs r925. I couldn't tell if these had been fixed by the more recent versions that are out.
This "berserk" error came up for Nalorakk, Jan'alai, and Halazzi:
Date: 2011-04-27 20:38:04
ID: -7
Error occured in: Global
Count: 1
Message: ..\AddOns\BigWigs_Core\BossPrototype.lua line 362:
Module BigWigs_Bosses_Nalorakk uses "berserk" as a toggle option, but it does not exist in the modules default values.
Debug:
(tail call): ?
[C]: error()
BigWigs_Core\BossPrototype.lua:362:
BigWigs_Core\BossPrototype.lua:355
BigWigs_Core\BossPrototype.lua:385: Message()
BigWigs_Core\BossPrototype.lua:534: Berserk()
LittleWigs_ZulAman\Nalorakk.lua:55: OnEngage()
BigWigs_Core\BossPrototype.lua:272: Engage()
BigWigs_Core\BossPrototype.lua:172: ?()
...igs\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147:
...igs\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
[string "safecall Dispatcher[1]"]:4:
[string "safecall Dispatcher[1]"]:4
[C]: ?
[string "safecall Dispatcher[1]"]:13: ?()
...igs\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
...ce\AddOns\BigWigs\Libs\AceEvent-3.0\AceEvent-3.0.lua:120:
...ce\AddOns\BigWigs\Libs\AceEvent-3.0\AceEvent-3.0.lua:119
Finally, when Jin'do goes into the spirit phase, the addon spams the message "Phase 2" with the sound, over and over and over. Whatever triggers it just keeps repeating, apparently.
This addon is a terrific help, thanks for all the work that goes into it!
On a related note to the above request, a way to ignore or automatically discard all Wintergrasp raids would be great. (Maybe an option to automatically remove any raids where no boss was killed and no epics were looted.) For those who do Wintergrasp a lot, those raids end up clogging up the list.
On Lord Jaraxxus, a personal warning should be added for people who stand in the Legion Flame fire on the ground. There is a general warning in place to list the people who get the debuff, which generates the green patches of fire. But there needs to also be a standard flash'n'shake warning for anybody who stands around in the fire, taking damage. The debuff put on a character, and the patch of fire on the ground, are all called "Legion Flame", so that can be a bit confusing.
For the standard "Fire on YOU!" flash'n'shake warning to be added, the spells are: 66877, 67070, 67071, 67072.
Afterthought: just to clarify, oRA3 is not getting MT/MA frames, and not having them is not a sign that the addon is broken.
I'm in the same boat as the previous posters. The fact that oRA3 isn't getting MT frames doesn't mean it's broken, but it does mean it is far less useful as a raiding addon than oRA2.
Given how very difficult it is to get casual raiders to keep even a few addons up to date, it's hard to imagine that they would have to add/update/configure an extra 2-3 addons just to get MT boxes similar to what oRA2 provides, if we upgrade to oRA3. As much as I'd like to do the switch to oRA3 myself, that's not an option either, since the two versions aren't compatible.
As such, I hope that oRA2 is kept up to date for as long as possible, and I certainly appreciate the effort that has been put in to maintain this older version. It's been a great help in raiding to know that everybody has the same main tank boxes to look at, and the other features are handy.
If this is still being maintained... it looks like patch 3.3 broke/changed the readycheck feature. It isn't working at all in oRA2; the /readycheck command doesn't even work, and as an assist when it is pulled up it just shows the person doing the readycheck as ready, without getting data on anyone else.
A few oddities and errors with the version check section have popped up; I posted tickets for two of them.
Apart from those bugs, one small issue relates to the BigWigs public release versions. If possible, it would help to have the listed version number in game updated to the version number listed on the website and BigWigs zip file. For example, the current latest public release is r6570. In game, the version is listed as r6569, in both the /bwv output and the About section of the addon. That can be confusing for some people, as they are not certain if they installed the latest release properly.
It's a rather minor thing, but seemed worth mentioning as it was causing some raiders a bit of consternation when updating.
The new BigWigs looks great; thanks to everybody who put in the time and effort to make it!
One request: can we get public releases pushed frequently for it? I had a raid the other night at General Vezax that wasn't able to finish, because too many people were getting errors from BigWigs. The problem was fixed in r6553, but that hasn't shown up in a public release, and I don't want to have guildmates get in the habit of needing to use alpha releases regularly for raids.
A new public release each Tuesday, when there are bugfixes to apply, would help out a lot; thanks!
Any word on MagicMarker updates for WotLK? With Ulduar looking to again require (or at least encourage) crowd control on trash, this will be in demand.
0
Most important addons do get updated eventually; hopefully more addon authors will be able to make changes before 4.2 goes live, this time around. MSBT did eventually get officially updated for 4.1, too.
0
If accurate, that can be checked again via the API, in BigWigs.
0
0
I'm getting this error now, since patch 4.1, that prevents placing the raid markers on the ground. This can be tested by going into a raid, pulling out the pop-out from the right of the screen, and trying to place a raid marker.
0
On a related note, if this is a common problem, what about using the same boss recognition (or at least falling back on it) as BigWigs? BigWigs already does all the boss detection, and knows when a boss is successfully killed; perhaps it would be possible to hook onto that for logging bosses, for people who are running BigWigs.
0
Here are some errors that came up when running ZA and ZG last night, using LittleWigs r925. I couldn't tell if these had been fixed by the more recent versions that are out.
This error came up for Jin'do and Halazzi:
Some other errors:
This "berserk" error came up for Nalorakk, Jan'alai, and Halazzi:
Finally, when Jin'do goes into the spirit phase, the addon spams the message "Phase 2" with the sound, over and over and over. Whatever triggers it just keeps repeating, apparently.
0
On a related note to the above request, a way to ignore or automatically discard all Wintergrasp raids would be great. (Maybe an option to automatically remove any raids where no boss was killed and no epics were looted.) For those who do Wintergrasp a lot, those raids end up clogging up the list.
0
On Lord Jaraxxus, a personal warning should be added for people who stand in the Legion Flame fire on the ground. There is a general warning in place to list the people who get the debuff, which generates the green patches of fire. But there needs to also be a standard flash'n'shake warning for anybody who stands around in the fire, taking damage. The debuff put on a character, and the patch of fire on the ground, are all called "Legion Flame", so that can be a bit confusing.
For the standard "Fire on YOU!" flash'n'shake warning to be added, the spells are: 66877, 67070, 67071, 67072.
0
Death and Decay is covered for the 10-man normal version, spell #71001.
The other three versions that need to be added are: normal 25-man version #72108; 10 and 25-man heroic modes, which should be spell #72109 and #72110.
0
I'm in the same boat as the previous posters. The fact that oRA3 isn't getting MT frames doesn't mean it's broken, but it does mean it is far less useful as a raiding addon than oRA2.
Given how very difficult it is to get casual raiders to keep even a few addons up to date, it's hard to imagine that they would have to add/update/configure an extra 2-3 addons just to get MT boxes similar to what oRA2 provides, if we upgrade to oRA3. As much as I'd like to do the switch to oRA3 myself, that's not an option either, since the two versions aren't compatible.
As such, I hope that oRA2 is kept up to date for as long as possible, and I certainly appreciate the effort that has been put in to maintain this older version. It's been a great help in raiding to know that everybody has the same main tank boxes to look at, and the other features are handy.
0
0
0
Apart from those bugs, one small issue relates to the BigWigs public release versions. If possible, it would help to have the listed version number in game updated to the version number listed on the website and BigWigs zip file. For example, the current latest public release is r6570. In game, the version is listed as r6569, in both the /bwv output and the About section of the addon. That can be confusing for some people, as they are not certain if they installed the latest release properly.
It's a rather minor thing, but seemed worth mentioning as it was causing some raiders a bit of consternation when updating.
0
One request: can we get public releases pushed frequently for it? I had a raid the other night at General Vezax that wasn't able to finish, because too many people were getting errors from BigWigs. The problem was fixed in r6553, but that hasn't shown up in a public release, and I don't want to have guildmates get in the habit of needing to use alpha releases regularly for raids.
A new public release each Tuesday, when there are bugfixes to apply, would help out a lot; thanks!
0