[Feral Druid] Rake stun Thread

[Alkazar]

Merging pounce and rake was smart idea at first but now I can see its limitations too and I need some advice in the end
First of all useful stuff:

ADDON
- Lose Control
I was using this entire MOP and now i cannot play withou it. This addon was not updated to WOD so its useless for ferals
BUT! I have modified it to display rake stun (with support of omniCC) Now it display seconds and miliseconds of your stun
You can download it Here

- OmniCC
You can download it Here
Config:
config1
config2


MACRO

#showtooltip prowl
/cast [nostance:2] !Cat Form(Shapeshift)
/cast [mod:ctrl] Shadowmeld(Racial)
/cast !Prowl
/stopattack
/cast [stealth] Rake
/stopattack
/script UIErrorsFrame:Clear()
/stopmacro [stealth]
/cast !Cat Form(Shapeshift)

This is my insane macro for stealth,shadowmeld,opener and shapeshifting in one button. It saves a lot of keybind space. Now what it does:
1) if you are in other stance than cat - turn cat, if possible cast prowl
2) if you are in stealth - opener
3) if you are in combat - shapeshift
4) if you are in combat and pressed ctrl - shadowmeld + prowl (need to be pressed 2x)

-LIMITATIONS:
May be bugs im not sure, tell me in coments

/cast Prowl
/cast [stealth] Rake

This should turn you into stealth and stun your target if its near. It instead turn you into stealth, cancel stealth and cast rake without stun


- Other limitations:
Rake itself have /startattack command by default built in.
Sometimes
1) When you go prowl and then quickly use rake and your GCD is not up, it instead of stunning my target autoattack instead and you loose Prowl+opener
2) Your target is moving. your range is 5yd and you shlould stun succefuly but thanks to world lag only auto attack land and your opener is !@#$ed /stopattack command is not solution

Tell me pls in coments what do you think about about it limitation or bug?



Edit RESOLVED
--------------------------------------------------------------------------------------------------------------
- Rake autoattack in stealth may be fixed in later patch

Final macro:

#showtooltip prowl
/cast [nostance:2] !Cat Form
[COLOR="#FFFF00"]/castsequence [mod:ctrl] reset=120 Shadowmeld, !Prowl[/COLOR]
/stopattack
/cast [nocombat, nostealth] !prowl;  [nocombat, stealth] rake
/stopattack
/script UIErrorsFrame:Clear()
/stopmacro [stealth]
/cast !Cat Form

Night Elf ONLY

 

[Rai]

omniCC is a must have
use it now 3 years...

 

[Vail]

I think if I understand what you want, this might work better for your second macro...

/cast [nocombat,nostealth]Prowl;Rake

If you are not in combat and are not stealthed then: Cast Prowl
Otherwise: Cast Rake on the currently targeted unit

 

[Pooh]

I think if I understand what you want, this might work better for your second macro...

/cast [nocombat,nostealth]Prowl;Rake

If you are not in combat and are not stealthed then: Cast Prowl
Otherwise: Cast Rake on the currently targeted unit

Can you give me a link on who to create macros?

 

[Vail]

Can you give me a link on who to create macros?

It's just something you pick up over time. Not to be patronizing, but there is some stuff you can browse through though:
Making a macro - WoWWiki - Your guide to the World of Warcraft

This thing here hasn't been updated since, I think, Wrath, but since macro language hasn't changed in that time it still works. Basically you can type a macro into it, and it will tell you what that macro will do.
Fitzcairn's Macro Explain-o-matic

 

[Kincaide]

Can you give me a link on who to create macros?

If you have any specific questions on macros, go ahead and start a thread. I love macros, and I love figuring out how to make them as efficient and functional as possible. You could start a thread called "The Macro Questions Thread" and I'm sure a lot of macro-heads would be happy to help.

 

[Alkazar]

I think if I understand what you want, this might work better for your second macro...

/cast [nocombat,nostealth]Prowl;Rake

If you are not in combat and are not stealthed then: Cast Prowl
Otherwise: Cast Rake on the currently targeted unit

Thanks for response but this is not what I meant. The second macro you call it is just part of first macro separated. What it should do if not in combat is: go prowl and then quickly stun target from stealth but it doesn't. I think it's because it is so quick that rake don't make it to stealth "version" if you know what I mean
/cast [stealth] Rake is not a solution it just ignores that condition.
You can try it for yourself if you have druid

 

[Kincaide]

What it should do if not in combat is: go prowl and then quickly stun target from stealth but it doesn't. I think it's because it is so quick that rake don't make it to stealth "version" if you know what I mean

I think you're on the right track here. All the lines in the macro are applied simultaneously, not in sequence. The macro is read in sequence--that's why a /stop command can cancel part of a macro--but the application of the pieces of the macro are run at a simultaneous condition. In other words, from the macro's point of view, all pieces of the macro acknowledge the nostealth state that you were in when the macro began.

Your best bet to get around that is to carefully set up conditionals such that hitting the macro twice will accomplish what you want.

I have more I could say on the subject of druid macros, but I'm a resto so this specific situation (Rake) is not one that I have experience with.

 

[Vail]

Thanks for response but this is not what I meant. The second macro you call it is just part of first macro separated. What it should do if not in combat is: go prowl and then quickly stun target from stealth but it doesn't. I think it's because it is so quick that rake don't make it to stealth "version" if you know what I mean
/cast [stealth] Rake is not a solution it just ignores that condition.
You can try it for yourself if you have druid

/cast [nocombat] !Prowl
/cast [stealth] Rake
/stopattack [stealth]

I don't have a feral spec druid atm, but I tried it with Shred in place of Rake and it seemed to work.

 

[Tilt Shift]

- Other limitations:
Rake itself have /startattack command by default built in.
Sometimes
1) When you go prowl and then quickly use rake and your GCD is not up, it instead of stunning my target autoattack instead and you loose Prowl+opener
2) Your target is moving. your range is 5yd and you shlould stun succefuly but thanks to world lag only auto attack land and your opener is !@#$ed /stopattack command is not solution

Tell me pls in coments what do you think about about it limitation or bug?

I've not experienced this. A white hit reports before rake and you can see the damage on screen and on-log, but the system seems to resolve this attack after the stun. Just adding a data point.

 

[Alkazar]

I think you're on the right track here. All the lines in the macro are applied simultaneously, not in sequence. The macro is read in sequence--that's why a /stop command can cancel part of a macro--but the application of the pieces of the macro are run at a simultaneous condition. In other words, from the macro's point of view, all pieces of the macro acknowledge the nostealth state that you were in when the macro began.

Your best bet to get around that is to carefully set up conditionals such that hitting the macro twice will accomplish what you want.

I have more I could say on the subject of druid macros, but I'm a resto so this specific situation (Rake) is not one that I have experience with.

Rly? Thats new for me. Interesting.

/cast [nocombat] !Prowl
/cast [stealth] Rake
/stopattack [stealth]

I don't have a feral spec druid atm, but I tried it with Shred in place of Rake and it seemed to work.

Same result

I've not experienced this. A white hit reports before rake and you can see the damage on screen and on-log, but the system seems to resolve this attack after the stun. Just adding a data point.

Strange! My rake stun always hits as last....

I dont get it. Is EU wow different from US? I dont think so

 

[Vail]

Strange! My rake stun always hits as last....

I dont get it. Is EU wow different from US? I dont think so

The exclamation point ((!)) before prowl prevents you from leaving prowl no matter how many times you hit the button, meaning in the macro I listed, you should only be able to go INTO stealth. You will not unstealth prematurely as you are here.

 

[Alkazar]

The exclamation point ((!)) before prowl prevents you from leaving prowl no matter how many times you hit the button, meaning in the macro I listed, you should only be able to go INTO stealth. You will not stealth prematurely as you are here.

I know what (!) do. I was using exactly your macro. but no matter what rake stun always hit as last.
I think its because rake is written something like this:

-startattack
-apply DoT
-apply stun if in stealth

that startattack is almost in every ability these days (exceptions are stun openers such as Cheap Shot). I know its freshly new ability so I think they will fix it like this:

-apply stun if stealth
-apply DoT
-startattack only in NOstealth

On the other hand I resolved my issue with quick stealth-rake thanks to Kincaide "castsequence what a brilliant idea "

#showtooltip prowl
/cast [nostance:2] !Cat Form
/cast [mod:ctrl] Shadowmeld
/castsequence [nocombat, nostealth] !prowl;  [nocombat, stealth] rake
/stopattack
/script UIErrorsFrame:Clear()
/stopmacro [stealth]
/cast !Cat Form

 

[Kincaide]

On the other hand I resolved my issue with quick stealth-rake thanks to Kincaide "castsequence what a brilliant idea "

#showtooltip prowl
/cast [nostance:2] !Cat Form
/cast [mod:ctrl] Shadowmeld
/castsequence [nocombat, nostealth] !prowl;  [nocombat, stealth] rake
/stopattack
/script UIErrorsFrame:Clear()
/stopmacro [stealth]
/cast !Cat Form

I'm glad that something I said helped you figure it out! However, I would never recommend /castsequence and I think /castsequence is a terrible command I think you can get what you want with just carefully layered conditionals.

There appear to me to be conflicting or redundant elements in your macro, and if it works for you then great let's not mess with it, but if you'd like to get it more efficient or reliable, we can probably tighten it up even more. But I'm not completely clear on what you want it to do in each potential circumstance so I can't advise more precisely without knowing.