Let's Talk About Macros!

[Niwashi]

The /merror command therefore should not be adjusted to suppress these messages, but a general interface setting should allow their suppression independent of the method of their generation.

But it shouldn't be independent of the method of generation, because in one method those represent failures, whereas in another they're intended.

If you use a skill directly (or rather try to) and the situation doesn't allow for it, you'd generally still want to be warned about that. Where people don't want to be warned is specifically when it comes from a macro that's designed to have these actions fail (like the <t> or <tt> pattern, where you hope one of the two commands succeeds, but the other will always fail). People want to be able to tell the system not to use those warnings for these particular commands, but still warn on the same errors in direct commands.

[Tonjiar]

This would be usefull. If they added this it would make stances slightly better. as I could then macro kiss of the wasp to replace itself with kiss of the viper when I used it and vice versa.
would save slots on hotbars.

So this is completely possible right now but it is on a by a full hotbar basis.

I have two macros for swapping my ninja stances

/micon "Kiss of the Viper"
/ac "Kiss of the Viper" <me>
/hotbar copy rog 2 nin 3

and

/micon "Kiss of the Wasp"
/ac "Kiss of the Wasp" <me>
/hotbar copy rog 3 nin 3

I created my ninja 3 hotbar and copied it over to rogue since I have hotbars in the rogue class that will never be used anymore. Only difference is one of the buttons on bar 2 is the kiss of the wasp macro and the same position on bar 3 is the kiss of the viper macro.

[dragonseth07]

So this is completely possible right now but it is on a by a full hotbar basis.

I have two macros for swapping my ninja stances

/micon "Kiss of the Viper"
/ac "Kiss of the Viper" <me>
/hotbar copy rog 2 nin 3

and

/micon "Kiss of the Wasp"
/ac "Kiss of the Wasp" <me>
/hotbar copy rog 3 nin 3

I created my ninja 3 hotbar and copied it over to rogue since I have hotbars in the rogue class that will never be used anymore. Only difference is one of the buttons on bar 2 is the kiss of the wasp macro and the same position on bar 3 is the kiss of the viper macro.

I never would have thought to use Classes as hotbar mules. You, sir, are a genius.

[CarrotParfait]

OP: What are the problems with macros as they work in FFXIV?

The biggest problem with macros is that they are
A. client-side only and
B. can't queue actions

Unlike skills and abilities, the client won't let you execute a macro before you are off the global cooldown. The client has to believe that no other action is executing before it will let you execute a macro, which introduces lag to and from the server on any ability executed from a macro. It also means that you have to repeatedly click on a macro to make sure that it actually executes ASAP, which can be annoying if you tied party chat to your macro.

The biggest improvement would be to allow the client to accept the button press for a macro while other skills are being activated, and queue up the execution of that macro.

[Studly]

I really want a smart cast option. Similar to <mo> but have a ground aoe cast where the center is where my mouse is. For things like shadowflare, salted earth, ect. There are many time in which you want those aoes to hit two mobs that have a gap between them and just casting at <mo> or at <t> will only hit one set of mobs cause it is centered on single mob. I want to put my mouse in the gap between the two mobs and have my aoe skill cast there on the ground.

[Lucielle]

I never would have thought to use Classes as hotbar mules. You, sir, are a genius.

While I won't argue that he's got a clever method for rotating hotbars to work around the lack of a macro assigning command (I use a similar method myself on WAR and DRK), it doesn't lessen the fact that having the option to simply place a macro from our macro menu directly into the hotbar via a command would be incredibly useful and that it's bizarre that we can't, especially considering we can put basically anything else on the hotbar you can think of using similar text commands. It's a functionality that feels conspicuously 'artificially absent'.