I cleared my entire addons folder.
There is nothing in there and I still got errors
2 Likes
Troll? So you relayed your bug report in the bug forum and then are complaining here?
And I’m the troll? 
Try reading the post 
Hope this helps! It’s not that many words, I believe you can do it!
3 Likes
I’m merely confirming what someone else said, and you’re trolling about it. So yes, you’re the troll. And now you’re blocked.
1 Like
Oh I read it alright. Still sounds like the group of posters in this chat don’t know the contents of their own addon subdirectories.
Try running “Scan and Repair” after you’ve dumped your addon folder. I believe you can do it!
That did precisely squat in my case. I reinstalled the entire game after nuking every Blizzard product from my machine. I’m still getting errors from Blizzard_MoneyFrame while in combat. At this point I wish I could modify those files, since all it needs is a simple conditional to query the combat state around that line. That check should still be safe.
2 Likes
You’ll find there are two types of trolls on these forums.
One type will want to bash Blizzard even when they do good or necessary things.
The other will want to defend them even when it’s clearly their own problems that are coming up here.
You’re dealing with one of the latter types.
1 Like
I haven’t seen any LUA errors pop up but this was common on the beta.
Blizzard probably writes their own LUA code for high level functions like the UI. It appears that they use the same API that we use. I remember when I was writing my addon trying to call AI routines and getting a message saying that users were not allowed to use some of the routines in the API.
Obviously if they are in the API and users can’t use them they must be there for Blizzard developers.
1 Like
Some setting is corrupted in your game I’ve been playing for hours in several different combat scenarios: M+ delves PVP raids open world
Changed settings around - nothing. It is likely you and the several other people on this thread all had a certain addon that changed hidden settings in the game. And now that that certain addon is borked, it was unable to reset the defaults before it was uninstalled.
Also I want to address the people throwing out that I’m a troll. You need to really think about what you are assuming and accusing Blizzard of here: You’re convincing yourself that Blizzard has knowingly release a bug in its Lua parser that’s causing errors and has yet to announce or release a hotfix for it.
If that is really true that parser error should be happening for the entire player base. Which it is not.
So what’s more likely is the a subset of the player base all had a particular addon that changed hidden settings to the game and were never undone prior to the addon borking patch.
There would be a thread on the forums with 10s of thousands of replies if it were as you accuse Blizzard of because if it always comes up in combat - which is the primary activity in the game - then it would be game breaking and halting for everyone.
Addon changes are stored in plain text CVar files. I wiped those while doing a full UI reset prior to reinstalling, according to Blizzard’s own documentation. Addons aren’t the issue here, Blizzard’s incompetence is. The fact that you’re not having issues means nothing. I had a persistent issue where whenever this character would join a raid, my raid frame would just disappear. I use no unit frame addons and have been on the base UI this entire expansion. No one else had that particular issue, but the reinstall did sort that out, so it wasn’t for nothing.
1 Like
By default, the scriptErrors 0 CVar is set, so you often don’t see when things break. Try setting /console scriptErrors 1 then come back here and say you’re not having issues.
1 Like
Yep typed in the console and I’m currently doing timewalking as Brewmaster, no errors and on 3rd boss of Freehold.
Update: finished it with no errors.
Then I wish I’d have your luck, you seem to be the only one with a pristine copy of WoW free from Blizzard’s idiotic “secret value” errors.
1 Like
It’s more likely that I didn’t give into peer pressure and downloaded some addon that changed settings in the game that I have no way of changing or resetting back to baseline myself than having a “pristine copy of WoW”
I’m wondering if it has something to do with being a fresh install or not. I didn’t personally run into this on the beta, but the beta was a clean install, whereas my live version of the game was just an update…
I’m not really sure, but I do know I haven’t had a single LUA error so far other than the Renown thing popping up and not going away.
Mine is more subtle (but hidden because I expected errors because new patch lol)…basically after downing a couple bosses in raid, when going to compare the drops to what I’m wearing, or while inspecting another player (to find out if I’m going to need roll against their need roll or pass and let them have it) …occassionally the UI refuses to show me some of the gear in question (either my gear, or the other player’s gear, or the item that just dropped) until I /reload.
It’s not a huge deal, takes all of about 20 seconds, but it is a very obvious bug, and when I check the error code in BugSack, it’s the same Blizzard_Moneyframe issue OP was talking about here.
3 Likes
Update after playing a bit today: this tentatively might have been resolved. I haven’t had this bug pop up yet today. Fingers crossed.
I manually turned off all addons but Bartender and haven’t gotten another error since.