'for' limit must be a number
Predatorie opened this issue ยท 2 comments
Bug description
Logged into the game, hovered over the Active Quests list and the error was thrown as shown below. Reloading UI does not stop the error.
I have 20 quests in my active list.
Let me know what other additional information you might need.
Stack Trace
Message: ...ce\AddOns\Questie\Modules\Tracker\QuestieTracker.lua:791: 'for' limit must be a number
Time: Wed May 6 12:59:50 2020
Count: 1
Stack: ...ce\AddOns\Questie\Modules\Tracker\QuestieTracker.lua:791: 'for' limit must be a number
...ce\AddOns\Questie\Modules\Tracker\QuestieTracker.lua:791: in function <...ce\AddOns\Questie\Modules\Tracker\QuestieTracker.lua:783>
Interface\SharedXML\C_TimerAugment.lua:16: in function <Interface\SharedXML\C_TimerAugment.lua:14>
Locals: (for index) = 1
(for limit) = nil
(for step) = 1
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "'for' limit must be a number"
_QuestieTracker =
ItemButtons =
}
StartFadeTicker = defined @interface\AddOns\Questie\Modules\Tracker\QuestieTracker.lua:781
baseFrame = {
}
CreateActiveQuestsFrame = defined @interface\AddOns\Questie\Modules\Tracker\QuestieTracker.lua:416
expandButton = {
}
GetNextItemButton = defined @interface\AddOns\Questie\Modules\Tracker\QuestieTracker.lua:776
PrintProgressColor = defined @interface\AddOns\Questie\Modules\Tracker\QuestieTracker.lua:1040
GetNextLine = defined @interface\AddOns\Questie\Modules\Tracker\QuestieTracker.lua:769
FadeTickerDirection = true
menuFrame = QuestieTrackerMenuFrame {
}
OnDragStop = defined @interface\AddOns\Questie\Modules\Tracker\QuestieTrackerPrivates.lua:38
LineFrames =
}
FadeTicker =
}
SetSafePoint = defined @interface\AddOns\Questie\Modules\Tracker\QuestieTracker.lua:308
activeQuestsFrame = {
}
IsFirstRun = true
OnDragStart = defined @interface\AddOns\Questie\Modules\Tracker\QuestieTrackerPrivates.lua:14
FadeTickerValue = 0.060000
}
Questie version
v5.10.2
Duplicate of #1868
We're targeting this issue for the next release. Unfortunately it is just not that easy to debug.