Feral Cat Macro helpFollow

I don't think you can add modifiers like that into a macro. Macros do not have conditional statements like if this than that.

The only problem I can see is that Tiger Fury has a cool down that might make this hang up. Here is a link to a site that has some examples of Feral macros. Check it out: http://druid.wikispaces.com/Macro's+and+Addons#toc6

Macros do indeed have conditional statements, but none of them will allow you to do what you are describing here.

Macro conditionals cannot watch your CP and are not intelligent enough to identify buffs/debuffs. You will have to make those decisions yourself. However, if Tiger's Fury is off the GCD (my memory is fuzzy since I haven't used it in forever and don't have KotJ):

#showtooltip 
/cast Tiger's Fury 
/cast Rake

Should at least combine those two actions in one press. If Tiger's Fury triggers the GCD, then you can do:

#showtooltip 
/castsequence reset=30 Tiger's Fury, Rake

This will require you to press the button twice to perform both actions, but it should still work. Note it will not work again as long as TF is on cooldown; the macro will not roll forward until it can accomplish each task in the list successively.

Edit: The macro you have will not work under any circumstances since multiples of those abilities trigger the GCD and will halt the macro immediately if it cannot proceed further.

Edited, Jan 2nd 2009 2:13pm by Norellicus

Why are you spamming Rake?

You should let the DoT run its course, then reapply.

Spam Mangle or Shred. All other cat attacks are more situational.

Also what is your DPS rotation?

Isn't that true for everyone? :)

I noticed a huge increase in 'skill' when I keybound everything and started using more conditionals. Everyone needs to be told at some point. It will up your effectiveness by a huge margin. Clicking skills that aren't non-combat skill is just foolishness.

The whole keybind thing is what actually started me on my make a new UI quest. I have a whole bar of hidden keybinds. Its caster form but the 1-= keys have about 3 conditionals on them in any form. The 2 side bars hide in combat and Revive and Brez swap via combat status.

That being said things that involve stuff with divergent cooldowns should not be macro'd as one spammable macro. Too many things have different durations. They also have different priorities and macros can not account for that. The type of macro you are trying to make is not a good idea for that reason.

Keep the questions coming though it is the only way to learn.

I was reading some info and it appears i should spam claw for now so ill switch my macro.

Edited, Jan 5th 2009 10:44am by nevercrits

As you level you'll get more and more attacks, and combat will become (a little) more complex.

Regarding the creation and use of macros, I think you'd get a lot out of the discussion in this post.

The general idea is that instead of trying to use macros to execute predefined sequences of moves, which get increasingly clumsy, you use them to set up conditionals that make it so a given button/key does the right move if you're in combat or out of combat. This saves bar space and reduces the numbers of keys you have to click in combat. For example, your 1 key will Pounce if you're in stealth or Mangle if you're in combat.

Hiya,

To the OP: indeed, as was mentioned above, your first post was not the best post ever posted. But hey, you are in the friendly neighborhood, so not much harm done here.

I have not seen this in replies yet, but when levelling, I turn your macros around. Something like this:

/cast Pounce
/cast Tiger's Fury

and even

/cast Claw
/cast Tiger's Fury

Granted, my opener/attack does not get the benefit of TF, but at this way, Tiger's Fury is up as much as possible. I tend to forget about specials like TF, trinkets etc, so for me it is a godsend. Maximum uptime but a bit loss in the start.

As a second opinion on "sequenced" macros: try to avoid them. Situations change, certainly when soloing (levelling), so you best start training the use of your appropriate abilities at appropriate times. When you sequence and something goes wrong, you have to start looking for other buttons, which is at the very least... inconvenient.

Pffff I hope the above makes any sense, because I am too tired right now to read it back again. (sorry in advance)