i keep getting this error every 15-20 minutes that forces me to reload. what is going on? it’s not just handynotes doing it too, i get the same error from atlas, bagnon, etc
19 Likes
Errors with the addons and your WTF folder.
You have two options: wait for more addon updates or try deleting the WTF folder and starting over to see if some of the saved variables are giving you issues.
2 Likes
I am not sure if it’s related.
What’s the best Coord mod to use right now?
2 Likes
I’ve been using TomTom without any issues
2 Likes
Tontom freaks out when I try to use anything in my bags. Despite all these addons supposedly being up to date they are clearly not.
9 Likes
I tend to find if you delete the add-on’s folder (as opposed to just overwriting the existing folder) before updating you end up with fewer errors.
You might also need to delete the add-on’s .lua files in the WTF folder, although this will reset the add-on to its defaults.
4 Likes
Are your addons updated?
I know your Atlas isn’t updated since there is no up to date version of Atlas 
3 Likes
Keep in mind it’s not always the addon that it claims it is.
Like, LeatrixMaps constantly gives me an error with my action bars every so often, preventing me from using any skills. So I disabled it - error popped up again a bit later from another addon.
Disabled that. Error hasn’t been back. Re-enabled Leatrix Maps. Error hasn’t been back so far.
6 Likes
I’ve had that happening off and on throughout Shadowlands. Just a random addon being blamed for it. Usually it’d just keep me from using an item for a quest or depositing Anima, but a /reload would fix it. Sometimes it’d prevent me from using the ExtraActionButton, which was real fun on fights like Eye of the Jailer.
Since the patch though it’s done that when just trying to hit a keybind in Blizzard’s default UI. Only addons I’ve noticed it saying the past couple days is WeakAuraOptions or Bagnon.
4 Likes
I occasionally get that from TomTom. I’ve noticed it most often when I try to open my quest log while I’m in combat by just clicking on the quest from the objective tracker (instead of hitting the hotkey). I haven’t really dug further than that though since a reload clears any issues.
3 Likes
Well i guess now is as good a time as ever to stop the update cycle. Time to clean the house and reinstall them.
2 Likes
I’m getting this kind of error from a few different addons that are up-to-date. I’m not convinced it’s the addons. Even my home brewed addons sometimes clash with the stock UI and I write clean, basic code. The error gets thrown a couple of times and then stops. I have buggrabber and bugsack to catch and hold my errors.
6 Likes
I’m fairly sure that it happens when Wow recognises that you’ve changed a variable (or maybe called a function) that Blizzard has ‘protected’. It happens in my custom addons as well.
For example, If I remove the line ‘MainMenuBar.addButtonsToTop = false’ from my actionbar addon, there are no more errors.
It has to stem from a change, either intended or not, in the way they handle access to their private code.
2 Likes
I’m seeing this error from multiple addons as well. Most recently Datastore_quests.
3 Likes
Also getting this error - it never shows up when first logged in, but after a little playing it will just randomly show up. It’s inconsistent which addon it blames, but it’s always wrong. Reloading makes it work for a short time, then it blocks actions again.
It would be nice if they would fix this… but they’ll just blame the addons, even though it’s clearly a problem they’ve introduced in the new UI.
8 Likes
Yeah, I do tend to think it’s a Blizzard issue of some sort. This error will pop up when I’m doing things that aren’t related to the addon. I’ve also seen it come up after I’ve done X thing several times, and then suddenly there’s an issue. For instance, the other day I was upgrading some of my battle pets. I used 4 upgrade stones out of my bags without issue, but suddenly on the fifth one this error came up with an addon. It made no sense.
5 Likes
What I had to do I delete all my add-ons than wait I then had to look at when it was updated. I decided that I would not be using all my prev add-ons because they mess with the new ui code…now I need only have 3 add-ons that have nothing to do with the ui just my ilvl…immersion pawn and that s it…not getting anymore annoying Lua errors
2 Likes
Having this issue out the wazoo since prepatch. I’d have it randomly in the past (one in a hundred times something would mess with mission tables and I’d reload, or mogging), but lately I can almost never use any items without moving them to my backpack first, sometimes I can’t use my keybinds (but can click spells?) without reloading. Sometimes it blames handynotes, sometimes TSM, sometimes better wardrobe, all updated addons. Probably some old addon somewhere messing with it, but I’ve never had this issue in 14 years of playing off and on.
Just went through and deleted some ancient addons and reinstalled some possibly corrupt ones, so we’ll see.
Edit: It did not, in fact, work lol. All updated 10.0 addons and still being screwy
3 Likes
It seems like Blizzard expanded their list of restricted functions.
This error happens when the UI realizes it’s been changed in a way that it disallows. It’s called taint, and it will clear on a /reload until it’s detected again.
Many addons are having problems working around this, due to many relying on now-blocked code.
4 Likes
Also wanted to say that I’ve had MANY addons have this same issue. (Details, Raider.io, TSM, SilverDragon, Accountant, Altoholic, Global Ignore List, Handynotes, and Prat to name the ones I can remember off the top of my head)
It cannot be just an ‘addon issue’ because too many of them are having this problem. There’s something Blizzard has done and honestly it would be nice to have some transparency about it to help addon creators fix this.
8 Likes