I’ve been playing Wow for 16 years and I’ve never seen anything like this. Every time there’s a new patch and I do M+ I have to figure out what Addon is giving me LUA Error. I only use the most basic addons like Bartender, Raider IO and that’s pretty much it. However I have to wait like 1-2 weeks before it all magically works out no matter how often I download the newest version.
The way you broke the addons is beyong annoying. Not paying my resub for the next month because you don’t really care about player experience. Thank you for your attention to this matter
7 Likes
If you are seeing errors in addons then you might want to take this to the UI and Macro forum. That’s where the addon people hang out.
Developers don’t read this forum. When you enter notes here you are talking to players having a general discussion. To talk to the devs you need to file a ticket.
1 Like
A lot of the time its not even an addon, its WoWs own UI calling on secret errors because Blizzs left hand doesnt know what its right is doing.
9 Likes
It is the addon, but on Blizzard’s own fault. And if you want to stop getting LUA Errors boxes, install the BugSack and the BugGrabber addon (need both). What it does is transfer those LUA boxes into chat messages or sound which you can turn off.
Addons creator right now are attempting to code their ways around the new API and it’s limitations. It is a vague new system that hides a lot of useless stuff. Hell, some stuff is hidden to addons but not on the base UI, like grouping. If someone joins or leaves the group and you have a UI addon while in combat, you don’t see it until the fight is over.
That causes a lot of LUA errors because the API apparently seem to be constantly changing, but mostly because most addons were using the Combat system API to make their code work because it was the easiest way to do it, even tho it wasn’t necessarily a combat addon. Now they have to make another completely different way allow their addons to do the same thing
5 Likes
Yeah this is pretty much a must right now, especially if you’re doing any sort of challenging group content. Even trying to use the console command that normally suppresses them only seems to last a few seconds, or not at all. But those two add-ons work great together, and are a lifesaver this week.
Get Bug Sack and Bug Grabber add-ons, then you can ignore Lua errors until after the M+ run.
I will say it’s ironic to have to download a related pair of add-ons because Blizzard broke something and makes their own (and 3rd party) add-ons throw more Lua errors than a 2-year old throwing a tantrum.
1 Like
With all addons off, every time last boss in m+ dies error screen pops but with no text. Blizzard own ui is broken, what a mess of expansion and it is all blizzards doing.
1 Like
Make sure you are using bugsack and buggrabber.
While they’re primarily used by addon developers, they can also show you which addon (if any) is causing a lot of issues so you can disable it, which is especially useful for dealing with the ‘your addons are causing many LUA errors’ popup.
For the smaller Blizzard UI LUA errors, I’ve noticed that bugsack and buggrabber being installed has mostly minimised the amount of errors I run into; all I hear is a little chirp that says ‘vitality’ when a bug gets grabbed, and if that annoys you, you can mute it in the settings.
Borderline killed our raid tonight.
And it’s ignore or disable. There’s too many to ignore and disable does what it says forcing you to manually turn them back on one by one.
I’m really only getting errors from DCS at this point.
I’ve disabled all addons and still get spamemd to unholy hell in certain raid environments and rarely in keys. There USED to be an option to disable LUA errors but it appears to be gone now.
Fixing THIS is a higher priority in my world than most any other nonsense people are harping on about. Like it’s beyond dumb your base game 0 addons should ever be giving players errors. Like that is basic testing 101.
1 Like
See above. Get Bug Sack and Bug Grabber from curseforge.
Those two addons will make sure that if it’s actually an addon causing the problems, you know exactly which one it is so you can disable it or go get it updated if there’s a new version out.
Hiding the problem does not fix the problem.
It’s not hiding the problem.
Bug Sack and Bug Grabber will, as I quite literally said, show you which addons are causing the LUA errors. Then you can either disable that addon specifically, or you can search to see if the addon has been updated and download the update.
We still get LUA errors even when all addons are disabled (except BugGrabber and BugSack to capture the stuff).
The errors come from Blizzards own LUA code baked into game data, primarily on world map and tool tips). The LUA from most addon developers has far better code quality than what Blizzard produces themselves.
The most concerning fact is that the errors report they come from using secrets when not in combat at all or accessing stuff which has nothing to do with combat (like gear tooltip info or loot sell values).
Just stop using secret values for stupid stuff like item vendor prices or WQ rewards. I don’t see how these secret values can be exploited to make combat easier.
Having to use buggrabber/bug sack to avoid the companies own coding problems is such a clown moment.
1 Like
Yes - install new addons to mitigate the bugs caused by Blizzard’s plan to make addons less important.
I now have more addons in Midnight since ever before.
ERROR #1: No notes:
Message: …AddOns/Blizzard_GameTooltip/Mainline/GameTooltip.lua:754: attempt to perform arithmetic on a secret number value (tainted by ‘*** ForceTaint_Strong ***’)
Time: Sat Apr 18 00:36:17 2026
Count: 1
Stack:
[Interface/AddOns/Blizzard_GameTooltip/Mainline/GameTooltip.lua]:754: in function ‘EmbeddedItemTooltip_UpdateSize’
[*GameTooltip.xml:96_OnSizeChanged]:1: in function <[string “*GameTooltip.xml:96_OnSizeChanged”]:1>
[C]: in function ‘GetWidth’
[Interface/AddOns/Blizzard_GameTooltip/Mainline/GameTooltip.lua]:754: in function ‘EmbeddedItemTooltip_UpdateSize’
[Interface/AddOns/Blizzard_GameTooltip/Mainline/GameTooltip.lua]:837: in function ‘EmbeddedItemTooltip_SetItemByQuestReward’
[Interface/AddOns/Blizzard_FrameXMLUtil/Mainline/QuestUtils.lua]:823: in function ‘QuestUtils_AddQuestRewardsToTooltip’
[Interface/AddOns/Blizzard_GameTooltip/Mainline/GameTooltip.lua]:209: in function ‘GameTooltip_AddQuestRewardsToTooltip’
[Interface/AddOns/Blizzard_GameTooltip/Mainline/GameTooltip.lua]:727: in function ‘GameTooltip_AddQuest’
[Interface/AddOns/Blizzard_UIPanels_Game/Mainline/WorldMapFrame.lua]:176: in function ‘TaskPOI_OnEnter’
[Interface/AddOns/Blizzard_SharedMapDataProviders/WorldQuestDataProvider.lua]:421: in function <…rd_SharedMapDataProviders/WorldQuestDataProvider.lua:420>
Locals:
self = Frame {
itemTextureSet = true
IconOverlay2 = Texture {
}
count = 1
isCraftedItem = false
Text = FontString {
}
FollowerTooltip = GameTooltipGarrisonFollowerTooltip {
}
isProfessionItem = false
yspacing = 13
IconOverlay = Texture {
}
Count = FontString {
}
IconBorder = Texture {
}
itemID = 257022
Tooltip = GameTooltipTooltip {
}
Icon = Texture {
}
}
itemTooltipExtraBorderHeight = 22
(*temporary) =
(*temporary) =
(*temporary) = Texture {
}
(*temporary) =
(temporary) = nil
(temporary) = nil
(temporary) = "attempt to perform arithmetic on a secret number value (tainted by ’ ForceTaint_Strong ***')"
ERROR #2: When rolling over “Ritual Site: Daggerspine Point” on the full-screen World Map pane:
Message: …/Mainline/Blizzard_UIWidgetTemplateTextWithState.lua:35: attempt to perform arithmetic on local ‘textHeight’ (a secret number value, while execution tainted by ‘*** ForceTaint_Strong ***’)
Time: Sat Apr 25 19:23:14 2026
Count: 1
Stack:
[Interface/AddOns/Blizzard_UIWidgets/Mainline/Blizzard_UIWidgetTemplateTextWithState.lua]:35: in function ‘Setup’
[Interface/AddOns/Blizzard_UIWidgets/Mainline/Blizzard_UIWidgetManager.lua]:526: in function ‘ProcessWidget’
[Interface/AddOns/Blizzard_UIWidgets/Mainline/Blizzard_UIWidgetManager.lua]:562: in function ‘ProcessAllWidgets’
[Interface/AddOns/Blizzard_UIWidgets/Mainline/Blizzard_UIWidgetManager.lua]:275: in function ‘RegisterForWidgetSet’
[Interface/AddOns/Blizzard_GameTooltip/Mainline/GameTooltip.lua]:588: in function ‘GameTooltip_AddWidgetSet’
[Interface/AddOns/Blizzard_FrameXMLUtil/AreaPoiUtil.lua]:44: in function <…terface/AddOns/Blizzard_FrameXMLUtil/AreaPoiUtil.lua:3>
[tail call]: ?
[Interface/AddOns/Blizzard_SharedMapDataProviders/AreaPOIDataProvider.lua]:166: in function <…zzard_SharedMapDataProviders/AreaPOIDataProvider.lua:159>
Locals:
self=Frame <Blizzard_UIWidgetManager.lua:432>{
tooltipLoc=0
tooltipYOffset=0
widgetType=8
tooltipContainsHyperLink=false
tooltip=“”
widgetID=8043
widgetContainer=Frame GameTooltip.lua:580
tooltipAnchor=“ANCHOR_BOTTOMLEFT”
FadeInAnim=AnimationGroup <Blizzard_UIWidgetTemplateBase.xml:16>
disableTooltip=true
scriptedAnimationEffectID=0
modelSceneLayer=0
layoutDirection=1
outAnimType=0
inAnimType=0
widgetTag=“”
orderIndex=201
widgetSetID=2101
defaultTooltipAnchor=“ANCHOR_BOTTOMLEFT”
hasTimer=false
FadeOutAnim=AnimationGroup <Blizzard_UIWidgetTemplateBase.xml:23>
Text=FontString <Blizzard_UIWidgetTemplateTextWithState.xml:7>
tooltipXOffset=0
}
widgetInfo={
scriptedAnimationEffectID=0
modelSceneLayer=0
widgetScale=0
tooltipLoc=0
fontType=0
shownState=1
widgetSizeSetting=300
bottomPadding=5
enabledState=1
textSizeType=0
text="
Field Accolades are awarded for disrupting Ritual Sites. "
orderIndex=201
layoutDirection=1
inAnimType=0
widgetTag=“”
hasTimer=false
outAnimType=0
tooltip=“”
hAlign=0
}
widgetContainer=Frame GameTooltip.lua:580{
horizontalAnchorXOffset=2
verticalAnchorPoint=“TOPLEFT”
disableWidgetTooltips=true
widgetFrames=
horizontalRelativePoint=“RIGHT”
verticalAnchorYOffset=0
shownWidgetCount=0
dirty=false
widgetSetLayoutDirection=1
numWidgetsShowing=0
numTimers=0
timerWidgets=
horizontalRowContainerPool=
widgetPools=
BackModelScene=ModelScene <Blizzard_UIWidgetManager.xml:46>
FrontModelScene=ModelScene <Blizzard_UIWidgetManager.xml:33>
verticalRelativePoint=“BOTTOMLEFT”
widgetSetID=2101
horizontalAnchorPoint=“LEFT”
showAndHideOnWidgetSetRegistration=false
}
textHeight=
(*temporary)=5
(*temporary)=0
(*temporary)=0
(temporary)=1
(temporary)=0
(temporary)="attempt to perform arithmetic on local ‘textHeight’ (a secret number value, while execution tainted by ’ ForceTaint_Strong ***')"