Ah, that makes sense. Cant wait to have that kind of gear lol.
BTW, Im seeing some macros using a whole line for /wait 3. If you type <wait.3> instead at the end of each line you can do more steps per macro.
/ac "Basic Touch" <me> <wait.3>
You're correct, you can reduce the number of macros you need sometimes by doing this.
This is how my macros are set up so I only require two macros total when crafting multiples of HQ Spicy Tomato Relish.
Crafting HQ Spicy Tomato Relish is possibly one of the easiest ways to get Artisan's Specs for the inglorious grind that is Goldsmith desynthing, and that is pretty much why I use Macros to craft.
I dare anyone to craft at least 80 single HQ Spicy Tomato Relish' manually at a time and stay completely sane and content through the process. Unless you're a glutton for this kind of manual labor...
I've always used +1 second for my waits because of this. If lag is being unusually bad, I even have +2 second varieties.
It would take longer, but if the issue IS Server lag, just increase your weights from 3's to 4's or 5's. This would ensure that the previous action would have executed and completed before the next command gets sent.
Somebody else posted that most of these style of errors are not server lag, but routing/latency issues. Those of us who are completing endgame battle-oriented combat often have to resort to various methods to tunnel/vpn directly to a datacenter, or else the so called "Server lag" kills us via Landslide. Once you understand it's not the server, or the client that is the actual problem, the problems go away.
Fortunately, I live near Toronto/Montreal, and I experience a minimal amount of latency issues. my old laptop and PS3 have low performance, so I don't perform any tasks that depend on fast reaction time. my Desktop and my PS4 on the other hand work flawlessly. Also, I have similar macro's to the one you posted, and have not had any issues.
I have macros and have used them for bulk HQ crafting. I don't use them for any crafting that I need to use food for because using macros is much less efficient. I can HQ 33 spicy tomato relish in a 30 min food duration if I do it manually but probably less than 20 if using macros.
BTW, I don't really need to use food for the relish if I use HQ tomatoes. Using food allows me to use NQ tomatoes (get about 85% HQ yield vs 100% with HQ mats).
I'd love to see a macro system that uses a ready command instead of wait - ie, fire off the next command as soon as possible (receipt of server side ack) rather than waiting for a blind amount of time that can be screwed over by server lag.
What food do you use for NQ Tomato's on Relish? Because I have about 3 times as many NQ's as I do HQ's from gathering them myself and I'd hate to have to chunk them for nothing.
People have asked for more macro functionality in the past but Yoshida has repeatedly stated that he doesn't want macros replace player... play. Maybe if the developers didn't keep giving reasons to use macros (I have to make how many spruce planks to get my artisan glasses?)...
Well given that the servers are based in Canada; I can see the point of this. What Tunnel or VPN would you recommend for someone living in South Texas near the Gulf Coast?Somebody else posted that most of these style of errors are not server lag, but routing/latency issues. Those of us who are completing endgame battle-oriented combat often have to resort to various methods to tunnel/vpn directly to a datacenter, or else the so called "Server lag" kills us via Landslide. Once you understand it's not the server, or the client that is the actual problem, the problems go away.
|
![]() |
![]() |
![]() |
|
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.