CandyUI_Datachron
Mae-Is-Mean opened this issue · 10 comments
Error popped up on my engy when I got a quest
...dStar\Addons\CandyUI_Datachron\CandyUI_Datachron.lua:292: bad argument #1 to 'QueueNextCall' (number expected, got nil)
stack trace:
[C]: in function 'QueueNextCall'
...dStar\Addons\CandyUI_Datachron\CandyUI_Datachron.lua:292: in function <...dStar\Addons\CandyUI_Datachron\CandyUI_Datachron.lua:287>
Also, the graphics are kinda goofy on the datachron now that it's anchored to the minimap. My scientist bot info is under the actual datachron, and it covers the quest helper so you cant really leave it open if you want to.
Yeah I'm trying to figure out a way to make it less obtrusive. Any ideas
you have would be great
On Thu, Oct 2, 2014 at 11:14 PM, Mae-Is-Mean notifications@github.com
wrote:
Error popped up on my engy when I got a quest
...dStar\Addons\CandyUI_Datachron\CandyUI_Datachron.lua:292: bad argument
#1 #1 to 'QueueNextCall'
(number expected, got nil)
stack trace:
[C]: in function 'QueueNextCall'
...dStar\Addons\CandyUI_Datachron\CandyUI_Datachron.lua:292: in function
<...dStar\Addons\CandyUI_Datachron\CandyUI_Datachron.lua:287>Also, the graphics are kinda goofy on the datachron now that it's anchored
to the minimap. My scientist bot info is under the actual datachron, and it
covers the quest helper so you cant really leave it open if you want to.—
Reply to this email directly or view it on GitHub
#37.
Got the same error after handing in my daily crafting quest in Thayd. This error cropped up about 5 seconds later.
I'm also working on making a new minimap because the stock one is sort of tied into the datachron
The datachron isn't spitting errors anymore, but it does still not look right for scientists. The bot info is not in the right spot and ends up off-frame.
This is not fixed on the update posted 11/28. I tried the files here and the ones on Curse, both still have this same bug.
maybe i got the files mixed up with an older version
ill double check everything and fix the problems if i need to . Thanks!
On Fri, Nov 28, 2014 at 10:22 PM, Mae-Is-Mean notifications@github.com
wrote:
This is not fixed on the update posted 11/28. I tried the files here and
the ones on Curse, both still have this same bug.—
Reply to this email directly or view it on GitHub
#37 (comment).