SOOOO … If you’re using any regular inventory management addon (is there one that doesn’t have the problem?) attempting to buy a Warband bank tab causes a protected function error, forcing you to go through the rigmarole of turning off your usual bag management JUST to buy it.
Blizzard/Addon gurus: Is there a reason why addons are not allowed to buy warbank tabs and specifically warbank tabs? It’s an annoying bit of friction, seeing it was supposed to be one of the core features of this expansion.
Regular bank bag slot purchases via addon? That’s fine.
Gold can be moved into and out of the Warbank with addon active, too.
For some reason, they don’t want us buying specifically a warbank tab unless it’s through the plain jane UI, which is completely perplexing (I’m not sure if guild bank tabs are similarly affected) …
There’s no conspiracy theory. Why do you think this applies to every player and every addon? I’ve never had a problem accessing/purchasing warband tabs with an inventory management addon.
It’s definitely something Blizzard specifically intended.
It’s clearly confirmed behavior (there was even apparently one several months old on this same forum, although I did not want to necro), including bug reports people have made to a number of inventory addons at Github.
For some reason, “PurchaseBankTab()” is protected. Okay, perhaps the practical solution is obvious, if annoying, more of a question is why this needs to be a problem in the first place (since other purchasable bank expansions, with the possible exception of gbank that I do not have an opportunity to attempt right now, do not run into problems; certainly, regular bank bagslots are trouble-free as always, as is getting the reagent tab; neither does “interacting with the warbank” seem of itself considered problematic, since I was able to shift gold to my new DK on Tichondrius - I very much love the ability to easily move gold to an alt on a new realm - with zero friction).
Usually when a function is protected, it’s pretty clear why you are not being allowed to do xyz via addon (usually when it is not clear, it is because skill issue i.e. the thing that Blizzard is aiming to stop is above your play level e.g. when 4.0 gave fits to addons like Elkano buff bars because they made clicking off a buff Protected due to folks automating it with Shadowmourne - apparently you could get some kind of performance edge by canceling the buff sometimes - or it’s a taint issue where the actually-responsible addon is not the one ultimately failing).
In this case, there appears to actually be no reason at all for it, though.
Unless perhaps it’s a leftover from when the warbank was bugged out to Silithus and back (and apparently disabled altogether for a time? I only just recently got into TWW, which I’m already getting the “I should have chosen this instead of Dawntrail, now I’m behind for no good reason” cozy satisfied vibe about overall btw) …