#showtooltip
/cast Aimed Shot
It casts autoshot instead, and throws some error like "you can not do that now" or etc... also, the icon for the macro shows as gray, as if you didn't have a ranged weapon equipped or something.
Ugh.

Code: Select all
/cast Trap Launcher
/cast Ice Trap
Much gratitude to Spiritbinder for the signature and Vephriel for the avatar! <3
Much gratitude to Spiritbinder for the signature and Vephriel for the avatar! <3
WHU has reported much different. They said those who did use macros, even in TBC, did far less dps than those who manually did it during procs and such as needed. I trust their word and my own results too.Sarayana wrote:That's not always the case Taluwen. It's somewhat been true for Wrath, but back in TBC the macro was the way to go for BM hunters. Even at that, most raiding MM hunters in Wrath macro silencing shot to their other shots, and many of us use macros to fire off our long cooldowns at once. Macros are far from useless.
That's a different kind of macro. Macroing in Silencing gives you an additional shot, and macroing all your burst CDs to one button can help you get a bigger initial burst. Then you need to time them without macroes. The kind of macro that lowers DPS is the stupid "Push this button and you use all your shots *Flail*!" kind.Taluwen wrote:WHU has reported much different. They said those who did use macros, even in TBC, did far less dps than those who manually did it during procs and such as needed. I trust their word and my own results too.Sarayana wrote:That's not always the case Taluwen. It's somewhat been true for Wrath, but back in TBC the macro was the way to go for BM hunters. Even at that, most raiding MM hunters in Wrath macro silencing shot to their other shots, and many of us use macros to fire off our long cooldowns at once. Macros are far from useless.
I also exist on DeviantArt.
"I'll probably be some kind of scientist, building inventions in my space lab in space!"
Moderation note: Saturo is banned from all forums except the RP forum, and only allowed there until the current RP thread ends.
Ooh. Sadly, I see a lot of hunters doing this or wanting to do this now. ><; Not here, I mean ingame though.Saturo wrote:That's a different kind of macro. Macroing in Silencing gives you an additional shot, and macroing all your burst CDs to one button can help you get a bigger initial burst. Then you need to time them without macroes. The kind of macro that lowers DPS is the stupid "Push this button and you use all your shots *Flail*!" kind.Taluwen wrote:WHU has reported much different. They said those who did use macros, even in TBC, did far less dps than those who manually did it during procs and such as needed. I trust their word and my own results too.Sarayana wrote:That's not always the case Taluwen. It's somewhat been true for Wrath, but back in TBC the macro was the way to go for BM hunters. Even at that, most raiding MM hunters in Wrath macro silencing shot to their other shots, and many of us use macros to fire off our long cooldowns at once. Macros are far from useless.
Much gratitude to Spiritbinder for the signature and Vephriel for the avatar! <3
Ooh, if that works I might use that! I want to save bar space, but it's annoying to have to click-click-target-click to drop a trap at your feet... I'm just not as good at macros as you guysMockingbird wrote:I'm going to try using
/cast [button:1] Whatever Trap
/cast [button:2] Trap Launcher
Since I rarely PvP, I tend to have my traps on their own part of bar that I click - I'm quick and accurate enough that it doesn't cause trouble in PvE, where the reaction times are naturally more lenient.
therefore for regular trap, left click. For launch, right click/left click/target click.
Much gratitude to Spiritbinder for the signature and Vephriel for the avatar! <3
Hmm. I like how your macro lets you see the trap you will be casting, however it doesn't let you unload 2-3 at a time.Mockingbird wrote:I'm going to try using
/cast [button:1] Whatever Trap
/cast [button:2] Trap Launcher
Since I rarely PvP, I tend to have my traps on their own part of bar that I click - I'm quick and accurate enough that it doesn't cause trouble in PvE, where the reaction times are naturally more lenient.
therefore for regular trap, left click. For launch, right click/left click/target click.
Ehh... yes and no. Here is how it currently stands with casting these from macros:Nimizar wrote:My guess is that this is a similar situation to the one affecting druids in Tree of Life form (all macros for their heals that are affected by ToL break).
When we hit Trap Launcher, our traps actually switch to be different spells. This confuses the macro engine, since it tries to use the "normal" trap spell, which isn't actually available until the TL effect is used. With Snake Trap working in this context, I would be curious if it works *without* Trap Launcher already being active (I also note that ST is the only new trap we learn after learning Trap Launcher, so that could explain any differences in the order the abilities are tried by the macro engine).
This is the post GC made in response to the druid ToL macro issues.
No clue on why Aimed would be stuffing up though, unless it has something to do with it now being a spec ability. Do Intimidate and Explosive work in macros at the moment?
It's almost certain that it is the same problem then. Whether it is the normal or the modified form that works in macros is just a question of which of the two spells appears first in the internal list consulted by the macro engine.Worba wrote:Ehh... yes and no. Here is how it currently stands with casting these from macros:
Aimed Shot: works only if master marksman is ON
Snake Trap: works only if trap launcher is OFF
Others (explosive, immo etc): works only if trap launcher is ON
Hopefully Blizzard will wake up and fix this next tuesday.
If so, why were mount macro commands fixed the morning after 4.0 came out?Nimizar wrote:It's almost certain that it is the same problem then. Whether it is the normal or the modified form that works in macros is just a question of which of the two spells appears first in the internal list consulted by the macro engine.
I wouldn't put money on it being fixed before 4.0.3 though (since macro engine changes generally require a client side patch).