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.e. an 'empty' entry for the realm I'd deleted the toon from. Getting rid of that empty section has made things work again.
Thus the code either needs to recognise when there are no toons left for a realm and not save that realm at all, and/or handle the "no toons in a saved realm" case correctly.
Confirmed that wT's fix above works. That "only make one or two at a time" bug had been annoying me for months (but not enough to poke at it or report it, admittedly).
I've seen this bug a few times in the last couple of weeks.
I join raid #1, MT windows are set, they work fine via oRA2.
I then leave that raid and join raid #2. New MTs are set. The boxes come up, but with the names they were set to in raid #1. The healthbars end up stuck at whatever I last saw those raid #1 players' health at.
Even if I'm promoted and set the MTs again myself in raid #2 I still see the old ones.
Any chance Copying from the 'Open Change Summary Log' display could be enabled? It's a pain to have to go find the .txt file for each addon if you want to CnP changes elsewhere.
-Ath, trying to point out Omen/Threat changes to his guild
I'm also missing the old pull-out bar functionality. I'd only just started using it as well. Very useful on encounters like Gruul and Void Reaver where you need to track your threat versus multiple tanks.
Aaaaaaaaaand... where's the option to have my own bar always coloured red and an arrow by it gone ?
Any chance of a Wiki page being setup for this excellent addon ? It doesn't need to be brilliant, just a nicer place to link folk to than the download link or a page on another site.
This addon seems to have no info. in the Wiki as yet. The auth in WAU is listed as Ominous, but his page in the Wiki doesn't list this addon either. I would have downloaded the addon via WAU, not direct from any web page.
The current version has a bug if you're fishing and place a lure on the pole. Updates.lua is expecting a Rogue to always have both a Mainhand and an Offhand weapon so errors out when checking the buff for the "two hander".
I've fixed this in my local copy:
37 function PoisonReminderFu:CastPoison(a1)
38 local search = gsub(ITEMENCHANTMENTADDSELFSELF, "%%s", "(.+)")
39 local Poison, Weapon = string.match(a1, search)
40 local Mainhand = GetInventoryItemLink("player", 16);
41 local Offhand = GetInventoryItemLink("player", 17);
42 if Poison and Weapon then
43 if Mainhand and string.find(Mainhand, Weapon) then
44 self.db.profile.MainHandPoison = Poison
45 elseif Offhand and string.find(Offhand, Weapon) then
46 self.db.profile.OffHandPoison = Poison
47 end
48 end
49 end
Basically I put the results of the GetInventoryItemLink() calls into variables and then changed the code to check if they're 'true' before passing them to string.find(). The original error was:
Error: bad argument #1 to 'find' (string expected, got nil)
AddOn: FuBar_PoisonReminderFu
File: Updates.lua
Line: 43
Count: 1
I noticed something like this in our guild's last Gruul run on Tuesday. I assumed it was because the OT was sometimes going out of melee range while avoiding cave-ins, thus making the melee DPS (me and others) candidates for the next Hurtful Strike.
Not in my case. MT1+2 stand about 5-10 yds apart, MT utilising the circumference of melee range on Gruul. We were all comfortably DPS'ing away, clear of the last shatter, plenty of time before the next, and *wham*. Our MT1 moves away from caveins and the MT2 moves with him.
We also had really weird stuff like MT2 showing top of the meter by 4-5 times, whilst MT1 definitely had aggro... and then suddenly it would flick back to a correct display.
Prior to last night (Thu 6th Dec 2007) I'd not seen any problems with Omen. But last night on Gruul the melee DPS all died on the first attempt. Why? We were clearly showing below both MT1 and 2 on Omen, in my case a clear 20-30% threat below, yet we were actually above MT2 and got killed by Hurtful Strike.
Initially we wondered if this was Blessing of Salvation not stacking with Tranquil Air Totem, whilst Omen thought it was... but then we went without that totem on subsequent attempts and still saw problems.
On Tue 4th Dec 2007 I saw no such problems in the same encounter. No Hurtful Strikes on me despite sometimes being within 1% of MT2 (no paladin, no shaman, so I was working without either threat reduction method, hmmm, maybe something buggy with how either one is applied?).
Either someone in the raid last night had a sufficiently old enough version of KTM (I do allow reception of data from it as the guild isn't strict enough on people using the same addons) or Omen ... or some update between the 5th and the 6th has bugged Omen itself. I run WAU every day before starting to play WoW.
Edit: The version I was using last night is "## X-Build: $Revision: 55025 $" (from Omen/Omen.toc)
Edit2: Looking at folder datestamps nothing to do with Omen was updated for me yesterday, so it was more likely someone else with a 'bad' version of Omen or KTM, if versions are the problem.
0
That's with latest from WAU, I downgraded to 81420 and things work again.
0
http://www.wowhead.com/?item=35298#comments
0
Having deleted the only character on another realm the top of <wow>\WTF\Account\<account name>\SavedVariables\Fubar_RestFu.lua looked like:
RestFuDB = { ["account"] = { ["Shadowsong" = { }, ["Turalyon"] = { ["Jersey"] = { ["restXP"] = 82500, ["currXP"] = 4354,i.e. an 'empty' entry for the realm I'd deleted the toon from. Getting rid of that empty section has made things work again.
Thus the code either needs to recognise when there are no toons left for a realm and not save that realm at all, and/or handle the "no toons in a saved realm" case correctly.
-Ath
0
That sounds like the error I have, which started after I ctrl-clicked (or whatever the tooltip says it is) to remove a toon on another realm:
0
0
I join raid #1, MT windows are set, they work fine via oRA2.
I then leave that raid and join raid #2. New MTs are set. The boxes come up, but with the names they were set to in raid #1. The healthbars end up stuck at whatever I last saw those raid #1 players' health at.
Even if I'm promoted and set the MTs again myself in raid #2 I still see the old ones.
0
-Ath, trying to point out Omen/Threat changes to his guild
0
-Ath
0
Aaaaaaaaaand... where's the option to have my own bar always coloured red and an arrow by it gone ?
-Ath, getting used to Omen2 otherwise.
0
ta,
-Ath
0
0
The current version has a bug if you're fishing and place a lure on the pole. Updates.lua is expecting a Rogue to always have both a Mainhand and an Offhand weapon so errors out when checking the buff for the "two hander".
I've fixed this in my local copy:
37 function PoisonReminderFu:CastPoison(a1) 38 local search = gsub(ITEMENCHANTMENTADDSELFSELF, "%%s", "(.+)") 39 local Poison, Weapon = string.match(a1, search) 40 local Mainhand = GetInventoryItemLink("player", 16); 41 local Offhand = GetInventoryItemLink("player", 17); 42 if Poison and Weapon then 43 if Mainhand and string.find(Mainhand, Weapon) then 44 self.db.profile.MainHandPoison = Poison 45 elseif Offhand and string.find(Offhand, Weapon) then 46 self.db.profile.OffHandPoison = Poison 47 end 48 end 49 endBasically I put the results of the GetInventoryItemLink() calls into variables and then changed the code to check if they're 'true' before passing them to string.find(). The original error was:
0
Not in my case. MT1+2 stand about 5-10 yds apart, MT utilising the circumference of melee range on Gruul. We were all comfortably DPS'ing away, clear of the last shatter, plenty of time before the next, and *wham*. Our MT1 moves away from caveins and the MT2 moves with him.
We also had really weird stuff like MT2 showing top of the meter by 4-5 times, whilst MT1 definitely had aggro... and then suddenly it would flick back to a correct display.
-Ath
0
Initially we wondered if this was Blessing of Salvation not stacking with Tranquil Air Totem, whilst Omen thought it was... but then we went without that totem on subsequent attempts and still saw problems.
On Tue 4th Dec 2007 I saw no such problems in the same encounter. No Hurtful Strikes on me despite sometimes being within 1% of MT2 (no paladin, no shaman, so I was working without either threat reduction method, hmmm, maybe something buggy with how either one is applied?).
Either someone in the raid last night had a sufficiently old enough version of KTM (I do allow reception of data from it as the guild isn't strict enough on people using the same addons) or Omen ... or some update between the 5th and the 6th has bugged Omen itself. I run WAU every day before starting to play WoW.
Edit: The version I was using last night is "## X-Build: $Revision: 55025 $" (from Omen/Omen.toc)
Edit2: Looking at folder datestamps nothing to do with Omen was updated for me yesterday, so it was more likely someone else with a 'bad' version of Omen or KTM, if versions are the problem.
0
MiniMapTrackingFrame:SetPoint("TOPLEFT","Minimap","TOPLEFT",0,-2) MinimapToggleButton:Hide() -- MinimapZoomIn:Hide() -- MinimapZoomOut:Hide() GameTimeFrame:Hide() endOf course the positioning will likely be all wrong. I use Discorf Frame Modifier to move them somewhere sensible.
-Ath