I can confirm this bug. Only started this past week end though. My latest addon additions are Altoholic and related DataStore items. Will try disabling those and see if the error still occurs
EDIT: Removing Altoholic et al doesn't resolve this, and I now get the failure on entering the world - I was only getting it on update/NPC interaction previously. Error follows:
Let me know if you want someone to test things for you, Jafula.Code:Message: ...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:909: bad argument #1 to 'find' (string expected, got nil) Time: 11/08/10 09:49:33 Count: 1 Stack: [C]: in function `find' ...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:909: in function `GetQuestObjectiveCompletion' ...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1017: in function <...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1005> (tail call): ? [C]: ? [string "safecall Dispatcher[2]"]:9: in function <[string "safecall Dispatcher[2]"]:5> (tail call): ? ...face\AddOns\Jamba\Libs\AceTimer-3.0\AceTimer-3.0.lua:164: in function <...face\AddOns\Jamba\Libs\AceTimer-3.0\AceTimer-3.0.lua:138> Locals: <none>
Connect With Us