Cannot use items with latest update
ThatGuy116 opened this issue ยท 15 comments
The latest update has blocked the function to use items in your bag. Like making the Obsidian Keys etc.
I can confirm the op. I'm no longer allowed to use consumables or Knowledge Point items directly from the bags. Have to move them to an action bar and use. This just started happening after I updated Bagnon last night.
I'm also having trouble with USE items in my bag. I receive this msg: :: "Bagnon has been blocked from an action only available to the Blizzard UI. You can disable this addon and reload the UI." A simple solution (until the issue can be fixed): Click and drag the item to an open slot on one of your bars, then right click to USE. If, after use, a greyed-out icon is still on your bar, simply click, drag, and remove it. Hope this helps.
i also cannot use any item in my inventory that requires a right-click action to proceed; I receive this msg: "Bagnon has been blocked from an action only available to the Blizzard UI. You can disable this addon and reload the UI."
If it is one of those "right-click to open for loot" items, it's fine; but any other item - anything that is 'applied' by right-clicking (buffs, potions, porting items, seeds - any xpac, on any continent, in any profession) - literally anything you have to right-click to use, will get this error.
Date: 2022-12-10 21:21:34
ID: 23
Error occured in: AddOn: Bagnon
Count: 1
Message: Error: AddOn Bagnon attempted to call a forbidden function (UNKNOWN()) from a tainted execution path.
Debug:
[string "=[C]"]: ?
[string "=[C]"]: ?
[string "=[C]"]: UseContainerItem()
[string "@Interface/FrameXML/ContainerFrame.lua"]:1409: ContainerFrameItemButton_OnClick()
[string "@Interface/FrameXML/ContainerFrame.lua"]:1461:
Interface/FrameXML/ContainerFrame.lua:1448
[string "=[C]"]: ?
Locals:
None
#1579 might be the cause of all of this.
I noticed the same with Awakened reagents - can't transform with the addon on :/
the problem is taint - certain functionality is only allowed for Blizzard code within certain context - e.g. combat.
If Addon code tries to do functions that the game believes to breach thos rules it will bock it. Unfortunately the detection is not foolproof. In this case a default code got tainted so any normal addon like Bagmon using it gets blocked even though it is "normal" use. (I hope i kinda got it right).