If I open another tradeskill and then try to click the engineering button in Skillet, it throws this error specifically
1x [ADDON_ACTION_FORBIDDEN] AddOn 'Skillet' tried to call the protected function 'CastSpellByName()'.
!BugGrabber\BugGrabber.lua:519: in function <!BugGrabber\BugGrabber.lua:519>
[C]: in function `CastSpellByName'
Skillet\Skillet-4.10.lua:1709: in function `SetTradeSkill'
Skillet\UI\MainFrame.lua:529: in function `TradeButton_OnClick'
[string "*:OnClick"]:2: in function <[string "*:OnClick"]:1>
Any other profession seems to work fine
Did Blizzard do anything with Engineering (or any other professions) in 8.2.5?
If you can type "/skillet debugshow", try again, and then let me know what the last few lines are in chat that might help, (and then "/skillet debugshow" to turn it off).
In the meantime, I'll go see if my engineer is having similar issues.
Skillet is working fine with my engineer.
I believe it's related to this issue as I was experiencing issues with OPie as well: https://www.curseforge.com/wow/addons/opie/issues/264
The problem specifically occurs if I have Skillet already open for another profession and attempt to switch to Engineering using the Skillet buttons above the skill level.
Running "/skillet debugshow" I get the following lines:
Skillet: SetTradeSkill(Itamae, 4036, nil)
Skillet: SetTradeSkill: orig= Engineering (4036), spell= Engineering (4036)
and then I get an error saying Skillet has been blocked from an action only available to the Blizzard UI. This doesn't happen with any other profession, like if I go from Enchanting to Cooking, it works just fine.
I have this same issue, also using OPie to open Skillet. I can open Cooking through Skillet, but then when I try to switch to engineering Blizzard blocks it like described in the comment above. Same happened for Tailoring if I recall correctly.
I can open the Skillet engineering window by going through the Blizzard professions UI.
Blizzard is fucking with us in 8.2.5! I'm getting this error on random switches between professions. If I log off and log on again (same character), the problem is gone.
I don't believe Skillet is at fault here so I'm closing this issue.
To post a comment, please
or register a new account.