Baganator

Baganator

11M Downloads

Not Categorizing Equipment Sets separate from other equipment

pranavius opened this issue ยท 11 comments

commented

What version(s) of WoW are you using?

Retail

What version of Baganator?

668

What version of Syndicator?

185

What isn't working? What was supposed to happen?

Equipment that I have assigned to at least one equipment set is not categorized as such despite me increasing the priority of the Equipment Sets (Auto) category to "Highest"

Are you experiencing any lua errors

No response

Anything else?

No response

commented

Does this apply to all equipment in sets, or just one piece?

Please post a screenshot of one of equipment's tooltip, and an export of all your categories

commented

This applies to all equipment in sets.

Here's a screenshot of a tooltip showing which set an item belongs to, but this is not reflected in the bags. I deleted my Baganator saved variables just prior to taking this to see if I had changed any settings manually, but the same issue persists with default settings.

Image

Export of categories:

{"categories":[],"version":2,"sections":{"1":{"name":"EQUIPMENT"},"2":{"name":"CRAFTING"}},"order":["default_auto_recents","----","default_hearthstone","default_keystone","default_potion","default_food","default_consumable","default_questitem","_1","default_auto_equipment_sets","default_weapon","default_armor","__end","_2","default_reagent","default_tradegoods","default_profession","default_recipe","__end","default_gem","default_itemenhancement","default_container","default_key","default_miscellaneous","default_battlepet","default_toy","default_other","----","default_junk","default_special_empty"],"modifications":[{"showGroupPrefix":true,"source":"default_auto_equipment_sets","priority":3}],"hidden":[]}
commented

Are you on a Mac?

commented

Yes

commented

Try this build, should have the issue resolved:

Baganator-668-1-gc4db339.zip

commented

Thanks for the quick response. Do you know what about MacOS causes certain APIs to crash/misbehave?

commented

I don't, but this particular API is the only one I know of and its been broken since at least June 2024.

commented

Just reloaded after changing to the build you provided and caught this error:

Image
commented
commented

That looks good! Thanks again for the quick turnaround.

commented

Awesome ๐Ÿ‘