There was a message in a MoneyFrameFix addon update today that said the problem had been fixed and the addon was no longer needed.
I removed the addon, and bugsack/buggrabber and all does in fact, seem to be well now …
For me anyhow, so far.
Fingers crossed !
That’s hilarious - I finally d/l the addon yesterday after suffering thru for a week plus - so I’ll hold it for a little bit because I don’t trust it’s really gone yet lol
As of 1/30/2026 at 4:15 cst it is not completely fixed. Still receiving the same error
Damn. not good news, I’ll keep going as I am and see if it re-surfaces, been doing Twilight content today so that may have an impact, trying a delve tomorrow will be a key test as it always tended to go belly up at the reward chests stage !
that is the standard box shelf response…”ask the wow community for help….check the forums”…their blizz help is overpaid for doing nothing but telling us to check wow forums and seek help from each other…wtf BLIZZ….we pay YOU for monthly services and we get crap in return
At least for me it seems like this issue has been fixed. I’ve seen other lua errors occasionally while running keys, but this was coming up during every single one and I did not see it at all today after running at least 10 keys.
I did that very thing. With the addon disabled, a few minutes in, eventually got the error. So no, not gone yet.
This bug appears to be fixed for me? I installed a couple of bug add-ons, which suppressed the errors, but they would still generate a message in the chat about too many errors and mousing over certain items wouldn’t show a tooltip.
However, since the most recent server maintenance, I haven’t seen either issue crop up.
I’ve done Delves and all kinds of stuff now and this particular issue does seem to have been extinguished for me. What a relief.
I did get one LUA error but that was just a fight at my Garrison banker involving BagBrother and something in playerMoneylua, and it didn’t keep repeating, so more of an addon conflict.
I suspect that mileage may vary now, depending on what add-ons are in use perhaps ?
Still seems to be happening for me as well as of 3’rd of February.
I’ve only been doing old Legion World quests for resources and still seems to break especially on old quests.
I’d like a fix please it’s been like this for weeks it’s annoying having to reload after every zone or quest. 
just to show you how much blizzard cares about it’s game..this error is still going on since Nov….all they care about is how much money is coming it it seems. if we skip buying midnight till they start fixing stuff..it will send a message!!!
On beta? Otherwise no it hasn’t.
Someone said do this:
Yeah, same thing here. Looks like there isn’t a fix yet!
This is a Lua taint error in World of Warcraft Retail’s built-in Blizzard_MoneyFrame code (specifically line 340 in MoneyFrame.lua).
It occurs when hovering over bag items (or other tooltip triggers like SetBagItem), as the game tries to display the item’s vendor sell price in the tooltip’s money frame (e.g., “4s 70c” for 470 copper).
WoW’s UI has “secure” (protected) frames and variables to prevent exploits in combat or restricted execution (e.g., action bars).
Addons can taint these, turning normal values into “secret” (unreadable) ones during certain operations.
Here, WorldQuestTracker taints the local silverWidth variable (used to size the silver coin button in the tooltip money display).
When MoneyFrame_Update runs, it tries arithmetic like width = goldWidth + silverWidth + spacing but fails because silverWidth is a “secret number value” (visible as in locals, but protected).
This bug exploded around January 2026 after a patch (likely tied to the Midnight expansion), affecting tooltips even with no addons in some cases—but addons like WorldQuestTracker, Bagnon, Auctionator, etc., trigger it reliably.
Update WorldQuestTracker: Download the latest from CurseForge. Recent versions (e.g., v12.0.0.547+) may have mitigations.
Disable WorldQuestTracker:
Exit WoW, rename its folder (WorldQuestTracker → WorldQuestTracker_disabled), relaunch.
Test by hovering bags—if errors stop, it’s confirmed.
Install a suppressor addon:
| Addon | What it does | Download |
|---|---|---|
| PlsFixMe Tooltips (v1.0.1, Jan 26, 2026) | Blocks silverWidth (and similar like textHeight, comparison tooltips) errors; fixes missing world quest/item tooltips. Temporary workaround—prices may not show in combat. |
Blizzard side: They’re aware (multiple forum threads), but no hotfix yet. Report yours: /console scriptErrors 1, reproduce, submit via in-game bug reporter.
Errors spam the chat but don’t crash WoW. Reload UI (/reload) after changes. If it persists without WQT, check other tooltip/quest addons (e.g., AllTheThings, Bagnon)
I ran the code through Grok and this is the response i got.
This isn’t entirely correct. I like many others have done fresh installs, no addons at all and running default settings. The errors still happen. Likely because the GUI is technically a built in addon and accesses the game/server files the same way as player addons do (this is the reason that its been so difficult to break certain addons, because they have to “green lite” their GUI while blocking player addon).
If you haven’t done a clean install and haven’t removed everything just reinstalled over what you already had it might still show up.
So to perform a clean install without reinstalling:
You will notice immediately that all addons have been removed, also any UI configurations you made will be reset.
This is the whole idea behind a clean install you do not want to have anything that can be causing errors left over in your configurations.
If you do plan on using addons start by installing:
BUGSACK and BUGGRABBER.
These two addons will help identify any addons which do break and cause taint.
From then on I would make sure that curse forge only installs one addon at a time if you have lots of them you use, that way you can see what is breaking the game.