Been seeing this from the start I start botting my alt druid. For some reason it keeps equiping agility gear on my moonkin druid, also it's picking quit rewards with agility, a trinket for example. I don't have logs as I'm not seeing it happen.. i notice it when I check my chars gear once in a while. Any solution?
Sounds like a problem with your weight sets. Try replacing them with the set available on my AutoEquip mod thread here.
not really sure if its even AutoEquip doing it or something else.. what plugin buys the wrong item? AutoEquip only equips them right? Which plugin should I check that buys them incorrectly?
Downloaded and added the weight, thanks alot for the pointer, not sure if it helps since this doesn't prevent my bot from choosing the wrong quest reward, or does it?
Hey again, hope i dont bother u to much. Anyways.. I tested it with the new weights that u linked but it still buys and equips the items with agility instead of intellect. Any clue?
Quest rewards are chosen based on the same weight sets. Which specific items are the problem? A log would be appreciated.
See attachement, look in this for for "Mar'at Belt", this is an agility belt and im a druid in boomkin spec, also specified with talented. View attachment 1036 2013-11-20 14.14.txt
This. Big time this. ^^ I'm using ShortRound's weights over my own, even though I need to update my signature, lol. Edit: Sorry, read further down after making this post. I just checked your log for what you suggested. This is based solely on my own opinion and understanding, but someone else may be able to provide another viewpoint. [15:02:55.332 D] Quest Reward: "Mar'at Belt" scored 1274.9 - Has the highest value of the rewards. [15:02:55.332 D] Quest Reward: "Bracers of the Dark Pyramid" passed since we can't equip it. - You're unable to use this, so it's discounted as useable. [15:02:55.334 D] Quest Reward: "Shining Scorpid Eye" scored 529.3666 - Has the lowest score for the rewards, so it's also discounted. [15:02:55.334 N] Choosing Mar'at Belt. - Chosen because of the score based on the weight sets. [15:02:55.334 D] Selecting "Mar'at Belt" as quest reward. It scored 1274.9. - Showing why it was chosen, which is because it had the highest score. [15:02:56.167 N] [AutoEquip]: Equipping Waist "Mar'at Belt" instead of "Girdle of the Rescuer" - it scored 1274.9 while the old scored 1053.4 - Used the higher scored item, because that's what AE2 does. It changes out your gear for the higher scored item. The last line does bother me though, along with the first line. If you're using the replacement weights, and not the ones that come with HB, then it should have (more than likely) kept the current Boomkin-compatible belt you were wearing. It may have also chosen the Shining Scorpid Eye (if it was an intellect item) also. I'm wondering if when you downloaded the weight sets from ShortRound's thread, did you delete the default weight sets? Or, did you possibly just overwrite them with the new ones? You have to delete the default weights to completely get rid of them, then put the new weights in. If you overwrite them then they go wonky and stop working properly. Try deleting ALL the weights, start with a fresh set of weights (use the ones from ShortRound's thread that he linked, they work wonderfully and are well designed), and see how that works out.
Thanks for you reply and insight. The thing is, I did what u said, deleted the old weight sets and replaced them with the one from shortround's thread. Still buys and equips the wrong items.
Hrm. I'm not as "bot smart" as some of the more experienced users are, so I'm personally running out of things to suggest. It could be a code related issue, it could be something wrong with the AutoEquip 2 plugin, it could even be Honorbuddy messing up when choosing rewards. It's been working rather well with my mage, but I'm only level 42. I do know that it's been having issues with selecting quest rewards once you get into the MoP quest areas, but that was a while back. Since I don't have a character to take through the MoP zones to quest anymore, I can't really say if it's been fixed or not. Maybe Tony, or some of the other more experienced users, can help you out further. I apologize for my lack of knowledge and ability to assist you. Hopefully you can find a resolution soon.
