




Happily, timer conflicts are actually a non issue in this case. Only one macro can be running at a time. If a macro is not /mlock-ed, activating any other macro will cancel the remaining lines before starting itself.Yeah, that's part of the problem for how I did this, as you'll probably be able to pick out how I'm using shared 9 and 10 in a 4x3 configuration to have the flyout, along with the macro closing the bar, so with how that's constructed putting a timer on either 9 or 10 could cause problems like if I was switching between a crafter and gatherer, or jumping between different battle classes quickly, I can see hitting a situation where there's a timer on 9 or 10 that expires and closes the window. What I would do for a variable or two with some Shenzhen I/O style assembly.
Last edited by Rongway; 07-29-2021 at 03:11 PM.
|
|
![]() |
![]() |
![]() |
|
|
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

