Locking in neck gems is not working for my paladin. I try to lock in culminating blasphemite and masterful emerald, but when sending to addon and also when clicking re optimize, the gems both revert back to deadly emerald. I am unable to send these gem preferences to the addon at all.
Nevermind, the problem was i hadn’t put the sockets on the necklace yet. The problem resolved itself when i put magnificent jeweler’s setting on the item. I’ll leave this up in case you think there is some way to prevent confusion like mine in the future.
In theory you should be able to lock in the extra gems without having already added the sockets, but maybe there is a case where it is discarding them if the underlying item doesn’t have the sockets yet, we’ll take a look.
There’s definitely an issue. I actually notice this every now and again. It was broken around two weeks ago, then it was fixed last week, and now this week it’s broken again.
I lock specific gems in, then the second I hit “re-optimize” it changes some slots to Versatile Ruby. It seems to mess up the slots that do not already have sockets. My gems are set to Auto in the settings.
If you could make a snapshot of this happening, I can use it to test. Press the “help” link next to the big “Best in Bags” section header, then copy the generated 32-digit snapshot ID into a post here.
I was able to reproduce this issue – as mentioned, it only happens if you lock a gem into a socket that the item does not already have in your inventory.
It is actually a bit difficult to make this case work smoothly in all scenarios… but we should be able to make the most common use cases behave as expected.