I have noticed a few issues such as the site recommending gear that is too high a level to equip (character lvl 72 told to use a sword that requires lvl 78 for instance) but if it is a known issue I do not want to waste your cycles having to read through a redundant post.
The addon also has issues with Equiping an Item that is either in my inventory and/or currently equiped(this is only a real issue because it does not geat added to the gear set properly and betterbags does not place it under healing set so I have to be very wary of what I disenchant)
Anyway thank you for all the work done and being done.
I think the required player level issue was reported by some other people – seems to happen mostly with warband-bound items. Blizzard is using some janky ways to determine the required player level for some reason – we have an update tonight that will hopefully fix most of those issues.
The other issue I believe is related to another bug we plan to fix later tonight where the optimizer solution would sometimes suggest swapping to a duplicate of the same item in your inventory.
It could also be related to an issue for which I don’t have an immediate fix: if the optimizer wants you to equip a warband-bound item, then you equip it… the addon will sometimes have trouble and think it is a different item because the act of equipping certain warband-bound items actually modifies the item, thus making it appear to be a different item to the addon. Doing an export/import to the AMR site after equipping your warband-bound items is a way to resolve that issue for now – we’ll give some thought to how to improve that in a future update.
I have not logged on to see if the new version, I am about to log on and try it out and Make a follow up post.
The Item level issue I had was with a plain BOE green in my warband bank,
I had tired the new export/import to no avail.
I have seen it go nuts and equip the same trinket(New Darkmoon), even when I mailed the duplicate trinket to another character and did I new export/import with my bank open.
I have noticed it getting confused with item when I swap specs also. I tend to do the export/ Import then swap to each spec after I transmog the gear for that spec.
If you get v145 of the in-game addon and re-export your items, it should resolve the required player level issue. If it still persists for some of your items, create a snapshot ID via the “help” link next to the big Best in Bags section header and post it here – Blizzard is being really inconsistent with how they specify required player level this xpac, but I should be able to figure it out from examples.
I can take another look at how the addon finds items and deals with duplicates – a couple years ago we started using the actual unique IDs that Blizzard assigns to each item, which should be pretty reliable… that said, I’m wondering if that unique ID is changing sometimes, for example if you transmog an item or equip a BoE item… that might change it’s ID – I would need to check.
I currently have v146 I guess the addon was updated after your post? I know things are wonky with items. Like I went to buy gear in the AH and selected useable only, looked at the required level before I bought it(it required lvl 70), did the buyout and when I got it in the mail it required lvl 80 to use.
Still had an issue with it repeatedly equipping the same item that was BOE when I did the Export/Import and it not showing as equipped in the AMR addon. After the item became soulbound I did another Export/Import and that seemed to have fixed the issue so the appears to be a workaround.
Yeah duplicate items I crafted in my bank are still giving my priest issues with AMR even though I have a pair soulbound and equipped even after re Exporting/Importing it seems to want me to equip the pair that are BOE.
Hope this info helps, let me know if I am wasting your cycles
Could you post a snapshot ID of your setup with the priest that is still having issues? You can create a snapshot ID via the “help” link next to the big Best in Bags section header – the following post also describes how to do it:
I no longer have this issue since I have replaced the offending piece with another upgrade. If I run across it happening again on any characters I will Send a snapshot ID