Dear Devs: Macro Command - Wait

[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)