tekkub/Cork — Issue #68: Reproducible raid buffing bugout using Cork's macro
Author: Zidomo
Created: 2012-01-11 04:10:15+00:00
State: open

75b58b217 / 4.3.0.44-Beta, WoW 4.3 live, USEnglish client server.

In a 25-man same server raid (not Raid Finder) in Baradin Hold, 85 Priest, Cork buffing macro button created through its options & located on the default Blizzard icon bars. With not all of the raid in the same vicinity (some in the instance, some still in a city), click the Cork macro button to buff (with a Priest, the macro button does Power Word: Fortitude & Shadow Protection). Error is thrown up and no buffs are cast:

["message"] = "Cork-4.3.0.44\\templates\\RaidBuffingItems.lua:81: Usage: GetRaidRosterInfo(index)\nCork-4.3.0.44 \\templates\\RaidBuffingItems.lua:81: in function `CorkIt'\nCork-4.3.0.44\\Cork.lua:239: in function \n: in function `Click'\nInterface\\FrameXML\\ChatFrame.lua:1508: in function `?':\nInterface\\FrameXML\\ChatFrame.lua:4273: in function `ChatEdit_ParseText':\nInterface\\FrameXML\\ChatFrame.lua:3992: in function `ChatEdit_SendText':\nInterface\\FrameXML\\ChatFrame.lua:2704: in function :\n: ?\n: ?\n: ?\n: in function `UseAction'\nInterface\\FrameXML\\SecureTemplates.lua:275: in function `handler':\nInterface\\FrameXML\\SecureTemplates.lua:561: in function :\n",
["type"] = "error",
["locals"] = {
"self =

{\n}\nframe = CorkFrame {\n 0 = \n SetManyAttributes = defined @Interface\\AddOns\\Cork\\Cork.lua:225\n}\nplayersonly = true\ncast = false\n(for index) = 1\n(for limit) = 25\n(for step) = 1\ni = 1\nunit = \"raid1\"\n(*temporary) = defined =[C]:-1\n(*temporary) = 3\nitemid = 49633\nCork =

{\n ValidUnit = defined @Interface\\AddOns\\Cork\\templates\\RaidBuffer.lua:47\n GenerateLastBuffedBuffer = defined @Interface\\AddOns\\Cork\\templates\\LastBuffedBuffer.lua:9\n GenerateRaidBuffer = defined @Interface\\AddOns\\Cork\\templates\\RaidBuffer.lua:12\n GenerateMacro = defined @Interface\\AddOns\\Cork\\MacroGenerator.lua:9\n Update = defined @Interface\\AddOns\\Cork\\Cork.lua:172\n SpellCastableOnUnit = defined @Interface\\AddOns\\Cork\\Cork.lua:259\n anchor = {\n }\n GenerateTempEnchant = defined @Interface\\AddOns\\Cork\\templates\\TempEnchant.lua:19\n GenerateRaidScan = defi", -- [1]
"ned @Interface\\AddOns\\Cork\\templates\\RaidBuffer.lua:74\n db =

{\n }\n GenerateItemBuffer = defined @Interface\\AddOns\\Cork\\templates\\RaidBuffingItems.lua:19\n petmappings =

{\n }\n dbpc =

{\n }\n GenerateAdvancedSelfBuffer = defined @Interface\\AddOns\\Cork\\templates\\SelfBufferAdvanced.lua:8\n UpdateMouseBinding = defined @Interface\\AddOns\\Cork\\Mousewheel.lua:11\n petunits =

{\n }\n keyblist =

{\n }\n MYCLASS = \"PRIEST\"\n classnames =

{\n }\n RegisterRaidEvents = defined @Interface\\AddOns\\Cork\\templates\\RaidBuffer.lua:59\n hasgroupspell = true\n IsSpellInRange = defined @Interface\\AddOns\\Cork\\Cork.lua:255\n config = {\n }\n colors =

{\n }\n RaidThresh = defined @Interface\\AddOns\\Cork\\Cork.lua:269\n IconLine = defined @Interface\\AddOns\\Cork\\Cork.lua:264\n defaultspc =

{\n }\n corks =

{\n }\n GenerateSelfBuffer = defined @Interface\\A", -- [2]
"ddOns\\Cork\\templates\\SelfBuffer.lua:7\n}\ndataobj =

{\n}\nValidUnit = defined @Interface\\AddOns\\Cork\\templates\\RaidBuffingItems.lua:11\n", -- [3]
},
["session"] = 5458,
["counter"] = 2,
}, -- [999]

Error repeats every time you click the macro button. Rendering it unreliable and useless if you happen to cast when not everyone in the raid is in the local vicinity. This has happened in every single weekly Baradin Hold raid since 4.3 (and prior) where I clicked the macro button, except for the last week. This past week, I waited until everyone in the raid was within 40 yards before attempting to use the macro. Only then did it work without bugging out.

I reported this exact same error back in October in WoW 4.2 in issue 66 (https://github.com/tekkub/Cork/issues/66), but didn't post/remember the details of when it occurred. Stopped clicking the Cork macro after it happened so let it slide and closed the ticket.. But have tried again in 4.3 and the bug is reproducible.