Dear Devs: Macro Command - Wait

[xSinful_Snake]

What is the macro command for calling an additional macro at the end of your initial macro?

[Tirocupidus]

What is the macro command for calling an additional macro at the end of your initial macro?

I think that person was talking about a special keyboard that can do that. You can't do it in the game interface.

[Araye]

If you are granted that which you wish, they will reduce the number of command lines to 7. Smile

[xSinful_Snake]

I think that person was talking about a special keyboard that can do that. You can't do it in the game interface.

Darn, given tha I'm a ps3 player, I can't rely on such a device.

[xSinful_Snake]

I think what Sinful_Snake is getting at is streamlining. On my way to 50 Weaver, there were a number of times it would have been more convenient to have a single macro rather than two performing the same synthesis hundreds of times over. Granted, pressing two buttons as opposed to one isn't the end of the world, but I don't think it's unreasonable to suggest a function that worked well in FFXI to be implemented here. /wait takes up a line that could be used for more complex and productive macros, making everyone who uses macros for legitimate purposes happier.

Finally someone who understands my perspective on the issue.

[Ekko]

And bring back the decimals !

[Camate]

Greetings,

Apologies for the bump and also for the delay in a response, but we received some information from the development team that in patch 2.2 we’ll be making it so wait commands can be placed after other commands on the same line.

For example:
/ac “Swiftcast” <me> <wait.1>
/ac “Raise” <t>

You’ll notice that for the parameter after wait, you need to add period and not a space. Also, when omitting this parameter it will be taken as “1.”

Hopefully this helps for creating a bit more space in your macros.

[Mordermi]

Greetings,

Apologies for the bump and also for the delay in a response, but we received some information from the development team that in patch 2.2 we’ll be making it so wait commands can be placed after other commands on the same line.

For example:
/ac “Swiftcast” &lt;me&gt; &lt;wait.1&gt;
/ac “Raise” &lt;t&gt;

You’ll notice that for the parameter after wait, you need to add period and not a space. Also, when omitting this parameter it will be taken as “1.”

Hopefully this helps for creating a bit more space in your macros.

Awesome! Thanks for delivering this great news!

[Tano]

Greetings,

Apologies for the bump and also for the delay in a response, but we received some information from the development team that in patch 2.2 we’ll be making it so wait commands can be placed after other commands on the same line.

For example:
/ac “Swiftcast” &lt;me&gt; &lt;wait.1&gt;
/ac “Raise” &lt;t&gt;

You’ll notice that for the parameter after wait, you need to add period and not a space. Also, when omitting this parameter it will be taken as “1.”

Hopefully this helps for creating a bit more space in your macros.

I'd like a "wait until previous action is done" command as default for <wait> onstead of 1s.
I'm currently using 0.5s as default wait time for instant actions, but it feels like it's too much (and 0.4s simply doesn't work all the time)

[Zirael_Foxfire]

Would be nice if macro wait command allowed decimal points instead of full seconds. And 0.5 second 'precast' is missing from macroed actions compared to not macroed actions.