/cancelaura Netherwalk doesn't work

[Syncness]

#showtooltip
/stopcasting
/stopcasting
/cancelaura Netherwalk
/use Netherwalk

Doesn't work. The same macro works for Aspect of the Turtle however.

Anyone else?

I've already submitted a bug, recommend others do so as well.

[Juvencus]

#showtooltip
/stopcasting
/stopcasting
/cancelaura Netherwalk
/use Netherwalk

Doesn't work. The same macro works for Aspect of the Turtle however.

Anyone else?

I've already submitted a bug, recommend others do so as well.

Works fine for me. Tried both with the /stopcasting lines and without.
Check for spelling in the game macro.

[Deleted]

just flip it.
#showtooltip
/stopcasting
/stopcasting
/use Netherwalk
/cancelaura Netherwalk
Work perfectly

[BrioWoW]

Works fine for me. Use it all the time.

[Teevo]

just flip it.
#showtooltip
/stopcasting
/stopcasting
/use Netherwalk
/cancelaura Netherwalk
Work perfectly

This is bad. It'll use it and immediately cancel it. That's why you put the /cancelaura first.

#showtooltip Netherwalk
/cancelaura Netherwalk
/cast Netherwalk

That's all I use and it works great.

[Kobor]

For me this is working just fine, copied from Paladin Divine Shield macro.

#showtooltip
/say Solo Soaking! <-----Optional row
/cancelaura Netherwalk
/cast Netherwalk
/stopmacro

[Deleted]

/use Netherwalk
/cancelaura Netherwalk
Work perfectly

For a certain interpretation of "works", sure.

[Saverem]

This is bad. It'll use it and immediately cancel it. That's why you put the /cancelaura first.

#showtooltip Netherwalk
/cancelaura Netherwalk
/cast Netherwalk

That's all I use and it works great.

Same. Is there a point to /stopcasting as a DH? Most of your abilities are instant cast, and the ones that aren't (Eyebeam) can't be used while Netherwalking anyway...

[Teevo]

Same. Is there a point to /stopcasting as a DH? Most of your abilities are instant cast, and the ones that aren't (Eyebeam) can't be used while Netherwalking anyway...

None whatsoever. The only time you'd want /stopcasting is in an eye beam macro if you're using blind fury and have to move out of something.

[Lostprophet]

None whatsoever. The only time you'd want /stopcasting is in an eye beam macro if you're using blind fury and have to move out of something.

even then it is not needed since using netherwalk or any ability will cancel the channel anyway

[Teevo]

even then it is not needed since using netherwalk or any ability will cancel the channel anyway

Well true, but I was referring to cases where you need to move and won't use netherwalk to do so (saving it to soak something later)

[Yxiomel]

This is bad. It'll use it and immediately cancel it. That's why you put the /cancelaura first.

#showtooltip Netherwalk
/cancelaura Netherwalk
/cast Netherwalk

That's all I use and it works great.

No it wont; macros execute in a single frame, therefore he wont have Netherwalk yet regardless of the command order.

[Zyrosis]

No it wont; macros execute in a single frame, therefore he wont have Netherwalk yet regardless of the command order.

Not true at all. If you put the /cancelaura before the cast it will leave you with the buff active, and you just use the macro again to remove the buff. However, putting the /cancelaura after will use Netherwalk and immediately remove it. If you don't believe me, try it yourself in-game. Been using that method on my paladin for years.

Edit: You know what, just tested it and I either read your statement wrong, or you wrote it wrong, but no matter the order you'd still have to hit the macro twice to remove Netherwalk. First to cast it, second to remove it, no matter the order.

[Lostprophet]

Well true, but I was referring to cases where you need to move and won't use netherwalk to do so (saving it to soak something later)

Ah I should read =P In such cases I use either Chaos strike ( if enough fury) or fel rush.

[Kobor]

Edit: You know what, just tested it and I either read your statement wrong, or you wrote it wrong, but no matter the order you'd still have to hit the macro twice to remove Netherwalk. First to cast it, second to remove it, no matter the order.

I think it is because macro exit if found a valid command.