User Macros: New Options + Sharing Macros with others in game

It would be great if we can share our macros with friends, it would help others learn fun macros, and it would make it easier for non-keyboard players to get a macro from a friend with a keyboard. :)

As for new options, It would be great if we could have a macro that worked as an "order" of presses, rather then having to build in a "wait" option, the macro would work as an order of the skills listed until the target changed.

For example:

/ac "Heavy Swing" <ut>
/ac "Skull Sunder" <ut>
/ac "Butchers Block" <ut>

Each time the macro button was pressed, one skill would go off. The first time skill one "Heavy Swing" would go, the next time pressed, "Skull Sunder", and the third time pressed, "Butchers Block", it would then cycle back again, unless the target was changed.

Anyway, this would be a cool feature especially as the game grows and we get new skills.

The issue I see would be if the skill missed and the combo action didn't happen. I think if we wanted to go above and beyond, we could have something like the following:

/ac "Heavy Swing" <ct>
/ac "Skull Sunder" <ct>
/ac "Butchers Block" <ct>

This would function the same way as above, but only move onto the next skill if combo (or proc) is triggered. No combo, or changing the target, would have the skills start over with first line, followed by the rest, and then start back over after the last skill.

I could see this as a big help for controller players to return a lot of skills slots back.

Anyway, thanks for your time and consideration.

I had a similar question once. Here's the answer I got:

Here is the macro feature policy for FFXIV:
Do not make it so macros must be used.Minimizing and optimizing actions without error beyond that of human control is not allowed.Make it a support feature that can be used by people that are a bit shaky at controlling the game to ensure control, while not making it 100% optimized.The player makes the execution decision. We will not be implementing a feature where the macros makes its own decisions. For example: We will not be implementing a feature that executes things based on certain criteria (player status, enemy HP, certain actions, etc )

Quote:

---

Originally Posted by nexas506

I had a similar question once. Here's the answer I got:

Here is the macro feature policy for FFXIV:
Do not make it so macros must be used.Minimizing and optimizing actions without error beyond that of human control is not allowed.Make it a support feature that can be used by people that are a bit shaky at controlling the game to ensure control, while not making it 100% optimized.The player makes the execution decision. We will not be implementing a feature where the macros makes its own decisions. For example: We will not be implementing a feature that executes things based on certain criteria (player status, enemy HP, certain actions, etc )

---

A macro that executes a sequence of actions one after another is not something that's "beyond that of human control." The primary purpose of macros is to do a specific sequence of events. It also provides the means to overcome shortcomings of the user interface.

Quote:

---

Originally Posted by Laraul

A macro that executes a sequence of actions one after another is not something that's "beyond that of human control."

---

The first pattern the OP discussed was a straight sequence of events, but the second was putting the logic and decision making in the software so that the player wasn't deciding what skill should come next. So the <ut> pattern first discussed could perhaps be allowed (and can in fact be done now by duplicating and swapping out hotbars, though that's a much clunkier setup), but as pointed out, it has the downside of not recognizing if a combo action is truly available. The alternative <ct> version for fixing that problem breaks the rule about software decision making.

The first part is the one I agree with. Why doesn't /ac queue an action the same way as when you press the key? Normally you can press something and it will queue as your next action. Put it in a macro and suddenly that's not true, making it fail if you clip the animation in even the slightest.

For the second, no. There is a somewhat close feature I do want, however. I would like macros to be able to break (stop) if an action in the macro physically cannot/does not execute (on cooldown, not procced for, player stunned/out of range, etc.) It goes with the above, relying on an order of events, but no finer conditions than that. If the order is broken, the macro halts.

The original statement about the Macro Policy for Final Fantasy XIV was in response to restoring /wait times w/ decimals instead of rounding up or down, as it behaved like in the Beta versions. The explanation doesn't quite explain the reason why it was removed was seen as a benefit in the beta versions. The decision to remove it, like so many decisions, was done arbitrarily. My guess is that the dev team doesn't play the game that much, and for the most part underestimate players' intelligence.

Macros that allow us to reduce the amount of Keybinds should not be considered against FFXIV Macro feature policy.
It is still our decision to press the Macro button.

In fact, SE is hypocritical in their "policy" because they gave us the /wait command, which DOES allow for automated actions.

I would gladly give up the /wait command, in exchange for:
1 - Letting Macros queue like normal actions.
I use mouseover macros for healing, for example, and would be nice if I could queue the next cast while the current one is finishing.
2 - Letting me choose simple, harmless conditions for targets (if mouseover target is enemy, cast Aero, but if it's friendly, cast Cure).
None of the above are exploitative nor do they remove choice from the player.

I tried to make macros for cycle of skills in current scheme. It requires three extra XHBs and four macros. XHB changes regardless of missed skill.

XHB6
/ac "Heavy Swing" <t>
/chotbar copy current 7 current 1

XHB7
/chotbar copy current 8 current 1
/ac "Skull Sunder" <t>

XHB8
/chotbar copy current 6 current 1
/ac "Butchers Block" <t>

XHB6, 7, 8
/chotbar copy current 6 current 1
/nexttarget

As for queueing, I use the following <mo> macro. It works even if I use it about 0.4sec before GCD. I must hold a mouse a while, though.
/merror off
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/ac "Cure" <mo>
/micon "Cure"

Quote:

---

Originally Posted by Nurvus

(if mouseover target is enemy, cast Aero, but if it's friendly, cast Cure).

---

I suppose that the next macro works.
/ac "Aero" <mo>
/ac "Cure" <mo>

Quote:

---

Originally Posted by Mikoko_Miko

I suppose that the next macro works.
/ac "Aero" <mo>
/ac "Cure" <mo>

---

Yes, but for example, in WoW, even the icon changes dynamically according to macro conditions.
In the above example, the icon would change depending on whether I'm mousing over an enemy or an ally, or none at all.

In FFXIV almost every "solution" involves bruteforcing your way through action spam, as the game tries to cast both but only manages one.
Same with your "queue" Macro.
All you're doing is spamming countless actions and one of them should eventually go through.

What if your macro is meant to heal mouseover, but if none is available, behave normally?

Quote:

---

/ac "Cure" <mo>
/ac "Cure"

---

In this case, your macro wouldn't work.
It's a pointless restriction that shouldn't exist to begin with.

Macros execute one line per frame. So at 30 fps, it will execute the 15th lines 0.5 seconds after the macro is pressed.

I setup combo macros so the first action will create two difference paths ...
This Dark Knight macro goes into the RAU slot on crosshotbars1 & 2.

Quote:

---

/macroicon Syphon Strike
/macroerror
/action Syphon Strike <le>
/macrolock
/crosshotbar set Delirium 1 RAD
/crosshotbar set Souleater 1 RAL

---

To reset the slots, the first action in the combo is a macro which the RAR slots on 1 & 2.

Quote:

---

/macroicon Hard Slash
/macroerror
/action Hard Slash <le>
/macrolock
/crosshotbar set Spinning Slash 1 RAD
/crosshotbar set Power Slash 1 RAL

---

So when I perform the actions.. it goes...
http://i.imgur.com/T8DQEx5.jpg TO http://i.imgur.com/kyv6Uag.jpg

Still Macros are still far too limited, and poorly planned and thought out. Many actions aren't available thanks to level-sync... yet they still end up wasting space on your hotbar. Other actions aren't available unless certain conditions are met, yet they too are always visible. Idiotic, is what it is. No doubt the UI dev teams never bothered playing WoW. Hiroshi Minagawa doesn't really seem to have a clue when it comes to macros or hotbars or actions or anything that you'd expect the head of UI development would have a grasp of. His treatment of macros, removing key functionality w/o reasons likely fueled by a personal bias against macros and there purpose. I've lost all faith in the man. Only thing he's good at is coming up w/ elaborate excuses why things can't be improved. (Okay that's a little harsh. But seriously, what's it gonna take to get this guy to do something?)

Thanks everyone for the feedback. :)

I apologize for posting in such an old thread, but am new to the game and wondering if there were any improvements since this thread started to the macros.

I am specifically looking for a macro to reduce the clutter on my bar. I want to use it not as a cast sequence macro, but more as a if in stance 'x', show this action to be usable, and if in stance 'y', show a different action to be usable.

So for my monk, I want to see that if I am in no stance, or opo-opo stance, show Bootshine in keybind spot 1. If in Raptor stance, show Twin Snakes in keybind spot 1, and if in Couerl stance, show Snap Punch. I would use keybind spots 1-4 to show most of the actions that way (So in each stance change the 1-4 spots would change to only usable actions instead of greyed out abilities).

I see that you can brute force it with changing in and out entire bars, but I find that somewhat unappealing compared to being able to keep the same bar, but have the icons switch as I change forms/stances. This is just really to cut down on the amount of keybinds I have for my main skills shown, so I have more space for specific actions that don't require form/stances.