Greetings. As the title describes, Baggins 5.4.8 does not display the "In Use" category for characters that utilize multiple gear sets in the Equipment Manager.

I've seen this on previous builds, and on those the issue was temporarily resolved by switching gear sets in the Equipment Manager. Version 5.4.8 does not begin to display "In Use" items even after switching gear sets and/or specifications.

@Elberet thoughts?

@StrykerJC , can you describe in detail what you expected and where? What is an "in use" item? Which version of WoW are you playing? Have you seen any LUA errors? Did you check BugSack for recent Baggins-related messages, if that addon is installed?

Just to preempt confusion:
Items that are worn or equipped should not appear in Baggins, since they're not in the character's bags; items that aren't being worn, but are being used in an equipment set, should be caught by the equipment set filter, but only if the correct equipment set is selected in the filter's configuration, or if the "Any" flag is enabled.

@Elberet Not sure about them but equipment sets was working in retail but after the patch it now is not. Not sure if its WoW or baggins, but since the prepatch they stoped showing up at all, it still lists all the sets in options though so not 100% broken. Before patch it worked though so something changed somewhere or api broke?

@Elberet oh and in cata classic it seems to still work for me. think this is a retail only issue.

@StrykerJC , thanks for the clarification, I've heavily customized my Baggins bags and categories, so I didn't immediately get what you meant with "In Use". As mentioned earlier, the equipment set filter is currently broken after the rewrite; I've already verified the problem on retail and identified the cause of the issue.

Once @doadin has merged the fix and published a new Baggins version, items used in equipment sets should appear in the "In Use" category again. 🙂

The PR mentioned above should fix this issue.

Blizzard apparently never removed void storage related APIs from retail, but then also didn't reimplement them in Cataclysm Classic, because they decided to skip over void storage entirely and go straight for the Collections feature.

@StrykerJC , can you describe in detail what you expected and where? What is an "in use" item? Which version of WoW are you playing? Have you seen any LUA errors? Did you check BugSack for recent Baggins-related messages, if that addon is installed?

Just to preempt confusion: Items that are worn or equipped should not appear in Baggins, since they're not in the character's bags; items that aren't being worn, but are being used in an equipment set, should be caught by the equipment set filter, but only if the correct equipment set is selected in the filter's configuration, or if the "Any" flag is enabled.

On older versions of Baggins (including versions released this month), any equipment that was in the bags but part of a set in Equipment Manager would appear as a separate category called, "In Use." It was a handy way to see which items were off limits for cleaning out some space in the bag or for highlighting which items one might want to upgrade with Crests.

I have not seen any LUA errors for Baggins, only a behavior that was present in the addon for a long time but is no longer working with this version.

I'm attaching a screen shot from 5.3.3, where this was working as expected.

@StrykerJC , thanks for the clarification, I've heavily customized my Baggins bags and categories, so I didn't immediately get what you meant with "In Use". As mentioned earlier, the equipment set filter is currently broken after the rewrite; I've already verified the problem on retail and identified the cause of the issue.

Once @doadin has merged the fix and published a new Baggins version, items used in equipment sets should appear in the "In Use" category again. 🙂

Thank you so much for the work that you and @doadin are putting into this addon. I truly appreciate it.

@StrykerJC @Elberet merged commit: 8b91a76 , included in v5.4.9 just released, as per usual may take a minute to get through to updaters.

@StrykerJC @Elberet merged commit: 8b91a76 , included in v5.4.9 just released, as per usual may take a minute to get through to updaters.

I got the update, and the issue does seem to be resolved. Again, thank you!