Dear Devs: Macro Command - Wait

I'm becoming quite familiar with macros as a suitable way to craft as even use in battle however with a 15 command line limitation, I'm wondering why the command "/wait" requires its own line and why it int utilized as "<wait #>" and would be added to the end of a command line.

This is taking up precious command line space so can you please change it?

I definitely agree, with "/wait" requiring its own line there is a huge limitation on what you can do with macros. When I first saw how big the input box was I was so excited at the long strings of commands I thought I would be able to input. Nope, 15 lines max, and half of those are going to be used with "/wait". What a waste of potential that the <wait#> format could alleviate!

I'm glad I'm not the only one who realizes the potential of the macro function. Aside from the "/wait #", I don't really see any other problems with the commands. Fix this ONE issue Devs and you'll have happy players with 15 fun lines of command.

Though if you can't add the command "<wait #>", at least consider giving us an additional 7-8 lines of commands to make up for the /wait lines or nullify /wait from counting towards the 15 line-limitation counter.

Devs, this is crucial to the future of macros in this game, a function built in to the game, can we atleast get some support here?

Having Makros for some quality of life features is absolutly ok. Things like buffing makros or so. But what i don't get is the need to automize nearly everything, at least it sounds so for me.
Have you two a higher target in automizing your game with makros?

Don't misunderstand me, i just want to know it. You can do what you want wth makro as long as it is in line with intended behaviour.

Seems fine to me. If you want the game to play more of the game for you, just make a continuation macro to do what you didn't finish in the first one.

Quote:

---

Originally Posted by Tirocupidus

Seems fine to me. If you want the game to play more of the game for you, just make a continuation macro to do what you didn't finish in the first one.

---

This. You can have macros call and activate other hotbar buttons, near infinitely, probably more then you'll ever need. The basic user will never need what you're asking for, and for users like you, I highly recommend a Corsair K90 series keyboard, or a Logitech G series keyboard, or something else with dedicated hardware macros.

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

Quote:

---

Originally Posted by xSinful_Snake

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.

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

Quote:

---

Originally Posted by Tirocupidus

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.

Quote:

---

Originally Posted by Feilina

Having Makros for some quality of life features is absolutly ok. Things like buffing makros or so. But what i don't get is the need to automize nearly everything, at least it sounds so for me.
Have you two a higher target in automizing your game with makros?

Don't misunderstand me, i just want to know it. You can do what you want wth makro as long as it is in line with intended behaviour.

---

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.

Quote:

---

Originally Posted by Abadacchus

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.

And bring back the decimals !

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. :)

Quote:

---

Originally Posted by 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” &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!

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.

I'd prefer it if /wait simply held the next action until a previous action completed, a la

/ac "Divine Seal" <me>
/wait
/ac "Cure III" <me>

That way we wouldn't have to guess at the number of seconds or fractional seconds required to meet the animation delay on "instant" skills, and we wouldn't lose time or efficiency when Selene is out (hasting our abilities).

Quote:

---

Originally Posted by 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.

---

No one is ever happy.

Quote:

---

Originally Posted by Bridgeburner

I'd prefer it if /wait simply held the next action until a previous action completed, a la

/ac "Divine Seal" <me>
/wait
/ac "Cure III" <me>

That way we wouldn't have to guess at the number of seconds or fractional seconds required to meet the animation delay on "instant" skills, and we wouldn't lose time or efficiency when Selene is out (hasting our abilities).

---

This is pretty much the best solution. If you lag just a little bit in a crafting macro, it'll miss a step and then you'll fail your craft. It'd be best if instead of /ac there was a single command that waited until the skill was available to use, then used it.

How about you guys allow decimals since your game has a, y'know, 2.5 second global cooldown?

Quote:

---

Originally Posted by Bridgeburner

I'd prefer it if /wait simply held the next action until a previous action completed, a la

/ac "Divine Seal" <me>
/wait
/ac "Cure III" <me>

That way we wouldn't have to guess at the number of seconds or fractional seconds required to meet the animation delay on "instant" skills, and we wouldn't lose time or efficiency when Selene is out (hasting our abilities).

---

Fractional seconds worked in Beta, but they took them out stating that they did not want Macros to give players who used them too great of an edge such that all players would feel pressured to make Macros.

/wait times are now rounded to the nearest whole number.

Quote:

---

Originally Posted by Soda

How about you guys allow decimals since your game has a, y'know, 2.5 second global cooldown?

---

They did already state that they are not allowing decimals because the game has a 2.5s GCD, they do not want macros to be GCD-efficient so that you can't let a macro play the game for you.

Quote:

---

Originally Posted by 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” &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)

Quote:

---

Originally Posted by awvv

This is pretty much the best solution. If you lag just a little bit in a crafting macro, it'll miss a step and then you'll fail your craft. It'd be best if instead of /ac there was a single command that waited until the skill was available to use, then used it.

---

However, I realised that if I'm on macro, and if my FF lags, my macro lags as well.

Quote:

---

Originally Posted by Tano

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)

---

0.4s simply doesn't work at all. It defaults to 0s while 0.5s defaults to 1s.

Ohhhh man. Looking forward to emote spam dance routines!

I for one love using macros for crafting. they are especially useful for items you want to craft a lot of, and want/need to HQ them. I mostly use macros for base items with 40 durability, and even then I find that a few extra lines would make the macros cleaner and yes, reduce it to a one button synth from two. Macroing your crafts also lets you look through your inventory/armoury chest (although you can't move anything) or look through our journal or achievements while you are crafting, and it prevents any of those 4 am slip and push 4 when you meant 5 instances. The trade offs are that it takes a slightly longer time per synth, and you have less control i.e. you may end up doing a Great strides over an excellent condition and use your touch ability on the poor that always follows, whereas if you are doing the craft manually, you can adjust for such a situation. All in all, I am hugely appreciative of the new /wait system Camate posted earlier, good work guys!

Quote:

---

Originally Posted by 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.

---

If I remember correctly, this was possible in alpha, but was later taken away from the game because macros are supposed to be an useful tool, but not something that will be better or preferable to actual player input.

Quote:

---

Originally Posted by Smashington

Fractional seconds worked in Beta, but they took them out stating that they did not want Macros to give players who used them too great of an edge such that all players would feel pressured to make Macros.

/wait times are now rounded to the nearest whole number.

---

And that is also why there won't be a "wait until previous action is complete" command - it would create the exact same issue.

I'm looking forward to not having to waste lines on /wait for crafting. Hitting 5,3,4,7,7,7,8,-,1 (my standard rotation) for those 40 durability recipes is pretty mindless and *just* too long for macros as they are now.

Quote:

---

Originally Posted by Abadacchus

I definitely agree, with "/wait" requiring its own line there is a huge limitation on what you can do with macros. When I first saw how big the input box was I was so excited at the long strings of commands I thought I would be able to input. Nope, 15 lines max, and half of those are going to be used with "/wait". What a waste of potential that the <wait#> format could alleviate!

---

You forget that a macro is limited to 180 characters also (including new line characters). That's an average of 12 characters per line if you use all 15 lines. So forget about having 15 lines of long strings of text. Honestly though, I doubt anyone could find use for all 15 lines.

Quote:

---

Originally Posted by Smashington

Fractional seconds worked in Beta, but they took them out stating that they did not want Macros to give players who used them too great of an edge such that all players would feel pressured to make Macros.

/wait times are now rounded to the nearest whole number.

---

How would that give players that use Macros an advantage. It's in the game for everyone to use . Its not like macros are external tool like parser. There even a guide for it in game.

Thats like saying get rid of crafting classes because it provides a unfair advantage to people who took the time to level them, or lets get rid of chocobos becauase its unfair to those people who didnt take the time to do the quest.


that's a bad excuse . It only takes 5 mins to learn how to use them.

I don't think it would give players of the same job unfair advantages since they are there for everyone to use. However, if say, a Warrior made a two combo macro (BB and SP), he could alt-tab and check the scores of last night's game whereas a MNK or DRG still has to worry about positioning. So in that case, it would be an unfair advantage given to the Warrior. I'm sure that can play out in several different cases. Just seems better to make people have to actually try to play, rather than press a button and watch your character do a bunch of shit in a fight. Can't imagine that would be much fun.

Some of us are old and cant handle all this shit! I macro so I have time, usually I basic combo macro and free buff in between but my oldest macro set ive never changed and it's my buff AT&T with my drg which is like 15 seconds long. While the macro is going though it leaves me to dodge attacks and not have to push those buttons. Slows me overall but makes the harder fights survivable