Having played about with macros to set up my alt and switch out gear sets is very convenient but sometimes I have noticed some issues with macros and have been at a loss to why they are not working.
One of this issues is very specific and having a wait ability may fix it (it may not either). If you have a zig and it holds you other gear sets to swap sets you need to remove the zig from you bag, swap your gear, then put the zig back in the bag. Sometimes you only equip some items or no items get equipped, running the macro a second time seems to complete it.
Another issue I am seeing, is specific to assist tageting using target team #, then target current target's target. In some cases this does not activate fast enough and you cast/attack your current target before the assist happens.
I assume all commands in a macro get executed instantly? which sometimes causes the issues (first issue always happens).
If there was an ability to wait x milliseconds in the macro before it continues then we could stop the afore mentioned issues from happening.
There is a /sleep command but that is 1) in seconds, and 2) freezes the client for x seconds but does not prevent the issues with the macro.
A wait ability that does not freeze the client but allows other tasks to complete during the waiting period would help I think.
Thank you.
Persimmon.
One of this issues is very specific and having a wait ability may fix it (it may not either). If you have a zig and it holds you other gear sets to swap sets you need to remove the zig from you bag, swap your gear, then put the zig back in the bag. Sometimes you only equip some items or no items get equipped, running the macro a second time seems to complete it.
Another issue I am seeing, is specific to assist tageting using target team #, then target current target's target. In some cases this does not activate fast enough and you cast/attack your current target before the assist happens.
I assume all commands in a macro get executed instantly? which sometimes causes the issues (first issue always happens).
If there was an ability to wait x milliseconds in the macro before it continues then we could stop the afore mentioned issues from happening.
There is a /sleep command but that is 1) in seconds, and 2) freezes the client for x seconds but does not prevent the issues with the macro.
A wait ability that does not freeze the client but allows other tasks to complete during the waiting period would help I think.
Thank you.
Persimmon.