Quote Originally Posted by Xlantaa View Post
Weel, you can "cheat" a bit to have this. By using macros. For Example:

/micon "Sonte III"
/ac "Stone III"
/ac "Stone II"
/ac "Stone"

This way, if you have Stone III, use stone III, if you haven't III, then will use the next one, Stone II. Of course, this is annoying because you will read the error message “Stone III” is not a valid action name" all the time on screen...
One problem with this solution is that Stone actually has some extra utility than damage. It's one of WHM/CNJ's crowd-control abilities, with its added weight effect. I used this sort of macro for a while, and was occasionally frustrated when weight could have come in handy but was not easily accessed.

That said, there ARE a lot of abilities that can be combined nicely into one macro. For example, this one I use on PLD:

/micon "Cover"
/action "Shield Bash" <t>
/action "Shield Lob" <t>
/action "Cover" <t>

In this case, the macro works reliably because each action in it is viable under different circumstances.
- Is the target an ally? Then Shield Bash and Shield Lob do not apply. Cover is used.
- Is the target an enemy? If the enemy is close enough, then Shield Bash is used. If not, Shield Lob is used.

There are lots of abilities that can be combined into one button, since they have different valid targets. Unfortunately, Cure spells do NOT work reliably in this way, as they have a default target of yourself. Here's what I mean. Take, for example, this macro I used for a while:

/micon "Cure"
/action "Stone" <t>
/action "Cure" <t>

In theory, if you're targeting an enemy, it should use Stone, and if you're targeting a player it should use Cure right? Normally, that's true - but if you're button-mashing, or even trying to just cast as soon as you can after a previous action, there's a chance you'll clip off the first command and move on to the second. Suddenly, you're casting a totally useless Cure on yourself when you meant to cast Stone. This might not seem like it would come up much, but it happens surprisingly often.

It makes me SERIOUSLY wish you could disable "Target self by default" for Cures and buffs. "Default: Self" is really only useful when soloing content - and even there, it's kind of a crutch that's simply not needed by practiced players. In harder stuff, even if you're NOT using macros, it's all-too easy to accidentally cast a cure spell while you have the enemy targeted, wind up curing yourself, and wondering why the tank is still dying...