Indeed, and then test the post itself for a point before you hit submit.
Oh boy! Oh boy! A macro that supposedly implements a new command that's already handled far better in other plugins and macros, yet seems more focused on doing "class specific abilities". To bad not even any of these are right.
Feature's:
-Stick to mob obviously
Macro in front of GMs obviously
Random delays in macros are fun and efficient.
Code: Select all
/if (${Param0.Equal[taunt]}) /echo Taunting when within range.
/if (${Param1.Equal[slam]}) /echo Slaming when within range.
Suppose I want to slam, but not taunt? I guess I would do...
/macro stick "OMG DON'T TAUNT!" slam
to make it work with your syntax. At least look at some other people's WORKING macros to see how these things are handled, since it's rather apparent that you don't understand it yourself.
Your "main loop" then goes on to a crazy chain of goto loops intermingled with a couple return statements that the code can never reach. Ironically the only thing not redundant (unless turning attack on over and over again somehow helps you..) done in these loops is a while statement.
I don't mind helping people when they ask for it, but seriously..please refrain from posting a *NEW* macro that doesn't do anything save serve as an example of how to wait 5 seconds before accepting a group invite (or more likely, inviting a mob to your group, but that can be fun too.)