Macro Menu Bars

[Almagnus1]

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.

While I can definitely understand the anti-bot thing, as long as there's no way for the macro system to move the character, nor any way to interact directly with the targeting system, that would prevent the macros from being used with the creation of a bot.

[Rongway]

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.

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.