b-morgan
commented
1 year ago You have encountered my biggest frustration... the event UNIT_SPELLCAST_FAILED_QUIET tells me nothing about "why" it failed. I'm guessing that Blizzard didn't like the contents of "{table}". Please add a couple more commands, "/skillet tabledump on" and "/skillet debuglevel 4". These two commands will generate a lot more "spam" in chat.
Skillet also logs the chat output to a size-limited table in memory (when full, the oldest output is deleted as newer output is added). This table is written out to the character specific saved variables file, Skillet.lua, when you logoff or "/reload". "/skillet debugshow off" will stop the chat "spam" but you need "/skillet debuglogging off" to stop the output to the in memory table. You can check the state of Skillet's debugging with "/skillet debugstatus".
You can post a zip of the character specific saved variable file here (GitHub won't take .lua files).
Once the contents of {table} is revealed, I can determine what Skillet did wrong in creating it and hopefully fix it. I will need your help because my Jeweler is only level 47. In the mean time, I'll do some testing with my Engineer and see if a similar failure occurs.
Shaderx
5.04 Alpha 1 en-US
Cast bar succeeded but item not created.
Any idea why?
On further testing, creating the amulet by itself when i have all the mats will still queue a shimmering clasp. Creating a shimmering clasp in skillet by itself works. Queueing the amulet and then deleting the excessed queue shimmering clasp then starting the queue works. Starting the queue with the additional shimmering clasp gives the above error.