Bagnon

Bagnon

132M Downloads

Bags not visually updating

Closed this issue ยท 45 comments

commented

Is there an existing issue for this?

  • I have searched the existing open and closed issues.

Description

Getting these error as of the latest Bagnon update 11.1.17. Seems to make it so the bags don't visually update unless i use an item or reopen the bag window. Seems to happen when opening containers and creating gear from tokens.

6x ...eBlizzard_SharedXMLBase/CallbackRegistry.lua:80: CallbackRegistryMixin::RegisterCallback 'func' requires function type.
[C]: ?
[Blizzard_SharedXMLBase/CallbackRegistry.lua]:80: in function 'RegisterCallback'
[BagBrother/libs/WildAddon-1.1-6/WildAddon-1.1.lua]:101: in function 'RegisterSignal'
[BagBrother/core/features/itemTooltips.lua]:70: in function 'func'
[BagBrother/libs/WildAddon-1.1-6/WildAddon-1.1.lua]:31: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:28>
[BagBrother/libs/WildAddon-1.1-6/WildAddon-1.1.lua]:67: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:64>
[BagBrother/libs/WildAddon-1.1-6/WildAddon-1.1.lua]:76: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:74>
[Blizzard_SharedXML/EventUtil.lua]:93: in function <Blizzard_SharedXML/EventUtil.lua:85>
[C]: ?
[Blizzard_SharedXMLBase/CallbackRegistry.lua]:144: in function <...eBlizzard_SharedXMLBase/CallbackRegistry.lua:143>
[C]: ?
[Blizzard_SharedXMLBase/CallbackRegistry.lua]:147: in function 'TriggerEvent'
[Blizzard_SharedXMLBase/GlobalCallbackRegistry.lua]:9: in function <...ns/Blizzard_SharedXMLBase/GlobalCallbackRegistry.lua:8>

Locals:
(*temporary) = "CallbackRegistryMixin::RegisterCallback 'func' requires function type."


6x BagBrother/core/api/settings.lua:65: attempt to index local 'sets' (a string value)
[BagBrother/core/api/settings.lua]:65: in function 'upgradeProfile'
[BagBrother/core/api/settings.lua]:84: in function <BagBrother/core/api/settings.lua:61>
[C]: in function 'xpcall'
[BagBrother/core/api/settings.lua]:61: in function 'Upgrade'
[BagBrother/core/api/settings.lua]:57: in function 'func'
[BagBrother/libs/WildAddon-1.1-6/WildAddon-1.1.lua]:31: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:28>
[BagBrother/libs/WildAddon-1.1-6/WildAddon-1.1.lua]:67: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:64>
[BagBrother/libs/WildAddon-1.1-6/WildAddon-1.1.lua]:76: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:74>
[Blizzard_SharedXML/EventUtil.lua]:93: in function <Blizzard_SharedXML/EventUtil.lua:85>
[C]: ?
[Blizzard_SharedXMLBase/CallbackRegistry.lua]:144: in function <...eBlizzard_SharedXMLBase/CallbackRegistry.lua:143>
[C]: ?
[Blizzard_SharedXMLBase/CallbackRegistry.lua]:147: in function 'TriggerEvent'
[Blizzard_SharedXMLBase/GlobalCallbackRegistry.lua]:9: in function <...ns/Blizzard_SharedXMLBase/GlobalCallbackRegistry.lua:8>

Locals:
profile =

{
inventory =
{
}
rules =
{
}
point = "TOPLEFT"
hiddenBags =
{
}
color =
{
}
hiddenRules =
{
}
y = -350.222229
x = 474.999908
borderColor =
{
}
brokerObject = "BagnonLauncher"
vault =
{
}
guild =
{
}
bank =
{
}
}
(for state) =
{
inventory =
{
}
rules =
{
}
point = "TOPLEFT"
hiddenBags =
{
}
color =
{
}
hiddenRules =
{
}
y = -350.222229
x = 474.999908
borderColor =
{
}
brokerObject = "BagnonLauncher"
vault =
{
}
guild =
{
}
bank =
{
}
}
(for control) = "point"
id = "point"
sets = "TOPLEFT"
(*temporary) = "nil"
(*temporary) = nil
(*temporary) = "attempt to index local 'sets' (a string value)"

Bagnon Version

Bagnon 11.1.17

World of Warcraft Flavor

Retail

World of Warcraft Region

EU

Tested with only Bagnon

I got this issue with only Bagnon enabled

Lua Error


Reproduction Steps

Getting the errors on login.

Last Working Version

Bagnon 11.1.17

Screenshots

No response

commented

Which Bagnon version were you using before this one?
Your settings are either extremely old or got corrupted it seems, the error is on the settings upgrade, but the contents of it are extremely weird.

Resetting your settings should solve the issue "\run Bagnon_Sets = nil"

commented

Are you using any plugins for Bagnon? If so, could you try disabling them see if that solves the update issue?

commented

Which Bagnon version were you using before this one? Your settings are either extremely old or got corrupted it seems, the error is on the settings upgrade, but the contents of it are extremely weird.

Resetting your settings should solve the issue "\run Bagnon_Sets = nil"

Are you using any plugins for Bagnon? If so, could you try disabling them see if that solves the update issue?

Resetting my settings seems to have solved the issue. No longer getting the error on login. Will have to see if it pops up again.
Pretty sure i used the previous update.
And no, i'm not using any plugins,

commented

Have you been using Bagnon for a long time on that machine?

commented

In any case, will added a mechanism to the next version fix those weird settings that I can't understand how they came to be.

commented

Have you been using Bagnon for a long time on that machine?

Since probably like 2017 so i wouldnt be surprised if some old codes are causing it lol

commented

I'm not getting any error messages, but I too am having the "visual contents not updating" problem. E.g., smelting ore doesn't visually change the ore to bars dynamically. If I close/reopen the bags it shows correctly. I check for and install updates daily (Classic Anniversary).

When the servers come up from maintenance, I'll try the above fix.

**Edit: The fix appears to have worked for me. Not sure if or when the command will have to be repeated.

commented

I have tried resetting all settings, but the issue of backpack items not updating occasionally still occurs, which can be solved by reloading the UI.

commented

Hmm. After playing with it for awhile, the command doesn't seem to stick, if it works at all. Doesn't update when I try to move inventory around in the bag, but works correctly if vendor window is open.

commented

I am facing the same issue on WoW SoD, bags don't visually update when I move items to/from from/to bank and personal bags, and also bag sorting having issues, maybe linked to the first problem. I have to keep reloading UI to fix things.

Also opening items like Curios and other sacks containing items, they are also visually stuck in bag until a reload.

commented

Seems like resetting only applies to certain characters? My main doesn't have any problem anymore but on a DK alt, just moving items around doesn't visually update unless i reopen the bag. No errors either.

commented

getting the bags not visually updating as well with latest update. closing and opening the bags updates it.

commented

Similar problems here.
No backtrace initially, but subsequently on /reload, I see the following backtrace:

Time: Tue May 13 15:17:44 2025
Count: 1
Stack: ...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:39: Cannot find a library instance of "WildAddon-1.0".
[string "@Interface/AddOns/DataStore/Libs/LibStub/LibStub.lua"]:23: in function `LibStub'
[string "@Interface/AddOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua"]:39: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:35>
[string "@Interface/AddOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua"]:53: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:49>
[string "@Interface/AddOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua"]:83: in function `NewModule'
[string "@Interface/AddOns/Bagnon_ItemInfo/Main.lua"]:31: in main chunk

Locals: self = <table> {
 minors = <table> {
 }
 minor = 2
 libs = <table> {
 }
}
major = "WildAddon-1.0"
silent = nil

...

Update, the error from above seems to be caused by other incompatible modules. I had Bagnon_Itemlevel installed, and there was also a "Bagnon_ItemInfo" folder that wasn't tracked by Curseforge. Removing all Bagnon-related modules except for the official Bagnon module eliminates that error, but the issue with bags not updating still remains.

commented

Similar problems here. No backtrace initially, but subsequently on /reload, I see the following backtrace:

Time: Tue May 13 15:17:44 2025
Count: 1
Stack: ...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:39: Cannot find a library instance of "WildAddon-1.0".
[string "@Interface/AddOns/DataStore/Libs/LibStub/LibStub.lua"]:23: in function `LibStub'
[string "@Interface/AddOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua"]:39: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:35>
[string "@Interface/AddOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua"]:53: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:49>
[string "@Interface/AddOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua"]:83: in function `NewModule'
[string "@Interface/AddOns/Bagnon_ItemInfo/Main.lua"]:31: in main chunk

Locals: self = <table> {
 minors = <table> {
 }
 minor = 2
 libs = <table> {
 }
}
major = "WildAddon-1.0"
silent = nil

...

Update, the error from above seems to be caused by other incompatible modules. I had Bagnon_Itemlevel installed, and there was also a "Bagnon_ItemInfo" folder that wasn't tracked by Curseforge. Removing all Bagnon-related modules except for the official Bagnon module eliminates that error, but the issue with bags not updating still remains.

yes our particular issue is caused by either DataStore or Bagnon_ItemInfo, not Bagnon

commented

Could you guys kindly let me know if 11.1.18 (just submitted to curseforge) fixes your bag update issues?
Thanks

commented

Could you guys kindly let me know if 11.1.18 (just submitted to curseforge) fixes your bag update issues? Thanks

Updated Bagnon about twenty minutes ago after seeing this, did a /reload, and ran a Timewalking dungeon. Unfortunately still having the same issue.

commented

Could you guys kindly let me know if 11.1.18 (just submitted to curseforge) fixes your bag update issues? Thanks

Updated Bagnon about twenty minutes ago after seeing this, did a /reload, and ran a Timewalking dungeon. Unfortunately still having the same issue.

can confirm this

commented

`function Embeds:RegisterSignal(event, call, ...)

local f = self[call or event] or call
EventRegistry:RegisterCallback(self.Tag .. event, function(...) f(...) end, self, ...)

end`

this change on line 100 in WildAddon-1.1.lua seemed to fix the errors for me, but it was a different change then the day before, surprised everyone isn't getting these errors including the devs

SoD version of WoW

commented

`function Embeds:RegisterSignal(event, call, ...)

local f = self[call or event] or call
EventRegistry:RegisterCallback(self.Tag .. event, function(...) f(...) end, self, ...)

end`

this change on line 100 in WildAddon-1.1.lua seemed to fix the errors for me, but it was a different change then the day before, surprised everyone isn't getting these errors including the devs

SoD version of WoW

Unless I am missing something, that change changes nothing about the code.

commented

https://files.catbox.moe/2r8vvm.mkv

I really can't replicate this, everything updates normally on my end. SOD server.

commented

it fixes the LUA error, for some reason it seems some peoples LUA versions cant identify the type of the param passed into RegisterCallback (self[call or event] or call)

the fix I added doesn't change anything functionally, yes

all it does it tell the compiler that its a function parameter since for some reason the type is ambiguous (the original error)

"..eBlizzard_SharedXMLBase/CallbackRegistry.lua:80: CallbackRegistryMixin::RegisterCallback 'func' requires function type"

i am assuming since some people have the errors and others don't its a wow version/settings issue

also for me personally i get the error on loading in or /reload, don't even need to open the bags or do anything with them

commented

I see. That might be a clue to what is going on. Could you do me a favor please and try this on your machine, since I don't have the same error?

function Embeds:RegisterSignal(event, call, ...)
  if type(self[call or event] or call) ~= 'function' then
    print(event, call)
  end
  EventRegistry:RegisterCallback(self.Tag .. event, self[call or event] or call, self, ...)
end

It should print out some stuff in the chat. I'd like to know what.

commented

i will do you one better, ill try that and livestream it so we can do some pair programming

https://www.twitch.tv/aggybaby

commented

I'm in the twitch chat

commented

Ok, fixed that error message for the upcoming version. Have serious doubts however that it explains the lack of visual updates issue. They appear to be two unrelated problems. COULD be a cascade-effect thing, but we will see.

commented

i explained a bunch but apparently my stream is having issues

but that error i only get on load, and everything seems to work normally after, so i just needed to hide it basically, im not sure if others are having functionality issues

in my testing i tried just removing that entire function from WildAddon and then i wouldn't get updates in the bag frames anymore so it is needed/being used

commented

On Classic Season of Discovery: same issue. Sometimes it works, sometimes the visual update it not working. Closing and reopening the bag shows the change then (change: e.g. if you move an item from one bag slot to another).
I dont think this happend to version 11.1.15, probably 11.1.17 was the first version with this bug.

commented

Game Client:
Retail

Bagnon Version:
v11.1.17 & v11.1.18

Installed Plugins:
Bagnon ItemLevel Plus (CURRENTLY UNINSTALLED)
Plugin Version: v2.2.86-Release

Issue:
When using a stacked item (potion, food, pet levelling stone etc) the number of stacks would not change. Moving any item around the bag left the icon for it in the original bag slot, and an 'invisible' version in the new bag slot, which could then be moved to other bag slots but still remained invisible.

EDIT (NEWLY FOUND ISSUE): Discovered a new issue one the PTR (I hadnt uninstalled the addon there). I opened a renown chest and the items did not appear in my bag slots, they were invisible and only became visible once closing and opening the bag again.

Workaround: Reload UI / Close and Reopen bags

Troubleshooting Performed:

  1. While game was closed. Removed base addon (v11.1.17), installed plugin (v2.2.86-Release) and cleared the SavedVariables folder etc and rebuilt the folder structure fresh upon logging in

  2. The issue did not re-occur playing the game without th addon & plugin installed

  3. Reinstalled the base addon 'Bagnon' (v11.1.17) and launched game. Issue returned

  4. Performed full clean removal again, as per Step 1

  5. Installed updated version of the base addon 'Bagnon' (v11.1.18) and launched game. Issue returned

Current State:
I am currently leaving the addon uninstalled and will reinstall once the issue has been fixed. If you would like me to test fixes please let me know and i will happily do so. I am experienced with testing (its a part of my job as a Cyber Dev) so happy to run through things and update any code changes you want me to try etc

commented

P.S. Today issue started by grabbing items from the Mailbox. Before this action everything worked well. Not sure if this leads to the root cause or it is just "random"...

commented

SOD 11.1.18
Experiencing the same for about 2 days now.
Moving around items doesn't update until I close and reopen my bags.
Happens with the inventory, bank and mailbox.
Reloading seems to fix it for a short time but it eventually comes back.
No error message.

commented

Just released 11.1.19. It fixes the error message, unclear whether it fixes the update issue. Please let me know if it does.
Also, to everyone with the issue:

  • Do you have Bagnon plugins? If so, have you tried disabling them?
  • Do you have any unusual setting? For example, the error messages were only appearing to people with tooltip counts disabled. If you can't think of anything, try resetting your settings and see if the issue persists.
commented

Another test I thought of: after you start experiencing the issue, does the (bagnon) guild bank visually update normally? Is it just the inventory and bank frame that stop updating, or does the guild frame also stop? An answer to this would be quite informative.

commented

Game Client: Retail

Bagnon Version: v11.1.17 & v11.1.18

Installed Plugins: Bagnon ItemLevel Plus (CURRENTLY UNINSTALLED) Plugin Version: v2.2.86-Release

Issue: When using a stacked item (potion, food, pet levelling stone etc) the number of stacks would not change. Moving any item around the bag left the icon for it in the original bag slot, and an 'invisible' version in the new bag slot, which could then be moved to other bag slots but still remained invisible.

EDIT (NEWLY FOUND ISSUE): Discovered a new issue one the PTR (I hadnt uninstalled the addon there). I opened a renown chest and the items did not appear in my bag slots, they were invisible and only became visible once closing and opening the bag again.

Workaround: Reload UI / Close and Reopen bags

Troubleshooting Performed:

1. While game was closed. Removed base addon (**v11.1.17**), installed plugin (**v2.2.86-Release**) and cleared the SavedVariables folder etc and rebuilt the folder structure fresh upon logging in

2. The issue did not re-occur playing the game _without th addon & plugin installed_

3. Reinstalled the base addon 'Bagnon' (**v11.1.17**) and launched game.  **_Issue returned_**

4. Performed full clean removal again, as per Step 1

5. Installed updated version of the base addon 'Bagnon' (**v11.1.18**) and launched game.  **_Issue returned_**

Current State: I am currently leaving the addon uninstalled and will reinstall once the issue has been fixed. If you would like me to test fixes please let me know and i will happily do so. I am experienced with testing (its a part of my job as a Cyber Dev) so happy to run through things and update any code changes you want me to try etc

That would be really helpful. I haven't been able to replicate, so I do not know what is causing the issue. Could you please check the following:

  1. Does the issue also occur in the guild bank frame?
  2. While your inventory is open, what does /dump Bagnon.Frames:Get('inventory').ItemGroup:IsStatic() print out?
  3. Could you please replace BagBrother/core/api/events.lua and BagBrother/frames/inventory/itemGroup.lua with these files? (you'll have to rename them from .txt to .lua, github doesnt allow upload of .lua files). It will spam your chat with numbers whenever something in your bags changes, I am sorry for that, but what I want to know is if it STOPS spamming once the frame stops updating correctly. The spam is not visible to other players.

events.txt
itemGroup.txt

commented

I had the same issues with 11.1.17 reverted back to 11.1.14 which fixed the problem. Now after updating to 11.1.19 I used a pet cage and it would not be visually removed from my bag. After using your events.lua and itemGroup.lua the problem did not reappear.
2. returns true for me
3. It initally spammed but quickly stopped for me

Did you change anything in those 2 files or is it just the debugging outputs?
(Will try again with normal files and report back!)

To clarify: With 11.1.17 even moving items was not possible without reopening the bags everytime, this has since been fixed on my end with 11.1.19

Edit: With regular files it did not happen again, which is weird. I got the pet box from my mailbox and tried to use it and it was not removed. ๐Ÿคทโ€โ™€๏ธ

commented

WAS ABLE TO REPLICATE!

Super lucky, some asshole killed a stormwind vendor I was doing testing on while I was interacting with it, and that triggered the issue. It is a serious bug/flaw within Blizzard's EventRegistry. I've developed a workaround and will release a new build.

Please make sure to also update Scrap, PetTracker, any addon running WildAddon-1.1.

commented

I am testing, so far it looks good :-)

Only thing that is strange: I cannot see the numbers anymore. E.g. 4/30 items on bottom left in bag and bank. But hthis is of course another issue.

commented

Anyone else can confirm?

commented

Anyone else can confirm?

Everything looks ok so far.

commented

Anyone else can confirm?

11.1.20 seems to have fixed it for me. Still had the visual bug with 11.1.19

commented

4x BagBrother/core/api/owners.lua:54: bad argument #1 to 'pairs' (table expected, got number)
[C]: in function 'pairs'
[BagBrother/core/api/owners.lua]:54: in function <BagBrother/core/api/owners.lua:47>
[C]: ?
[BagBrother/libs/WildAddon-1.1-8/WildAddon-1.1.lua]:31: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:28>
[BagBrother/libs/WildAddon-1.1-8/WildAddon-1.1.lua]:66: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:64>
[BagBrother/libs/WildAddon-1.1-8/WildAddon-1.1.lua]:74: in function <...dOns/BagBrother/libs/WildAddon-1.1/WildAddon-1.1.lua:72>
[Blizzard_SharedXML/EventUtil.lua]:93: in function <Blizzard_SharedXML/EventUtil.lua:85>
[C]: ?
[Blizzard_SharedXMLBase/CallbackRegistry.lua]:144: in function <...eBlizzard_SharedXMLBase/CallbackRegistry.lua:143>
[C]: ?
[Blizzard_SharedXMLBase/CallbackRegistry.lua]:147: in function 'TriggerEvent'
[Blizzard_SharedXMLBase/GlobalCallbackRegistry.lua]:9: in function <...ns/Blizzard_SharedXMLBase/GlobalCallbackRegistry.lua:8>

Locals:
(*temporary) = 1
(*temporary) = "table expected, got number"

Still in 11.1.20, but 11,1,14 works with no problems for me.

commented

All Addons are up to date, dont know where the WildAddon1.1 stuff comes from.

commented

WAS ABLE TO REPLICATE!

Super lucky, some asshole killed a stormwind vendor I was doing testing on while I was interacting with it, and that triggered the issue. It is a serious bug/flaw within Blizzard's EventRegistry. I've developed a workaround and will release a new build.

Please make sure to also update Scrap, PetTracker, any addon running WildAddon-1.1.

RIGHT as I was about to start my testing on those 2 files hahaha

I have a character setup anyway ow on a random server with no addons ever enabled on them and a set of bags etc all ready to go if you need me to do anything else with them/test anything further.....glad you found it and nice pickup on the bug. Is it something that needs to go to Blizz to fix on their end?

commented

They really should fix it, but the workaround I made appears to be preventing it from occurring.

commented

Definitely fixed for me.

commented

They really should fix it, but the workaround I made appears to be preventing it from occurring.

I have done a few tests and don't see it happening....really great work mate, go and have a rest and feel good for catching the elusive bug/issue