Won’t be mildly annoying if I have to reload mid-pull during progress, is my worry.
Then it will be an active hinderance to my ability to play the game. I am not about to be benched over hecking AddOn support being stuffed in the blizzard jank bin.
Blizzard doesn’t support add-ons. I’m actually suprised they haven’t added a little disclaimer saying “use add ons at your own risk”. While they may allow their use they are the responsibility of the add-on writer.
If you want to yell at someone, yell at the add on creator. Until the time comes that Blizzard create their own add ons you can yell at Blizzard all day long. Won’t make a blind bit of difference.
Sorry, but in a Game with a whole “AddOns” section in the options and an “AddOns” section in the Game menu, I don’t buy that.
They support AddOns, hell they have essentially been relying on some for how they design the game it feels like.
This is absolutely on them, they know everyone uses AddOns in some capacity, AddOns have always been an integral part of World of Warcraft. If they “don’t support AddOns”, we wouldn’t have any.
They put the alert this thread is about in their game, not the people making the AddOns.
2 Likes
Then by all means. email Blizzard and ask them to fix the add ons.
Be sure to post their answer.
And that pull-down menu screen you talked about does nothing except give you the same options you have on the log-in screen.
It only allows you to either switch off a specific addon, switch on a specific add-on, disable them all, or reload them all. The only difference is that in the log in menu you don’t need to reload your UI in-game.
if you are talking about the add on section in the interface then that too is nothing to do with blizzard, that’s the add on creators who have given you those configuration options.
My understanding is that such errors are caused by “taint”, which is more of an issue now since the UI update causes the UI to be more interlinked than before.
I find the addon !!!NoTaint2 fixes most of these occurrences
1 Like
If they didnt support addons the API would not be accessible or published.
1 Like
Every time I level up I have to reload my ui as skills won’t work.
Weird thing is if it’s a macro it works fine!
blizzard coding is a joke…hire some normal coders not twitter activists
3 Likes
I’ve found that I only get the error if the blizzard ui and an addon overlap in some way.
Omg! So you’re saying it’s the same as every pre patch, and bliz is still making changes to the game… how bloody dare they.
How could anyone have forseen that, well… except its happened in every pre patch so far.
This was true for my one weakaura.
The only thing that caused this for me, was adding a WA that put tick markers on my cast bar for disintegrate, and only when I went to move the cast bar from being docked to my character frame.
After that, it worked just fine.
Wouldn’t surprise me if this is the case.
Which version of Elvui are you using? I keep getting an error message saying I should be using the PTR version.
I like your idea of delete the addon, it causes a problem of unfairnest against the people that do not run the addon, it will be unpleasance for them if they go into a pvp arena and have a dis anganvage.
You don’t say which addon is causing the issue. I used an addon called “buggrabber” to see which were the offending ones and promptly removed them. The problem is not only the addon creators but the changes blizzard made. The best solution for now and to make the game playable is to run with only really essential WORKING ones until they can be fixed. Hopefully this can be achieved before DF launches and most definitely by the time the raids and season starts.
People in the comments usually have fixes for errors, so I would suggest reading the comment section of the addon on curse forge, even if the addon is up to date,
Also, download bugsack.
13.01 I think? I update it reasonably often
1 Like
Current version is 13.06 - download it then delete the files from your folder before you copy and paste the new files. Do not overwrite them- you will not lose your configuration of the addon as this is stored in the WTF folder. Should solve most of your errors you getting but there are still a few bugs like the spell flyouts as this is a blizzard problem not the addon.
World of Warcraft_retail_\WTF\Account<numbers>\YourRealmName Click and and drag folder with the character name you set up all addons with to desktop after that delete WTF and Cache folder.
Go in to Battle.net click cogwheel next to Play button and press Scan and Repair, when done replace the folder you dragged to desktop.
This should fix the issue, i’ve had it myself several times… i think it’s due to old files that’s leftover after patches to game and updates to addons.
I hope it helps.
Bump to revive the topic because this is still an issue. My AddOns are:
- Details!
- HandyNotes
- Pawn
- OmniCC
- Musician
- Total RP 3
- Plater
- WeakAuras
- Deadly Boss Mods (and all modules)
- Bagnon
- BugGrabber
- BugSack
Every single one of these addons have at some point caused a blocked action on completely unrelated things. Bagnon, in particular, is blamed for blocked actions when using racials like Soar and Running Wild.
BugSack and BugGrabber have also been blamed for blocking action bar actions (but clicking in the spellbook works just fine).
I have managed to get blocked actions for each individual AddOn while I’ve tried to isolate the cause; in these test cases, only the AddOn being tested was active & the rest were disabled.
I’m convinced it’s the new GUI editor that causes these problems as it is the most common problem being pointed out by the LUA errors; it’s either tainting random variables or causing some kind of breakdown in the API.
The way it’s acting makes it abundantly clear that it’s not intended behaviour. I’m honestly aghast that it hasn’t been addressed yet.
Edit: I should point out I am also using a freshly downloaded copy of the game, on a brand new computer which has never had WoW installed on it before.
All AddOns are also up to date.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.