AdiBags

AdiBags

8M Downloads

[Bug]: Bank Bag Slot 1 not visible.

Nefram56 opened this issue ยท 5 comments

commented

Addon Version

v1.9.46zip

World of Warcraft Version

Retail

Describe the bug

When opening the bank, the first bag slot can't be equipped while the addon is enabled. The slot shows as blank and when you try to equip a bag in that slot you get an error saying, "this item cannot stack." When clicking on the v button on the bank frame it only shows bags 2-7 in the drop down menu after bank.
2022-10-29

Steps to reproduce

I don't know. I didn't notice this issue until after pre-patch dropped on OCT 25th. I've disabled the addon completely and the bag is still there. It's just not visible while the addon is enabled. I've checked on multiple characters and it's the same even with different bag types.

Verification

  • I have disabled all other addons and made sure this bug is triggered only with AdiBags enabled
commented

I've noticed this too, actually, and I'm pretty sure I know what the cause is. I'll try to get this fix in on the next release.

commented

Still an issue and it hides the contents of the bags. Was thinking I'd gone mad when I knew there was a load of Skystone in my bank as the proff window was showing them, but I could not find them. I tried with a new savedvariables to see if was a setting I'd changed somehow. But still the same.
Turning Adibags off then allowed me to see that bag and it's contents.

commented

I'm experiencing this too.

I had a completely empty bank with no bags installed. I tried to put a bag in the first slot, and it gave a "no equipment slot available for that item" error.

So, I tried deactivating Adibags, and tried it again in the vanilla UI, and it worked. Then, when I re-enabled Adibags, that bag I had put into the 1st slot visually was in the 2nd slot in Adibags.

commented

Hi.

We do know what the bug is -- there was an undocumented change in the Blizzard API that kept track of bank bag offsets. As mentioned above, this will be fixed in the next release (this week).

commented

This should be fixed. If not, please open a new issue.