[Addon] Jamba - An assistant for Multiboxers - Release for WoW 6+

[Ughmahedhurtz]

OK, reproduced the "Won't turn in quests anymore" bug. It appears to happen when you complete the last item/kill on one of those auto-complete quests, such as Monstrosity in Jade Forest or the "An Urgent Plea" initial quest series. Once that pops and you click the bubble in the watched quests list (note: I am not using Jamba's quest tracker; I use the Blizzard one) to get the completion dialog to appear, it won't turn it in. And then every quest after that is broken for accept or complete. No LUA errors popped up, either. /console reloadui across all toons unstuck things, so it's a pretty easy workaround.

[edit] Got an LUA error this time.

Message: Interface\AddOns\Jamba-Quest\JambaQuest.lua:1300: attempt to call global 'WatchFrameAutoQuest_ClearPopUpByLogIndex' (a nil value)
Time: 10/24/14 22:30:22
Count: 8
Stack: Interface\AddOns\Auctionator\AtrErrorInspector.lua:106: in function <Interface\AddOns\Auctionator\AtrErrorInspector.lua:51>
(tail call): ?
Interface\AddOns\Jamba-Quest\JambaQuest.lua:1300: in function `DoShowQuestComplete'
Interface\AddOns\Jamba-Quest\JambaQuest.lua:2341: in function `JambaOnCommandReceived'
Interface\AddOns\Jamba\JambaCore.lua:348: in function `OnCommandReceived'
Interface\AddOns\Jamba\JambaCommunications.lua:425: in function `?'
...que\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147: in function <...que\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
[string "safecall Dispatcher[4]"]:4: in function <[string "safecall Dispatcher[4]"]:4>
[C]: ?
[string "safecall Dispatcher[4]"]:13: in function `?'
...que\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: in function `Fire'
...erface\AddOns\Jamba\Libs\AceComm-3.0\AceComm-3.0.lua:261: in function <...erface\AddOns\Jamba\Libs\AceComm-3.0\AceComm-3.0.lua:243>

Locals: <none>