An Update on Additional Macro Slots

[Instrumentality]

Like what Laraul(above) is saying, can we get a plain english translation? :P
I cant even begin to understand programming stuff so it would be nice if someone could summarise whats being said and what it means for macros.

They're working on it. Please be patient.

[Asheilin]

As a healer I use dps macros that do this:

/ac "Aero" <t>
/ac "Aero" <tt>
/ac "Aero" <ft>

and during ANY time I'm dpsing as a healer I get a constant error message on my screen. "Invalid Target" Yes, I am aware I'm targeting a party member; thanks you macro >.> Any way we can get rid of that?

[dvoraen]

As a healer I use dps macros that do this:

and during ANY time I'm dpsing as a healer I get a constant error message on my screen. "Invalid Target" Yes, I am aware I'm targeting a party member; thanks you macro >.> Any way we can get rid of that?

May I introduce you to the following command (assuming your macro/-s has/have space for it)?

/? macroerror <- do this in game and read the result. Should be self-explanatory.

[Sida]

May I introduce you to the following command (assuming your macro/-s has/have space for it)?

/? macroerror <- do this in game and read the result. Should be self-explanatory.

→Display or hide text command errors within a user macro. Any errors are displayed upon macro execution. Setting resets to on after macro is executed.

While the explanation is explanatory to a degree, it doesn't do what we want it to do. It does not remove the onscreen chime+text for things like "you can't do this as you're already doing something else" which is one major way to use the fall through quality of the macro interface. I have tested that particlar command thoroughly and can say it's useless at last for my macro error woes. It removes the error messages generated during the macro, but displays them in the end anyway. For short macros the difference is unnoticeable, in practise the command doesn't work.

[EinherjarLucian]

→Display or hide text command errors within a user macro. Any errors are displayed upon macro execution. Setting resets to on after macro is executed.

While the explanation is explanatory to a degree, it doesn't do what we want it to do. It does not remove the onscreen chime+text for things like "you can't do this as you're already doing something else" which is one major way to use the fall through quality of the macro interface. I have tested that particlar command thoroughly and can say it's useless at last for my macro error woes. It removes the error messages generated during the macro, but displays them in the end anyway. For short macros the difference is unnoticeable, in practise the command doesn't work.

Try /recasterror and /actionerror, the three together (with /macroerror) are probably what you're looking for.

[Marveth]

explanation

I seriously hope people read this before answering further. Some of the replies in this thread are scary.

[Sida]

Nope, tried through them too. Recast error does nothing for overloaded macros as im not recasting anything and actionerror actally sets the game setting that's related to them. Which is off on me in te first place. At this point me and multiple other people have come to conclusion that you simply can't remove the pesky errors so while I would welcome you to offer a working and tested solution, would be overjoyed in fact, just listing vaguely error related commands from the documentation is something we went through already by ourselves.

[EinherjarLucian]

Nope, tried through them too. Recast error does nothing for overloaded macros as im not recasting anything and actionerror actally sets the game setting that's related to them. Which is off on me in te first place. At this point me and multiple other people have come to conclusion that you simply can't remove the pesky errors so while I would welcome you to offer a working and tested solution, would be overjoyed in fact, just listing vaguely error related commands from the documentation is something we went through already by ourselves.

For the thing I was using it for, it worked fine. Tested it before I posted it. Perhaps it doesn't work for your specific application. Ah well, YMMV!

[Sida]

For the thing I was using it for, it worked fine. Tested it before I posted it. Perhaps it doesn't work for your specific application. Ah well, YMMV!

Can you post the macro you were using it for? Maybe there is something then that can give some idea how to make it work. Mine is

/micon "Company Chocobo" mount
/ac "Mount Roulette"
/mount "Company Chocobo"
/ac Sprint

To summon random mount if in mountable area, to mount my chocobo if my companion is out and to use sprint if in city or dungeon (or in fight, in essence unable to summon mount). It works to what I want it to work, but if I'm summoning mount it throws error "already using an item" and if using sprint it says "unable to mount" adding the aforementioned macro error commands in any configuration to it has not been working to remove them.