^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 ._.
-
03-07-2016, 04:41 AMAlsarPlease give us an option to disable the "Cannot execute at this time"
-
03-07-2016, 07:47 AMCulfinrandir
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. -
03-07-2016, 08:27 AMAlsar
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. -
03-07-2016, 05:42 PMYasminou
Isn't that why /macroerror off exists? Put this at the start of your macro and you should be fine.
-
03-07-2016, 06:39 PMGenaxxMacro error only works for specific actions and not "Cannot execute at this time" or "Can only use when crafting".Quote:
Originally Posted by Yasminou