/startattack killed me vs prot pally

[Gruntworks]

LoL so title says it all, huge face-palm moment. We had the match in the bag until I reset avenger's shield by hitting him with my staff, which he was more than happy to parry me and throw a second avenger's shield at my healer stopping an incoming heal. I saw it happening in slow motion but couldn't do anything about it.
I have always used /startattack in my macros, example:
/startattack
/cast [@mouseover, exists] shadow wordain
/cast [mod:shift, @focus] shadow wordain
/cast shadow wordain

The benefit of /start attack is obvious, you just push the button and automatically target the nearest enemy and dot them unfortunately for casters this will also turn on your melee swing. This doesn't preset any problem what so ever at max level but at lvl 70 vs a prot pally it can kill you quick.

So in closing if you are used to using /startattack in your macros, I highly advise you delete the command and use tab/ left click/ or /target arena 1,2,3 macros.

Don't be a victim of this completely avoidable mistake. Don't reset avengers shield as a caster.

 

[Dreams]

/target arena 1,2,3 macros.

Problem solved

 

[Gruntworks]

Yeah just trying to give fellow non fotm players a warning, casters have it hard enough in this bracket vs rogues and prot pally. Don't need to give prot anymore advantages.

 

[Aerandielle]

/targetenemy

Will automatically target nearest enemy, but won't make you autoattack.

If its about always targeting the nearest enemy, you can use something like:

/console targetNearestDistance 5.000000
/targetenemy
/cast <insert spell here>

If you want to switch to nearest enemy and switch back to your previous target afterwards, just add /targetlasttarget

Last time i used these commands hunters still had wingclip and mongoose bite lol