Selecting first reward as the QuestCache seems messed up and contains no questreward

Hello,

I have been getting this error "Selecting first reward as the QuestCache seems messed up and contains no questreward choices but we have questrewards to choose from." for every quest that contains any number of rewards. It seems to only be affecting me in Pandaria zones. I have done everything ever suggested. Cleared all four caches, reinstalled a clean HB, deleted meshes, etc. It will ONLY choose the first reward, it doesn't matter what the item is. It is not because the stats on the first item outweigh the rest, it just doesn't recognize any of the choices apparently from what the error says.

Thank you, hopefully we can get this fixed.

View attachment 3936 2013-03-27 07.49.txt

 

As I stated in my original post, I have cleared all four caches. Can anyone help me?

 

Just curious if this is being looked at legitimately, or if it's thought we all are still jacking up our cache deletion? There are several of us having it, and we've all produced logs, with all of our cache's cleared. All the issues i've seen have been MOP related, and personally (when i've noticed it) it seems to be when the questreward is specific to the class you are playing (giving a choice for the possible specs you can have, druids get an int and an agi option, dks a tank/dps option etc). Should we just post this in Kick's profile page?

 

Absolutely not! Profiles have absolutely nothing to do with quest reward selection. More info here:

HelpDesk: Toon is picking the wrong quest rewards​

cheers,
chinajade

 

I do agree with him, a lot of people including myself are getting this issue in MoP zones only. So according to the help desk you linked us, the weight sets determines what the bot chooses as a quest reward? If so, would it help if I replace the weight sets with these weight sets updated for 5.2?

 

the problem isnt the weight sets, the issue is that to get the data for the quest reward items we need to read the data from the wow's data cache without the data we wouldn't be able to tell a what rewards are being offered up. the issue is in some cases wow's cache format is different or being corrupted preventing honorbuddy from reading the data it needs to be able to select a quest reward properly.

make sense?

the devs are looking into it, but it takes time as not everyone has the issue and they are the ones that need to replicate an issue that no one knows how to cause.

 

having the same issue here, cleared caches, doesnt help. cheers.

 

Closing thread. CodenameG has done well answering the issue.

cheers,
chinajade