Macro Settings

[Nepharius]

I'd like to toggle a setting that will cancel my macro if an error is encountered. I, like many crafters, often use macros. Even on good days it is not uncommon for a short moment of lag to cause my macro to skip an action wasting my time and resources. I'd rather complete the recipe manually from that point in the rotation than risk the HQ or even the durability.

[Seraphor]

If you're watching it and want to intervene manually, then just set up another Macro with a single benign action.
Macro's interrupt each other so just click that one to stop the other.

Macro's can't do IF functions, at that point they begin to compute and actually play the game for you, and you could create so many broken macro's with just an IF function alone that would break the game in so many ways. You'd essentially be condoning botting.

[Liam_Harper]

Macro's can't do IF functions, at that point they begin to compute and actually play the game for you, and you could create so many broken macro's with just an IF function alone that would break the game in so many ways. You'd essentially be condoning botting.

To be fair, I'm not sure how the option to simply auto-quit a macro in the case of a failed action would cause automated gameplay. The macro would only abandon on failure and nothing more. Do you have an example of how this would equal botting?

Another thing I'd really like to see with macros is the option to have them queueable but only for single action macros. Things such as raise, shirk, asylum on target, mouseover heals and so on. Not allowing macros to queue is perfectly reasonable to prevent automated combat strings, but entirely unnecessary for single QoL buttons.

[Seraphor]

To be fair, I'm not sure how the option to simply auto-quit a macro in the case of a failed action would cause automated gameplay. The macro would only abandon on failure and nothing more. Do you have an example of how this would equal botting?

Another thing I'd really like to see with macros is the option to have them queueable but only for single action macros. Things such as raise, shirk, asylum on target, mouseover heals and so on. Not allowing macros to queue is perfectly reasonable to prevent automated combat strings, but entirely unnecessary for single QoL buttons.

If it was specifically to END if something fails, no, that wouldn't be a problem.
But what does it recognise as failure? With crafting, and talking about lag spikes skipping steps, that's not a clear cut 'failure' that the game could automatically recognise, it's a subjective condition. It's merely a string of actions that didn't execute in the order you wanted them to. Which is why it would require an IF function.
You would have to design the condition that IF [this] THEN [that]. e.g. IF /ac "Waste not" = false THEN /ac "Waste not"

But this IF THEN capability could be used for many, many more things than simply adjusting your crafting macro, and could allow you to do all sorts of things you shouldn't be able to do, and blur the line between Macro's and Bots.

[Sove92]

The /macrocancel command should do what you are asking.

[Mhaeric]

The /macrocancel command should do what you are asking.

Just a note that this needs to be entered manually if using /mlock in your macros, because /mlock prevents other macros from working.

I would love to have a new general action or something similar that cancelled an active macro. Since it isn't a macro it could be used to cancel an /mlocked macro too.

[Luna-M]

I'd like to toggle a setting that will cancel my macro if an error is encountered. I, like many crafters, often use macros. Even on good days it is not uncommon for a short moment of lag to cause my macro to skip an action wasting my time and resources. I'd rather complete the recipe manually from that point in the rotation than risk the HQ or even the durability.

Not a solution but there is a hotkey for cancelling macros, so you can manually hit that when that happens.

[Absurdity]

Not sure if you're already doing it but since there is no "cancel macro if error occurs" function I'd suggest adding the <wait> function after every action in a macro. It differs from ability to ability but a <wait.3> generally makes the game wait long enough before the next action to account for sudden lag. If the lags get so bad that even 3 seconds aren't enough you can simply increase the wait time by a second.