I'm afraid that the most elegant solution to this is not very elegant at all. Basically, you have to create a macro that will /target your viper target, fire viper sting, and then /targetlasttarget. You could put that all under conditionals so holding shift or something would just fire it at your current target.

I believe you're only option is to use [target=mouseover] in your macro. Explicit targeting - [target=name] - only work with players.

A tip for MM hunters. Make a macro for each of your shots, make sure it includes silencing, because if you only include it on one, you'll lose 1-3 seconds of damage which is around 1 global cooldown which you could've used for a higher DPS Shot

I have a couple of questions regarding some of the macros listed here :

- With "aura" type skills (that can be canceled with /cancelaura), is it possible to make a toggling macro? I don't think strings like :
/cast Aspect of the Pack
/cancelaura Aspect of the Pack
will work, won't it? Also, I'll be using this toggling macro for Deterrence.

- With the Misdirection macro mentioned on the first page of the thread :
#showtooltip
/cast [target=focus, help] Misdirection
/cast [target=focustarget, help] Misdirection
/cast [target=target, help] Misdirection
/cast [target=targettarget, help] Misdirection
/cast [target=pet, nodead, exists] Misdirection

What should happen under the scenario that another hunter already MD'd to the MT? Normally (without macro) the MD will fail, showing an error message. In case with the macro, will it fail to execute (and there fore nothing will happen), or it will run through all the conditions and finally misdirected to the next "true" argument (line 4->hostile's target, for example)?

- With the melee macro also posted over there, I noticed that sometimes, when the Raptor Strike is still being queued to be executed due to swing timer of my melee weapon, the macro will cast Disengage immediately. Is it possible to make a macro that will delay Disengage until Raptor Strike is properly executed beforehand?

- I'm aware that in a macro, there can be any number of non-GCD triggering skills and "next strike" skills, but only one GCD-inducing skill. Is there any certain sequence that has to be followed for those skills for the macro to work? What I'm wondering is whether it is possible to make a macro such as :
#showtooltip
{/cast whatever Cooldowns you want}
/cast Chimera Shot
/cast Readiness

My intention is to fit one high-damage shot before refreshing the Readiness, while ensuring that Readiness is refreshed as fast as possible.

Answering your first question: The targeting logic is resolved ahead of the actual cast so you will attempt to cast it on the tank & have it fail.

For your second question, the GCD requiring spell has to be last, so no, you can't put Readiness after CS in a macro.

MizarAlcor:
With aspects, "/cast aspect /cancelaura aspect" -macros do work, however I do not see those being overly useful. You never want to be without an aspect, so I would think it better to use a castsequence for switching between the aspects.

Iru already answered two of the others, though I would like to add a bit to his answer: even if an ability does not trigger a GCD, it cannot be cast while a GCD is not finished. This is why the ability with GCD has to be the last. Exceptions to this are pet abilities such as Kill Command and Call of the Wild.

Misdirect
This should MD to your focus, your focus's target if it's hostile, your target if you don't have a focus, your target's target if you have a hostile targeted, or your pet if you don't have a target.


My question is when I use this it said it as a raid warning, party and something else but can't remember. How do I stop it from doing that or am I doing something wrong.

The macro itself won't announce anything anywhere. You must have an addon doing that.

Do you know which one it would be the only one I can think of would be DBM. If so do you know of a way to turn that part off.

Perhaps a list of the addons you're using will help us.

DBM won't announce misdirect, I have an add on called misdirection announce, but there are many, so as Arlen said, a list of adds would be useful.

Here is the list of my add ons

Thank you everyone I found which one it was it was Zhunter I turned that part off and now it works fine

I often try to put multiple shots into one macro based on priority to minimize the buttons I have to press. However, is there a way to put a condition infront of the aimed shot, so if I shoot a Multi-shot, it will skip onto a steady shot?

Worst case I could probably just put another modifier like CTRL that will just shoot steady shot for those instances when I do use multi-shot instead of aimed. As long as I'm asking, can you use a modifier for castsequences? I'll be testing shortly either way.

Thanks in advance for any insight or if there is a better way to go about this.

Nope.

Has anyone else been having trouble with standard chimera etc. macros that include
Silencing Shot and/or Kill Command?
After the patch it seems like all my shots that have Silencing Shot / Kill Command macroed in them
have this little "lag" and give me "spell is not ready yet" alerts..

I have them like this:

#showtooltip chimera shot
#show chimera shot
/cast [target=pettarget,exists] kill command
/cast chimera shot
/cast silencing shot

#showtooltip aimed shot
#show aimed shot
/cast [target=pettarget,exists] kill command
/cast aimed shot
/cast silencing shot

#showtooltip Serpent Sting
/cast Serpent Sting
/cast silencing shot

#showtooltip Steady Shot
/script UIErrorsFrame:UnregisterEvent("UI_ERROR_MESSAGE");
/cast Kill Command
/cast Steady Shot


my latency is about 180mms so that shouldn't be the problem.

Edit: adjusting my macros as suggested 2 threads below didn't help. I suppose it's addon issue then.
Edit2: not addon issue either

Just confirming that Silencing will indeed require to list cast before any other GCD consuming ability.

It seems with 3.2 Blizzard made a fairly large change in how /castrandom works. It's been changed to be "sticky" so that once invoked it will randomly pick a spell to cast. That's as you would expect. The newly added behavior is that any subsequent call will yield the same result until the previously selected spell is successfully called and completed.

There was a fair amount of code added to the client on this, so it is clearly intended. This change still allows you to, say, invoke a random mount. Each time you invoke the mount the spell has succeeded, and on the next cast the random clause is hit again - to get a potentially different result. If, however you see on your cast bar that an undesired mount is being invoked and jump out of that cast, the next call to your random mount macro will yield the very same result.

So, we know that none of you are using /castrandom to consolidate multiple hunter shots into a single button, that you map to something like, say, the scroll wheel that you then spam thousands of times to activate shots as they become available. But if you were doing this then I suspect you are starting to notice that it might not be working so well these days.

Here's an example, that a non-elitist jerk might have used to apply kill shot without mapping it to a key, by loading it onto an already heavily used button.

/castrandom Steady Shot, Kill Shot

Old behavior:
first call - selects (randomly) steady shot, which is (work with me here) on a supposed CD that it doesn't acutally have, so nothing happens
second call - selects (randomly) steady shot, fresh off the exemplar CD, and fires Steady
third call - selects (randomly) kill shot, but the target is at 87% so nothing happens
fourth call - selects (randomly) steady shot, which is back on CD, nothing happens
etc.etc. - more or less effectively applying the two shots, depending on how fast that mouse wheel is spinnning

New behavior:
first call - selects (randomly) steady shot, which is on that silly CD, so nothing happens
second call - selects (not at all randomly) steady, because it never finished. It's off CD and fires
third call - selects (randomly again, because the last spell finished) Kill shot, but the boss is at 87% so it doesn't fire
forth call - selects kill shot again, because it never fired, boss is at 86%
fifth call - selects kill shot again, ....
etc. etc. - the macro is "broken" in that it will get stuck on either Kill shot or Steady shot, and not ever select the other until the first actually fires and is complete.

Good. No macro can (or should be able to) play a hunter for anyone.

This is not possible and I would not recommend the macro you are trying to use. Hunter dps is complex and reactive enough that a castsequence macro isn't going to yield anything more than frustration and lower dps.

@Difool - Steady Shot has no cooldown (unless you are considering the GCD from another ability, in which case your condition applies perfectly) but the information you have shared seems good otherwise and I am glad to hear that hunter dps can't be reduced to a macro spam fest.

Hello i know there have been several posts on quick change of aspects in the pasts posts however i am unable to find one that does what I would like to do... Basically

-on 1st press-
1. Switch to Aspect of the Dragonhawk
2. Notifiy via MikSBT.DisplayMessage("Aspect of the Dragonhawk")

-on 2nd press -

3. Switch to Aspect of the Viper
4. Notifiy via MikSBT.DisplayMessage("Aspect of the Viper")

then rinse repeat..

currently i use

#Showtooltip
/cast Aspect of the Dragonhawk
/cast Aspect of the Viper
/run MikSBT.DisplayMessage("Aspect Changed")

However, this can get confusing... always wondering which aspect is up

Im thinking something like

/script if Aspect of the Viper is active then MikSBT.DisplayMessage("Aspect of the Viper") elseif Aspect of the Dragonhawk is active then MikSBT.DisplayMessage("Aspect of the Dragonhawk")

Im not to worried about the MikSBT.DisplayMessage thing i know how that works, however is someone could help me with the if statment that would be great

Doesn't MSBT allow you to pipe certain buff gains/losses to a designated location? Just set up the gaining Aspects buffs to display in your notification window. Then you can just use the macro to change aspects and not worry about notifying MSBT.