Issues with buy items (random stat allocation / naming)

[dooffie66]

Hello,

I tried to look through to see if I could find one with a similar issue.

I think the issue can best be described with a scenario.

I scan the auction house to get the latest info, and to see if I can snipe any good AH deals. > I open the gold guide AH window that shows deals worth buying. ( I have it set to expert to get those risky but profitable tmog deals ) > I find a good green item and I can see that it is one of those "leather chest of the owl" you know with randomly allocated stats. I add it to the buy list.

Here is the issue then. When I click on the item in the buy list, for it to find it so I can press buy. It doesn't find it. If I manually go into the Blizzard buy window I can see it in there.

So far I have only encountered this issue with items that have etc "Of the owl" "of the bear" and so on.

This issue was also present in the gold guide 1.0


Troubleshooting steps I have tried so far are:
-scan & repair
-clean install of the addon
-deleting interface & WTF folders
-deleting the addon, laucher & all data store in %appdata%
-clean install of wow
-on different ip ( through vpn )

I hope that this is helpful helping resolve the issue, or figuring out whether it is on my end or not.

Kind regards
-Glen

[ZG Support 1]

The team have been able to reproduce this and are working on a fix right now.

[dooffie66]

Splendid. I asume this requires a update to a addon it self. Is there an ETA on when a solution can be expected?

[ZG Support 1]

I'm sorry, I do not have an ETA. I only know that they are working on this bug. And yes, this is in the addon code so it needs the addon to get updated.

[dooffie66]

I'm sorry, I do not have an ETA. I only know that they are working on this bug. And yes, this is in the addon code so it needs the addon to get updated.

Okay

I'll just be patient and wait some time. Otherwise the new 2.0 is pretty good. I'm happy to see that some of the features that TSM had has been implemented.

Kind regards
-Glen

[ZG Support 1]

I was just informed this should be fixed with the next guide update that goes out. Version 13311 or higher should have the fix in it.

[dooffie66]

I was just informed this should be fixed with the next guide update that goes out. Version 13311 or higher should have the fix in it.

Fantastic!

Even though it is a paid addon, I feel that the contact to support and the quick responses alone makes up for it

Kind regards
-Glen