repost from the bigwigs thread:
gettin this error on the razuvious encounter when switching targets between hostiles:
the version im using is r10539 (along with newest bigwigs). the other bars like disrupting shout would also seem to disappear randomly and come back after a few cycles.
another guildy who was running r9943 (but same, latest version of bigwigs) was not getting any errors at all.
["message"] = "[2006/09/08 21:14:46-60]: CandyBar-2.0\\CandyBar-2.0.lua:1039: <unnamed>:SetNormalTexture(): Couldn't find 'this' in texture\n<in C code>: in function `SetNormalTexture'\nCandyBar-2.0\\CandyBar-2.0.lua:1039: in function `AcquireBarFrame'\nCandyBar-2.0\\CandyBar-2.0.lua:92: in function `Register'\nCandyBar-2.0\\CandyBar-2.0.lua:1184: in function `RegisterCandyBar'\nBigWigs\\Bars.lua:205: in function `obj_method'\nAceEvent-2.0\\AceEvent-2.0.lua:298: in function `TriggerEvent'\n...gs_RazuviousAssistant\\BigWigs_RazuviousAssistant.lua:147: in function `obj_method'\nAceEvent-2.0\\AceEvent-2.0.lua:298: in function `TriggerEvent'\nSpecialEvents-Aura-2.0\\SpecialEvents-Aura-2.0.lua:312: in function `obj_method'\nAceEvent-2.0\\AceEvent-2.0.lua:298: in function `TriggerEvent'\nAceEvent-2.0\\AceEvent-2.0.lua:854: in function <...ce\\AddOns\\BigWigs\\Libs\\AceEvent-2.0\\AceEvent-2.0.lua:846>\n\n ---",
gettin this error on the razuvious encounter when switching targets between hostiles
Thanks, fixed in the latest revision. The icon for the Mind Exhaustion bars will now be the same for all the adds, sadly. We need some CandyBar changes to make it work properly with raid icons, I think.
This is probably in part caused by the fact that I'm the only person in my raid using BigWigs, but I'm having a few issues with this module:
- The Taunt bar seems to appear when an Understudy gets taunted by one of our tanks, so it often gets overwritten shortly after using it with an Understudy as the other Priest stops MCing.
- Also related to Taunting, when the other Priest taunted Razuvious, I often got a warning that his add was ready to be MCed. Presumably because it turned into my Target's Target and was thus noticed as not having Mind Exhaustion any more.
- The Mind Exhaustion Bar for an Understudy resets if I target the Understudy for the first time again after breaking MC. I usually don't target the Understudy again until the timer is at 2 seconds, but it means I have an extra timer running.
Still works great despite these little things though, which are most likely caused by me being the only one in the raid using BigWigs.
["message"] = "[2006/10/19 21:20:02-308]: ...gs_RazuviousAssistant\\BigWigs_RazuviousAssistant.lua:17: Cannot find a library instance of AceLocale-2.2.\n<in C code>: in function `error'\nAceLibrary\\AceLibrary.lua:481: in function `AceLibrary'\n...gs_RazuviousAssistant\\BigWigs_RazuviousAssistant.lua:17: in main chunk\n\n ---",
["time"] = "2006/10/19 21:20:02",
["session"] = 308,
o.O i'm using the newest bigwigs from wowinterface.com
maybe you can help me with this question that's bugged me for a long time :)
how do we (end users) know when to update our mods that are ONLY on wowace.com/files? it's easy to know when to update a mod that's hosted on wowinterface.com but i've got a BUnch of mods that are ONLY on wowace.com/files.
basically, what's the right procedure for end users to follow when updating mods like this? and hopefully cut down on non-errors like the ones i reported for both this mod and also the nefcount module.
Started by Shyva and 100% recoded by me, this plugin assists priests on the Instructor Razuvious encounter in Naxxramas.
It provides timer bars for Taunt and Mind Exhaustion for all the adds, and also gives you a warning 5 seconds before an add is ready.
It distinguishes the adds based on their raid icon, so please make sure they all have one.
Obtain
Code here: http://svn.wowace.com/root/trunk/BigWigs_RazuviousAssistant/
Files here: http://svn.wowace.com/files/
gettin this error on the razuvious encounter when switching targets between hostiles:
the version im using is r10539 (along with newest bigwigs). the other bars like disrupting shout would also seem to disappear randomly and come back after a few cycles.
another guildy who was running r9943 (but same, latest version of bigwigs) was not getting any errors at all.
Thanks, fixed in the latest revision. The icon for the Mind Exhaustion bars will now be the same for all the adds, sadly. We need some CandyBar changes to make it work properly with raid icons, I think.
To correct in Babble:
I have found:
Is this this one ?
My translation in french:
To check for exhaustion
- The Taunt bar seems to appear when an Understudy gets taunted by one of our tanks, so it often gets overwritten shortly after using it with an Understudy as the other Priest stops MCing.
- Also related to Taunting, when the other Priest taunted Razuvious, I often got a warning that his add was ready to be MCed. Presumably because it turned into my Target's Target and was thus noticed as not having Mind Exhaustion any more.
- The Mind Exhaustion Bar for an Understudy resets if I target the Understudy for the first time again after breaking MC. I usually don't target the Understudy again until the timer is at 2 seconds, but it means I have an extra timer running.
Still works great despite these little things though, which are most likely caused by me being the only one in the raid using BigWigs.
the important two strings for the deDE Version are:
mindexhaustion = "Gedankenersch\195\182pfung",
taunt_trigger = "Reservist der Todesritter ist von Spott betroffen%.",
Janea
getting this on login. using r14301
maybe you can help me with this question that's bugged me for a long time :)
how do we (end users) know when to update our mods that are ONLY on wowace.com/files? it's easy to know when to update a mod that's hosted on wowinterface.com but i've got a BUnch of mods that are ONLY on wowace.com/files.
basically, what's the right procedure for end users to follow when updating mods like this? and hopefully cut down on non-errors like the ones i reported for both this mod and also the nefcount module.
thanks :)
There's no way to know when to update unless you know the internals of each mod and read the SVN log :/