Commando Archive
Thread: Recursive Macros Going Away
Chabian wrote:
Okay, how in the world could they do this?
The only specific way we definitely know is that Macros won't be able to call themselves like:
/tumbletostand;
/macro tumble;
But there is heavy speculation the other way they'll accomplish this (no for sure verification yet from the devs on this) is that Macros will no longer be able to target the F-Slots...so you would not be able to havemacro activate another macro in the F-Slots...This could mean that it will also prevent macros from clicking on weapons, armor, crafting kits, etc in f-slots...
I for one think they will limit the Macros from just activating other macros in the F-Slots...they will still be able to target non-macros in the f-slots...so you will still be able to put on or off armor...or arm a weapon...or use a series of specials...etc...you just won't be able to activate another macro via a macro...so a Buff Bot or AFK Dancer wouldn't be able to start over...
And there are ways around not being able to start over...They said they are not limiting the use of VERY LONG macros...you can't create an endless loop, but you can create a long running macro...
Chabian wrote:
Okay, how in the world could they do this?
When a user interactively clicks on a tool bar slot, he or she /ui action toolbarSlotXX or /user interfaces with toolbar slot xx...
Wouldn't the code have to be rewritten for a click event on the entire concept of the toolbar.
I already see a way around this recursive macroing
/ui action toolbarSlot01 (In slot 1 is /flamesingle2 Skill);
/pause 8;
/ui action toolbarSlot02 (In slot 2 is /famecone1 Skill);
/pause 8;
/ui action toolbarSlot01;
Would this not be a recursive macro ?????????
Message Edited by garvin on 08-01-2004 08:38 PM