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.
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.
Last edited by Enfarious; 04-29-2012 at 08:14 PM.
XIV Pad: http://xivpads.com/?Elasandria-Servion-Hyperion
Linkshell: http://sd-is.guildwork.com
Rig: https://www.dropbox.com/sc/jv56yukhpi7413q/gQTzd-DS9y
FX-8150 @4.1GHz; 8Gigs ripjaws @1600; OCZ Vertex 3 128GB SSD; WDC 1TB HDD;
XFX Radeon HD 7970;
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.


Reply With Quote



