^title.
Most of my crafting macros have
/ac "precise touch"
/ac "basic touch" <wait.3>
in them. I KNOW that you can't execute it at the time, that's the whole point of it ._.
^title.
Most of my crafting macros have
/ac "precise touch"
/ac "basic touch" <wait.3>
in them. I KNOW that you can't execute it at the time, that's the whole point of it ._.
The only problem is if you inadvertently run a crafting macro before starting the craft by mistake. You could end up with a situation where it was still running invisibly in the background & you try to start a craft when it's at, say Byregot's, resulting in a ruined craft. You wouldn't have a way of telling as some actions may have still to occur but be delayed by a <wait.x> command.
I do sympathise though, it's a real pain. Even being able to adjust the sound, location & size for that particular alert separately would help. You could make it small, silent & in a corner without running into the problem I outlined above.
That's a different error message tho. If you have a crafting macro running while you're not crafting it says "Only available while crafting".
I like your suggestion, that may be better than completely removing it. What bothers me the most is the sound anyway. While I'm doing hundreds (literally) of HQ synths with my macro I like to watch movies. I either have to pay attention to the screen or put up with the annoying noise of that error message.
|
![]() |
![]() |
![]() |
|
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.