Addons only get “blocked” for being out of date, and the game’s version didn’t change (TOC 100107). If addons are out of date, they either need to be updated if an update is available, or if not, you can test them by loading out of date addons, and if they work update the TOC files manually.
Altoholic in particular is only updated for 10.1. But on their discord they have new files posted that make it work with 10.1.7 (though you have to edit the TOC files if you don’t want to load outdated addons). I recommend the UI and Macro forum if you need more information.
How addons interact with the game is not a bug. If add-ons are experiencing issues, then the add-on author needs to find out what is causing it, and adapt their add-on.
The client is never going to be patched to allow add-ons. Add-ons must function within the LUA sandbox that Blizzard controls. If your issue is the “This add-on has been blocked…” pop-ups, then the add-on author needs to change their add-on to not attempt to access protected code.
A lot of this stems from the UI improvements for this expansion, so add-on authors need to adapt to those changes.
It’s not a bug in the client, it’s something on your end. I have had zero issues with my addons, and I use a lot, over the last several patches, or even right now. I suggest going to the UI and Macro forum and posting the exact issue you are having, then possibly someone can help you.
Definitely going to need some more detail though. From the info you’ve provided, all I’ve got is “you aren’t doing something right, but I don’t have enough information to know what”.
Community speculation does not make someone “100% wrong”. That’s the entire point. The add-on community needs to figure it out, if they want their add-ons to function properly.
The “blocked” add-ons are happening because Blizzard changed many things about the UI in this expansion. Blizzard does not make changes to allow add-ons to work 100% of the time, with no input from the author. Blizzard makes changes, and the add-ons must be adapted.
I mean, the other option is to just take away the LUA sandbox and force everyone to use their stock UI.
I mean, no, that isn’t even what this topic is about. You also clearly didn’t read the quoted post when replying. There is a known defect that Blizzard introduced with their hotfixes to the LUA API when they made the change to “fix” the PvP-related macros which allowed so-called “smart” interrupt capability. See Fizzle’s link above.
Well theres a wealth of misinformation. Because the popups are saying that an action has been blocked by an addon, and it happens when near a mailbox, or in Valdrak only. I have had the popup trigger saying this action was blocked with these addons constantly, Button Forge,Hekili, Map Coords, Pawn, SexyMap, TomTom, and more, these popup separately after ignoring the first one. When i switch characters, the order of them changes.
the “addon blocked” error message is down to user code attempting to call a protected function (instant block), or changing a variable and tainting it so that when blizzards secure code tries to access that same variable it cant because you’ve tainted it.
now blizzard is entitled to protect anything they want and addon authors do have to work around that as you mentioned, but this isnt about something that has been newly protected, this are basic code constructs, like a for loop, that is triggering taint/blocks.
theres no way that blizzard meant to protect the for loop, or any of the other basic code bits that are triggering taint and blocks, so its a bug.
we cant work around it, and only blizzard can fix it. if you understood how blizzards code/execution protection, and taint, worked, you would understand why this is a bug.