Musician Archive

---

SeismicEdge wrote:

I am seeing other musicians complaining about afk ers and I can't totally disagree. But when I want to buff someone, I have a recursive macro that keeps me flourishing for the full time and it does include loops. Now I understand they are going to get rid of the recursive macro commands just so the afk ers go away. Does this mean I have to type in all my commands or push buttons continually to buff someone? I don't see that as fun at all.

Can you write a single macro that allows you to complete a buff from beginning to end with no recursive command?

If so, would someone please share that with me?

---

If that's what it takes to get rid of the AFK macrotainers and the buffbots, I'll "suffer" through just about anything, yes, that includes the removal of recursive macros.

I know macros can be pretty long, so chances are you'll be able to take your buffing macro and put it all into one or two other macros & save yourself a little clicking--this is something I'll figure out once the macro fix goes in. Really we don't know how (or how soon) the Devs are going to change the recursive macros. The chances are good we won't have to worry about our current recursive macros if we're using them ATK.

There will still be macros. You'll just have a start it up again when it finishes. I, personnally, have all the flourishes in my toolbar, and it's not much trouble. But as for buffing, just write a long buffing macro. Macros can get to be pretty long, and you could write one quickly with copy and paste.

---

Gorai wrote:

quick question... does alias works with macro??? that would be neat.

---

Well, an alias can call a macro (via the /macro command), although right now I can't imagine why you'd want to do that. But I have found out that an alias cannot call itself - there is already a check for recursion in place for aliases (you actually get an error message mentioning something like "recursion guard hit" - it's been a while since I've seen it, so it's probably not quite like that, but that's the general tone). So one should hope that the same could be implemented for macroes relatively easily.

If you want to get an alias to loop, you need an ingame macro to help you with that. So you call your alias from within the ingame macro, and loop that instead.

---

Echinacea wrote:

Thing is...they can remove the /macro command all they want, but until /ui action toolbarSlotXX is gone, there's no way AFKing will ever end.

/sigh

---

eh, the best thing they can do (and probably the easiest in my opinion from a software standpoint) is to just have the client trace through all of the macro/alias calls every time you execute a macro. If it calls itself at any point during the trace the macro or alias fails to start. Combine that with a maximum amount of time any macro/alias/command chain can run and you're set.

Aliases are easy to create and you can also bust up macros. I often write small macros that are portions of a song. Most songs have a theme and bridge that repeats. I will write these seperately and then have a macro that calls them with some soloes or variations inbetween the bridge and theme. So a buff macro doesn't have to be huge. Simply write a macro that buffs for say 30 seconds then another macro that calls this first macro, pauses 30 seconds, and repeats those two for a total of 6 times. No two macros will be over 10 or so lines. You can get much larger with an alias.

Also you can make your buff macro sound decent by actually writting a couple of different flourish sets and alter calling these in your main buff macro.

For instance if you have a macro of 30 seconds of flourish you can simply write another macro that calls it as follows:

/macro macro1; /pause 30;
/macro macro1; /pause 30;
/macro macro1; /pause 30;
/macro macro1; /pause 30;
/macro macro1; /puase 30;

etc.