My easy controller setup for WAR

[karateorangutang]

#aintgottimeforthat

but you have time to die and get rezzed?

[whiskeybravo]

but you have time to die and get rezzed?

That's a slight misrepresentation but I'll entertain for a few seconds. It has a cascading effect. If I delayed anything on DRG, I don't get full potency of buffs, I could lose BotD from even a 1 sec delay at certain points, or even on WAR it might make it more difficult or downright impossible to land 3 FCs under berserk. Why risk all that when all it takes is getting used to a wider setup? If all it takes is a slight adjustment of pressing a button, that's the same as a slight adjustment of your hotbars to be better optimized. As in the provoke example, when you need to provoke you need it to go off immediately, not spam the button 5 times hoping it goes off in time. Again, I make due with just a few, but they still have their problems. And when you say "I've never had a problem in hundreds of attempts" I'm calling BS lol

[karateorangutang]

That's a slight misrepresentation but I'll entertain for a few seconds. It has a cascading effect. If I delayed anything on DRG, I don't get full potency of buffs, I could lose BotD from even a 1 sec delay at certain points, or even on WAR it might make it more difficult or downright impossible to land 3 FCs under berserk. Why risk all that when all it takes is getting used to a wider setup? If all it takes is a slight adjustment of pressing a button, that's the same as a slight adjustment of your hotbars to be better optimized. As in the provoke example, when you need to provoke you need it to go off immediately, not spam the button 5 times hoping it goes off in time. Again, I make due with just a few, but they still have their problems. And when you say "I've never had a problem in hundreds of attempts" I'm calling BS lol

Ok so to the point of my retort, that was simply my bad sense of humor at work and wasn't meant to offend. So allow me to entertain you for a minute.

We all know macros suffer from animation lock. I'm not arguing otherwise. It's tested and proven in the game engine. I too try to limit my macro's and make them in such a way so they are less hindering.

First off, I would never macro provoke or any ability that would be necessary to pull a mob from anyone else.
Secondly, animation can be overcome with simple timing. If your accustomed to playing games with tight twitch timing, this game as an absurdly large animation lock window. Its is literally more than a half a second, which is years in most game engines. Overcoming that is as simple act of timing your presses to not interfere with the queue, which honestly isn't that hard. Even with ping changes that only makes it easier as information is sent slower so it would happen even less.

That being said for some it could be a greater risk. I get that it doesn't work for everyone, but that doesn't mean it can't be the better option for some. I'd rather time a button than smash another button and look for abilities on the fly.

Additionally, 3 FC's is not a difficult feat. It's easy to achieve with a good 1.5 second grace window at the end. With Astro buffs it's even good enough to throw a fracture at the end. Honestly server ping is a bigger issue than macro's will ever be.

[nssixn6]

I should note that the order of the condensed macros is optimized for TFCing. If there isn't an add phase or tank swap coming up. Vengeance is wasted/burned for a Wrath stack. If big damage is coming I burn the RI/A macro.

My TFC is: HS,M,SE,HS,SS,BB, HS, Beserk, FC, M, SE, HS, RI/A or V, SS, BB, FC, Infuriate, FC, Frac, pac (or WP if bard sets up right)

As for the Mercy Stroke/ Tomahawk thing, it works because both action are context sensitive.
If gcd is still refreshing, Tomahawk is impossible, so it is ignored. If the the target is out of melee range, but below 20%, still on gcd, then nothing happens. If the target is below 20%, in melee range, then ms is used.