Issue with Hunter attacking a.n.other target after end of main combat

[moog]

I've had this happen a few times with my mixed group (main PC is driving the tank, second PC is mage/priest/hunter/warlock, connected with KeyClone).

I will finish fighting one group and my hunter will then start shooting at another nearby group.

It has only happened a handful of times in the couple of months I've been playing the mixed team but it happened again yesterday, so thought I'd see if anyone had any ideas.

In this team, they all take their target explicitly from the tank (a "/target party1target" macro) and I am definitely not taking a new target with the tank!
I have the option ticked to "Stop Auto Attack" (when changing targets).

It only happens with the hunter not with the warlock+pet or with any other class in my various teams.

Any ideas why this is happening and how I can stop it?

[GizmoxLoW]

Ive had this happen a few times. if your main is a melee character and when your target dies and you press your attack button you automatically select the next target. if that target is across the room and in range your ranged will start attacking/shooting it.

all you can really do is watch your button spamming and make sure your "attack on assist" option is turned off on your clones or they will start shooting just by assisting you

[Frappuccino]

There's an option in combat options where you can turn off 'auto attack' or something. That will prevent your character from picking up new targets when spamming things like arcane shot and enabling auto attack. It will also turn off auto attack (autoshot) when switching targets so you don't shoot arrows at targets that are say, cc'd, when you target them for what ever reason.

At work now so I can't remember the exact name of that option, it's there though!

Multiboxing or not, hunters really shouldn't have this option on, unfortunately it's on by default though :p

[moosejaw]

What frap said about combat options. It really annoyed me that casting misdirect with a target up on the hunter would start auto attack. Yeah, I really want to waste my three damaging attacks with autoshot threat. How the hell did misdirect get classified as a start attack spell? Time for a suggestion forum post.

[Ualaa]

I get this occasionally, but I know the reason is because of the attack macro I use on my hunters.
I personally use the macro, based off of ElitistJerks.com

It is something like...
/assist [target=party1target]
/castsequence !AutoShot, Steady Shot
/cast Kill Command
/script HideUIErrors()

Not sure the exact format, but if you press (a working version of) this macro, minus the assist, with nothing targeted and there is something you can shoot within range, your hunter will shoot at it. So, if your party-leader has no target but your slave-hunter has a hostile in its field of view, it will attack that target because the macro is being spammed. The wow server queue's a few keystrokes it seems.

[Brandish]

Yeah, something changed in the game that makes it autotarget a 'next thing' when you fire off an ability without a target.... had an embarassing moment in a normal group where my hunter fired at a different group at the end of the fight... luckily the group was strong enough to deal with it.

[Kel]

Possibly Blizzard decided that hunter's didn't have enough of a bad rep in groups so thought they'd help things along a bit :)

I think if you turn off the option which causes the auto-target thing it leads to a dps drop (there is a reason but as hunter isn't my main I wasn't paying attention when I read that) which may explain why some hunters leave it on despite the add pulling potential. For 'solo' play though it's probably more of a gain to turn it off and know that you won't get any surprise mobs heading your way.

[moosejaw]

I figured out part of my problem. Pebkac. I reloaded vista and neglected to wipe clean the G15 default profiler keymaps. I use Innerspace to bind the G15 directly, so I had 2 different sources firing off keystrokes at the same time, hence my auto shot starting when It wasn't supposed to. /doh

[Zolo]

Using [harm] will prevent your char from auto selecting a new target. I use this on all of my slaves. e.g.

/cast [harm] Spell

Or using Ualaa's macro

/assist [target=party1target]
/castsequence [harm] !AutoShot, Steady Shot
/cast [harm] Kill Command
/script HideUIErrors()

This change will mean that if Party1 has a target the hunter will attack it. If it doesn't have a target then the hunter will do nothing. It will not grab a new target automatically.

[Vyndree]

All of my macros (hunter or not) are preceded with...

INSERT PREFERRED TARGETING MACRO HERE
/stopmacro [noharm][dead]
/cast INSERT SPELL OR ABILITY HERE


for example:
/assist Vyndree
/stopmacro [noharm][dead]
/cast !Attack