Closed KnockUser closed 1 year ago
I cannot reproduce this issue and I have examined the code changes between 1.67 and 1.68 (and 1.69) and can find nothing that might cause this problem. Please download Skillet-Classic-1.69-wrath, verify the MD5 checksum, install, and test again.
If it still fails, please verify that it fails when Skillet-Classic is the only addon enabled. Please make a backup of your global saved variables file, Skillet-Classic.lua, and then type "/skillet flushplayerdata" or "/skillet flushalldata" (you can also delete the global saved variables file).
I will provide instructions on enabling debug output and uploading it if necessary.
Thanks, using v1.69 with no other addons worked here. By then going through the few other addons I use, it's a conflict with Auctionator. Having just that & Skillet enabled throws up the following error:
25x ...rfaceSkillet-Classic/Plugins/Auctionator.lua:509: attempt to index field 'API' (a nil value)
[string "@Skillet-Classic/Plugins/Auctionator.lua"]:509: in function <...rfaceSkillet-Classic/Plugins/Auctionator.lua:482>
[string "@Skillet-Classic/Plugins/Auctionator.lua"]:885: in function GetExtraText' [string "@Skillet-Classic/SkilletPlugin.lua"]:174: in function
GetExtraText'
[string "@Skillet-Classic/UI/MainFrame.lua"]:1976: in function UpdateDetailsWindow' [string "@Skillet-Classic/UI/MainFrame.lua"]:963: in function
UpdateTradeSkillWindow'
[string "@Skillet-Classic/UI/MainFrame.lua"]:2511: in function ScrollToSkillIndex' [string "@Skillet-Classic/Skillet.lua"]:1539: in function
SetSelectedSkill'
[string "@Skillet-Classic/UI/MainFrame.lua"]:2432: in function `SkillButton_OnClick'
Locals: recipe =
Version 1.68 for Wrath appears to be causing the queue window to remain empty when adding create or queue jobs to it (regardless of the type or number of operations).
These jobs are visible if Skillet is closed and reopened but I was unable to make them display without this step. I tried adding additional jobs or clearing and then adding new tasks - no success.
Restarting the game client did not fix the problem. Rolling back to v1.67 and restarting resolved this problem.