/wait n and <wait n>

after a bit of looking I noticed that no one had mentioned the <wait n> placeholder, it was such a wonderful thing when they thought to add it to XI, rather than wasting an entire line on a /wait.

You know you want it, I know I want it.

Give me back my macro lines. :D

I'm not sure I follow. If /wait isn't sufficient, where would you be putting this <wait n> thing?

He would put it in the same line instead of using another line for the wait.

/ac "Sacred Prism" <me>
/wait 1
/ac "Regen" <t>

would become:
/ac "Sacred Prism" <me> <wait 1>
/ac "Regen" <t>

or something like that.

Quote:

---

Originally Posted by Kikosho

He would put it in the same line instead of using another line for the wait.

/ac "Sacred Prism" <me>
/wait 1
/ac "Regen" <t>

would become:
/ac "Sacred Prism" <me> <wait 1>
/ac "Regen" <t>

or something like that.

---

That exactly. While it seems rather pointless in a smallish, 3~6 lines, macro where losing a few lines doesn't mean a whole lot, if your sitting @9 lines and things are stepping on eachother as a result of latency and what have you. that freeish <wait 1>, instead of a line lost to /wait 1, can be the difference between a failed macro that gets spread across 2 to make it work, and a functional single macro.

Ah, I see. I'd rather just see unlimited (or expanded) macro lines, rather than jamming a wait into another command, but I'm ok with your suggestion as well.

Peeeeersonally...
I'd prefer if the macro was validated entirely client-side and then sent for the server to execute it on it's own, rather than continuously sending commands, this way one could make a much bigger macro.
Hell, that'd probably be pretty great because it'd probably let them add stuff like a bigger macro size, an If statement, oh god i'd love that (because I want to make just one macro for 'self-heal' but it'd be different for each class and job)

At this point, I would settle for my macros working when I use them the first time. No reason I should be hitting my macros multiple times just to get them to work properly. Tired of equipment not being equipped or abilities not being used.

Quote:

---

Originally Posted by Raldo

Ah, I see. I'd rather just see unlimited (or expanded) macro lines, rather than jamming a wait into another command, but I'm ok with your suggestion as well.

---

I don't disagree, it was one of the things about ffxi windower(which I would never use of course) that made it useful. But since there's already code in place to handle other placeholders adding another place holder would probably be more convenient at least until 2.0.

Quote:

---

Originally Posted by Skies

Peeeeersonally...
I'd prefer if the macro was validated entirely client-side and then sent for the server to execute it on it's own, rather than continuously sending commands, this way one could make a much bigger macro.
Hell, that'd probably be pretty great because it'd probably let them add stuff like a bigger macro size, an If statement, oh god i'd love that (because I want to make just one macro for 'self-heal' but it'd be different for each class and job)

---

Sadly this will probably never happen, it would make it entirely too easy to add hax to macro's to accomplish things that they won't want happening. By offering up a way to insert binary date into a macro that's seemingly "safe" you could effectively packet spoof through the use of the macro system.

Quote:

---

Originally Posted by Kikosho

At this point, I would settle for my macros working when I use them the first time. No reason I should be hitting my macros multiple times just to get them to work properly. Tired of equipment not being equipped or abilities not being used.

---

This is the reason for a /wait, especially in the case of gear swaps where it causes a frame delay when you blink lines get skipped. With a <wait> after a gear change it would essentially allow you to compensate for that gear/blink delay in the client/server communication chain.

There was information in one of the patch notes that said wait can be done at the end of a line with the / character.

Now I tried this and I can't get it to work, I'll see if I can find the patch notes.

Esit:- Nope can't find it, maybe I imagined it lol

Quote:

---

Originally Posted by Jinko

There was information in one of the patch notes that said wait can be done at the end of a line with the / character.

Now I tried this and I can't get it to work, I'll see if I can find the patch notes.

Esit:- Nope can't find it, maybe I imagined it lol

---

Check the FFXI patch notes you'll find it. Like I said it's something from XI that in the famous words of Rocky the Flying Squirrel, "Now here's something I think everyone can enjoy."

Oh yea I know what you are referring to in 11, I just thought I saw something in the FFXIV patch notes about it.

Of course if macro's were stored server side they would work much faster negating some of the need to wait between lines.

Yes and no, it would possibly save us from the gear delay /waits, but the cast delays so abilities don't step on each other would still have to be present.
In XI they were also stored/executed from the client and like it was said a little earlier except for the possible hax, if they were fully processed on the client side they'd be just as fast/smooth, but even then we'd need /waits for cast delays and things.
If the client didn't stop sending commands randomly during a macro it'd probably be enough, but that's that whole not getting fixed til 2.0 lag/latency thing getting in the way.

Well with the new patch this isn't nearly so much an issue. I've not had a class/job change fail miserably since, all my gear actually changes out, and all my other macros are 6 lines or less, I think ffxi trained me to write short macros.