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 am using the newest SVN Version (oRA2_Buff-r13156[Grimwald].zip) and the error i attached to my post is allways poping up when i click a option in the buffs menu. What can i do about that?
edit: And my general Window is getting spammed by "Debug: Unit (xx): buff 'xx' not found" messages, how to turn that off?
I also have problems with oRA2_Buff. The attached messages always appear when buffing myself (I haven't tried the addon in raids yet). I am using the German WoW-client.
I also have problems with oRA2_Buff. The attached messages always appear when buffing myself (I haven't tried the addon in raids yet). I am using the German WoW-client.
You'll get spammed to those DEBUG messages in raid. :) For some reason the new version has debugging info turned on. To get rid of those, find the following line:
self:SetDebugging(true)
and change it to:
self:SetDebugging(false)
Do this for the following files to be sure you're rid of debug messages:
I am using the newest SVN Version (oRA2_Buff-r13156[Grimwald].zip) and the error i attached to my post is allways poping up when i click a option in the buffs menu. What can i do about that?
The 1st error is a bug in UnregisterBucketEvent - I already had a bug opened on Flyspray a few weeks back and it's posted on the WoWI-Portal linked in the Ace2 Thread as well...
The debug option will be set to false by default when most of the debugging work seems done. Until then you can alter it in the source code or enable/disable it calling SetDebugging() in the console.
Wierd i fixed my bug through deleting the "grimwald_timersoptional" array in the "root:World of Warcraft\WTF\Account\ACCOUNTNAME\SavedVariables\ora2.lua" file.
I also have problems with oRA2_Buff. The attached messages always appear when buffing myself (I haven't tried the addon in raids yet). I am using the German WoW-client.
This should be fixed now.
Additionally I moved the debug output to ChatFrame5 - still annoying if you acutally use it, but disabling debugging as mentioned before will get rid of the spam...
Wierd i fixed my bug through deleting the "grimwald_timersoptional" array in the "root:World of Warcraft\WTF\Account\ACCOUNTNAME\SavedVariables\ora2.lua" file.
I'm guessing it will only work until you try to change the buffs/cooldowns you're displaying - UnregisterBucketEvent isn't called if you're not showing any timers yet.
To fix it permanently you have to replace "bucket.func" with "self" in AceEvent-2.0.lua, in lines 785 and 788. (You'll have to modify that in the first or most recent AceEvent version loaded.)
edit: And my general Window is getting spammed by "Debug: Unit (xx): buff 'xx' not found" messages, how to turn that off?
You'll get spammed to those DEBUG messages in raid. :) For some reason the new version has debugging info turned on. To get rid of those, find the following line:
self:SetDebugging(true)
and change it to:
self:SetDebugging(false)
Do this for the following files to be sure you're rid of debug messages:
Optional/Timer.lua
Optional/BuffLocal.lua
Libs/SpellTimes-1.0/SpellTimes-1.0.lua
The 1st error is a bug in UnregisterBucketEvent - I already had a bug opened on Flyspray a few weeks back and it's posted on the WoWI-Portal linked in the Ace2 Thread as well...
The debug option will be set to false by default when most of the debugging work seems done. Until then you can alter it in the source code or enable/disable it calling SetDebugging() in the console.
Thanks mist, i was searching for that!
This should be fixed now.
Additionally I moved the debug output to ChatFrame5 - still annoying if you acutally use it, but disabling debugging as mentioned before will get rid of the spam...
I'm guessing it will only work until you try to change the buffs/cooldowns you're displaying - UnregisterBucketEvent isn't called if you're not showing any timers yet.
To fix it permanently you have to replace "bucket.func" with "self" in AceEvent-2.0.lua, in lines 785 and 788. (You'll have to modify that in the first or most recent AceEvent version loaded.)