search

AlexFolland / AutoGear

WoW convenience addon that automatically handles gear looting and equipping
https://curseforge.com/wow/addons/autogear
Other
8 stars 11 forks source link

Not registering equipment #23

Closed flutterJackdash closed 3 months ago

flutterJackdash commented 2 years ago

AutoGear doesn't seem to register that I'm holding a weapon (Kul Tiran Fury Spec Warrior) so every time I pick up a new weapon, however junk it may be, AutoGear determines that it is better than nothing, and swaps it out for the green gear I have in there, even if the item it determined to be better was grey. I either have to re-equip manually or run a manual scan on AutoGear, and this is happening constantly. It's the first I've ever run into this though, it has worked perfectly for all my toons.

AlexFolland commented 2 years ago

Fury has had its bugs over the years due to Titan's Grip. We've seen this particular issue in the past, but we thought we fixed it. Can you please link me to the wowhead pages for the weapons you want to wield, so someone can investigate?

For now, you can disable auto-equip with /ag equip and use the advice in the chat box to manually equip upgrades. I know this is annoying, but it's the only workaround we have right now. Thanks for reporting this.

flutterJackdash commented 2 years ago

Helm-Hewer Greataxe is the gear I'd been working with, but now I've got Bloodsoaked Skullforge Reaver x2 equipped and AutoGear is happier for it. Tried to have it duel wield to begin with, but AutoGear first determined that the Greataxe was the better choice and then it didn't seem to register anything was even equipped.

AlexFolland commented 2 years ago

Hmm, I wonder if the issue is just with axes. This is pretty hard to diagnose without playing the character myself. I haven't been playing WoW recently and just started a new job, so I feel a bit too busy to work on this right now. If you can find the issue in the code and/or submit a pull request with a fix, I would happily merge it.

AlexFolland commented 7 months ago

This might be fixed in the latest version which is not yet tagged for release. Would you mind trying with the latest git master?

AlexFolland commented 3 months ago

It's been a few months with no response and I expect that this issue is resolved, so I will close the ticket now. Please feel free to comment here again requesting to reopen this ticket or open a new ticket if you find any issue.