What's new
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

AutoEquip2 Hunter Issue

jolo309

New Member
Joined
Jun 5, 2011
Messages
48
Reaction score
0
Hello, everytime i start my bot it goes questing as i put it as but when it goes to rewards it don't pick bows or guns from rewards and it doesn't even equip it
 
Be sure you've set a weapon type and style in AE2 settings.
 
I put "ranged" as weapon style
And "bow" on weapon type i couldn't see any guns so
 
I have exactly the same problem. Same thing for Dungeons. It doesnt roll "Need" for bows / guns / crossbows. No matter what is configured.

I've tried:

Weapon Style: Ranged
Weapon Type: All

and

Weapon Style: Ranged
Weapon Type: Bow

It also doesn't always pickup a ranged weapon from quest rewards (Sometimes it does). However it does equip them if you have the ranged weapon in your bags.

EDIT: Another hunter related issue I forgot to mention. If you have an off-hand weapon in your bags that has agility stat on it then AutoEquip2 will try to equip it again and again. So I always have to destroy them because its so annoying when WoW tells me over and over again that I can't equip it..
 
Last edited:
Any chance this gets noticed by the developers?
If DungeonBuddy will work properly for MoP Dungeons it would be really nice if this works as intended.
 
i'm not sure if it's of any help. it's kind of late to re-post to this, but I was struggling with it also. I went into AE2 and just selected "ranged" and weapon type "none" and suddenly my character picked up a much much higher level (rare-blue)gun from a quest reward and equipped it. maybe a fluke. i'll re-post if it turns out to be one.
 
i'm not sure if it's of any help. it's kind of late to re-post to this, but I was struggling with it also. I went into AE2 and just selected "ranged" and weapon type "none" and suddenly my character picked up a much much higher level (rare-blue)gun from a quest reward and equipped it. maybe a fluke. i'll re-post if it turns out to be one.
chances are we resolved the issue in the latest version, so i doubt it was a fluke, and these guys if they still had the problem would of gotten it working as well.
 
chances are we resolved the issue in the latest version, so i doubt it was a fluke, and these guys if they still had the problem would of gotten it working as well.

Thanks G. I assumed as much, just wanted to follow up just in case. Good work.
 
Back
Top