It shouldn't proceed with the wait 11 if the cast comes back as an error, they changed macro behavior a while back. What I use is one button, hit it for mooch/cast then again for hook:
/micon Cast
/ac Hook <me>
/ac Mooch <me>
/ac Cast <me>


It shouldn't proceed with the wait 11 if the cast comes back as an error, they changed macro behavior a while back. What I use is one button, hit it for mooch/cast then again for hook:
/micon Cast
/ac Hook <me>
/ac Mooch <me>
/ac Cast <me>
well, the whole idea of fishing macro is to hit one button once, once in a while
and preferably send keystrokes into inactive window (gamepad)
im using something like this:
(the fastest fishes i saw are 9 sec, the longest ones are 15 sec)
Code:/micon hook /ac hook <wait.9> /ac mooch /ac cast <wait.2> /ac mooch /ac cast <wait.2> /ac mooch /ac cast <wait.2> /ac mooch /ac cast


ok looked up what I was thinking of, patch 2.28, I remembered it differently:
That macro should workOriginally Posted by http://na.finalfantasyxiv.com/lodestone/topics/detail/450816f57ade2015876e7675c3d06dca30386770
The <wait.x> command will no longer be executed when used on a line that incurs a text command error.
When used with an action that incurs an error such as "Invalid target" or "Target is not in range," however, the command will still be executed.
|
|
![]() |
![]() |
![]() |
|
|
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



