Tweet
there are a few rules to writing good macros. let's go over them:
RULE 1: YOU DON'T NEED /P IN YOUR MACRO'S! no one in the party needs to see /p hey everyone!!! look at me! i'm casting {cure} !!!11!one! <call> ~~~~ <squigglyline> ~~~ <annoyingsound14> every time you heal the tank. it does no one any good. all it does is distract them from important party chat, like tp flashes for a skillchain. so NO /P IN YOUR MACROS!
you should macro your weoponskills with a /p warning so the mages know when to burst. spammy cures, vokes, jumps, etc distract the players involved in a skillchain. it can cause problems, and is not needed to play the game. so keep party chat out of your macros unless you are involed in a skillchain, please. no one needs to hear another paragraph about angels jumping down from heaven every time you use jump.
sometimes when in parties with multiple healers, you can argue that you can have a /p (cure III) >> <t> on your cures, to prevent wasted mp by having multiple healers try to cure the same person. i'm not talking about these, so long as they are short and discreet, though i don't see how it really helps. in an emergency, by the time they see your party chat message, they've usually already started -or even finished- casting their own cure, and they can see you casting just fine without it anyway.
i met a dragoon (not knocking the job, only the player) once who had a full paragraph (three sentances over two macro lines) of party text on each jump. We almost missed some skillchains over it, and i had to open my menu to see my partner's tp flash.
if you want some party text in your macros, at least keep it short. place something from the translator in it so jp's know what you're trying to say. but don't do it at all when it's unneccessary. i've taken /p out of most of my macros, except my weoponskill ones. no one needs to know when the thief is casting (utsusemi). do they need to see when the ninja is casting it? maybe, but your backup voker can see you trying to cast, and doesn't need his chat log filled up with "/p an ninja is one with the shadows, and a master of stealth! casting (utsusemi: Ichi) please provoke!" every time you cast your spell, because he can see it just fine without it.
RULE 2: RE READ RULE 1
i know it's long, but important >.>
FULL MACRO PALLETS BY JOB
i added in full pallet guides by job. they're found later in the thread, though.
the summoner palet is finished on page 2
the white mage macro is done also on page 2
i just put in the ranger macro pallet, on page 3
the SOLO PALLET is finished! I'm really proud of this one!
page 3
the thief pallet is here, page 3
the samurai pallet is on page 3 now, too
the paladin pallet is finished, page 4
the ninja pallet is done, also page 4
kk i just added the bard pallet guide in. i din't actually write this one though, since i don't even have bard unlocked XD
more pallets to come soon! but for now, let's go over a few things...
~~~THE BASICS:
ok, let's go over how to input a few commands. there are several ways to do different things. to explain, first let's look at a provoke macro. there are two diferent ways to make a provoke macro:
/ja "Provoke" <bt>
/recast "Berserk"
/wait 30
/recast "Provoke"
or...
/ja "Provoke" <t>
/recast "Berserk"
/wait 30
/recast "Provoke"
<bt> means battle target. <bt> targets whatever the party is targetting. it is sometimes faster to type /ja "Provoke" <bt> than to tab through everything on the screen. you will autmatically provoke whatever mob the puller is pulling, (so long as that is the first thing targetted by the pt.) i don't use <bt> anymore, however, because i noticed <bt> has a problem with links sometimes. you can accidentally provoke the wrong mob with <bt>. i took <bt> out of all of my macros. now i target everything manually.
notice also how there is no party chat in this macro! everyone can see that you are provoking, and they can see "Dummy uses provoke on the lizard" they don't need to see it again in party chat. all that does is spam,and distract the people from more important partychat, like skillchain info.
now, if you decide you do want to have /party chat in your macros, make sure it includes something useful, like a tp call. this turns it from annoying spam into something that actually helps the battle. add <tp> in you provoke macro. like this:
/ja "Provoke" <t>
/p (provoke) >>> <t> TP = <tp>
/wait 30
/recast "Provoke"
flashing our tp to your pt members is something you should be doing anyway. always use the translator in party chat macros whenever possible. jp's play ffxi too, remember
next, let's discuss /recast. /recast tells you how much longer you have until you can recast that ability (i.e, how much time is left on the recast timer.)
different jobs have different needs. when i tanked as a ninja, i used this provoke macro instead.
/ja "Provoke" <t>
/wait 6
/ja "Berserk" <me>
/wait 24
/recast "Provoke"
this is because ninjas can use berserk when tanking. this way, i didnt have to remember to use berserk. every time i provoked, if berserk was ready, it would just berserk for me if it was up, so i didnt have to think about it
.
~~~~~sneak attack: a lot of jobs use sneak attack, and not just thieves^^
here is how a lot of players write their sata macros:
/ja "Sneak Attack" <me>
/wait 2
/ja "Trick Attack" <me>
/wait 2
/ws "Viper Bite" <t>
but here is another way, because it leaves more room on the pallet for equipment-swapping and other things:
/ja "Sneak Attack" <me>
/ja "Trick Attack" <st>
/ws "Viper Bite" <stnpc>
<st> targets yourself and waits until you choose to hit the enter/confirm button for it to go. this way, you don't have lag interfere with the trick attack (which does happen sometimes)
some players prefer to break this up, by seperating sneak attack, trick attack, and the weoponskill into seperate pallets right next to each other. this is another way to prevent lag from causing your sata to not activate properly. i don't use this way because all ten of my macro pallet sets are filled to capacity already, and i simply don't have room.
~~~~~RANGED ATTACKS AND PULLING:
now let's look at some pulling macros. we'll start with the ranged attack macro for pulling the mob to camp:
/equip ammo "Whatever arrows you are using now"
/ra <t>
/p (ranged attack) >>>> <t>
/recast "Sharpshot"
/echo <tp>
/equip ammo reloads your ammo slot if you happen to be out of arrows. that way, you don't have to worry about it. in place of /recast "Sharpshot", use whatever job ability is most imprtant to your current job. berserk is a common one.
if you plan to use ranged attacks during the fight (when you aren't actually pulling a mob), you will need a second macro for that:
/equip ammo "Acid Bolts"
/ra <t>
/recast "Berserk"
the /echo command puts something on the screen only you can see. if you typed /echo hey dummy! then "hey dummy!" would appear on your screen, and only you could see it. /echo <tp> shows you how much tp you have when you aren't enguaged with the mob, without having to open any menus. i put it on my pulling macro, just so i can still see my tp between fights.
and as i said before, each job is a little different. for example, here's a possible pulling macro for samurai:
/equip ammo "Wooden Arrows" <--or whatever arrows you happen to be using
/p {Ranged attack} >>> <t>
/ja "Third Eye" <me>
/wait 2
/ra <t>
/recast "Meditate"
it's also a good idea to have a heads up macro when pulling. just a:
/p <t> (found it!) <Pos> <call14>
i like call 14 for this because it's one of the less annoying-sounding calls. i use this macro if im not sure if i should pull the mob. i hit this macro and wait to see if someone says "NOO!!! DON'T PULL THAT OR WE'RE ALL GONNA DIE!!!" lol...
RULE 1: YOU DON'T NEED /P IN YOUR MACRO'S! no one in the party needs to see /p hey everyone!!! look at me! i'm casting {cure} !!!11!one! <call> ~~~~ <squigglyline> ~~~ <annoyingsound14> every time you heal the tank. it does no one any good. all it does is distract them from important party chat, like tp flashes for a skillchain. so NO /P IN YOUR MACROS!
you should macro your weoponskills with a /p warning so the mages know when to burst. spammy cures, vokes, jumps, etc distract the players involved in a skillchain. it can cause problems, and is not needed to play the game. so keep party chat out of your macros unless you are involed in a skillchain, please. no one needs to hear another paragraph about angels jumping down from heaven every time you use jump.
sometimes when in parties with multiple healers, you can argue that you can have a /p (cure III) >> <t> on your cures, to prevent wasted mp by having multiple healers try to cure the same person. i'm not talking about these, so long as they are short and discreet, though i don't see how it really helps. in an emergency, by the time they see your party chat message, they've usually already started -or even finished- casting their own cure, and they can see you casting just fine without it anyway.
i met a dragoon (not knocking the job, only the player) once who had a full paragraph (three sentances over two macro lines) of party text on each jump. We almost missed some skillchains over it, and i had to open my menu to see my partner's tp flash.
if you want some party text in your macros, at least keep it short. place something from the translator in it so jp's know what you're trying to say. but don't do it at all when it's unneccessary. i've taken /p out of most of my macros, except my weoponskill ones. no one needs to know when the thief is casting (utsusemi). do they need to see when the ninja is casting it? maybe, but your backup voker can see you trying to cast, and doesn't need his chat log filled up with "/p an ninja is one with the shadows, and a master of stealth! casting (utsusemi: Ichi) please provoke!" every time you cast your spell, because he can see it just fine without it.
RULE 2: RE READ RULE 1
i know it's long, but important >.>
FULL MACRO PALLETS BY JOB
i added in full pallet guides by job. they're found later in the thread, though.
the summoner palet is finished on page 2
the white mage macro is done also on page 2
i just put in the ranger macro pallet, on page 3
the SOLO PALLET is finished! I'm really proud of this one!
page 3the thief pallet is here, page 3
the samurai pallet is on page 3 now, too
the paladin pallet is finished, page 4
the ninja pallet is done, also page 4
kk i just added the bard pallet guide in. i din't actually write this one though, since i don't even have bard unlocked XD
more pallets to come soon! but for now, let's go over a few things...
~~~THE BASICS:
ok, let's go over how to input a few commands. there are several ways to do different things. to explain, first let's look at a provoke macro. there are two diferent ways to make a provoke macro:
/ja "Provoke" <bt>
/recast "Berserk"
/wait 30
/recast "Provoke"
or...
/ja "Provoke" <t>
/recast "Berserk"
/wait 30
/recast "Provoke"
<bt> means battle target. <bt> targets whatever the party is targetting. it is sometimes faster to type /ja "Provoke" <bt> than to tab through everything on the screen. you will autmatically provoke whatever mob the puller is pulling, (so long as that is the first thing targetted by the pt.) i don't use <bt> anymore, however, because i noticed <bt> has a problem with links sometimes. you can accidentally provoke the wrong mob with <bt>. i took <bt> out of all of my macros. now i target everything manually.
notice also how there is no party chat in this macro! everyone can see that you are provoking, and they can see "Dummy uses provoke on the lizard" they don't need to see it again in party chat. all that does is spam,and distract the people from more important partychat, like skillchain info.
now, if you decide you do want to have /party chat in your macros, make sure it includes something useful, like a tp call. this turns it from annoying spam into something that actually helps the battle. add <tp> in you provoke macro. like this:
/ja "Provoke" <t>
/p (provoke) >>> <t> TP = <tp>
/wait 30
/recast "Provoke"
flashing our tp to your pt members is something you should be doing anyway. always use the translator in party chat macros whenever possible. jp's play ffxi too, remember
next, let's discuss /recast. /recast tells you how much longer you have until you can recast that ability (i.e, how much time is left on the recast timer.)
different jobs have different needs. when i tanked as a ninja, i used this provoke macro instead.
/ja "Provoke" <t>
/wait 6
/ja "Berserk" <me>
/wait 24
/recast "Provoke"
this is because ninjas can use berserk when tanking. this way, i didnt have to remember to use berserk. every time i provoked, if berserk was ready, it would just berserk for me if it was up, so i didnt have to think about it
.~~~~~sneak attack: a lot of jobs use sneak attack, and not just thieves^^
here is how a lot of players write their sata macros:
/ja "Sneak Attack" <me>
/wait 2
/ja "Trick Attack" <me>
/wait 2
/ws "Viper Bite" <t>
but here is another way, because it leaves more room on the pallet for equipment-swapping and other things:
/ja "Sneak Attack" <me>
/ja "Trick Attack" <st>
/ws "Viper Bite" <stnpc>
<st> targets yourself and waits until you choose to hit the enter/confirm button for it to go. this way, you don't have lag interfere with the trick attack (which does happen sometimes)
some players prefer to break this up, by seperating sneak attack, trick attack, and the weoponskill into seperate pallets right next to each other. this is another way to prevent lag from causing your sata to not activate properly. i don't use this way because all ten of my macro pallet sets are filled to capacity already, and i simply don't have room.
~~~~~RANGED ATTACKS AND PULLING:
now let's look at some pulling macros. we'll start with the ranged attack macro for pulling the mob to camp:
/equip ammo "Whatever arrows you are using now"
/ra <t>
/p (ranged attack) >>>> <t>
/recast "Sharpshot"
/echo <tp>
/equip ammo reloads your ammo slot if you happen to be out of arrows. that way, you don't have to worry about it. in place of /recast "Sharpshot", use whatever job ability is most imprtant to your current job. berserk is a common one.
if you plan to use ranged attacks during the fight (when you aren't actually pulling a mob), you will need a second macro for that:
/equip ammo "Acid Bolts"
/ra <t>
/recast "Berserk"
the /echo command puts something on the screen only you can see. if you typed /echo hey dummy! then "hey dummy!" would appear on your screen, and only you could see it. /echo <tp> shows you how much tp you have when you aren't enguaged with the mob, without having to open any menus. i put it on my pulling macro, just so i can still see my tp between fights.
and as i said before, each job is a little different. for example, here's a possible pulling macro for samurai:
/equip ammo "Wooden Arrows" <--or whatever arrows you happen to be using
/p {Ranged attack} >>> <t>
/ja "Third Eye" <me>
/wait 2
/ra <t>
/recast "Meditate"
it's also a good idea to have a heads up macro when pulling. just a:
/p <t> (found it!) <Pos> <call14>
i like call 14 for this because it's one of the less annoying-sounding calls. i use this macro if im not sure if i should pull the mob. i hit this macro and wait to see if someone says "NOO!!! DON'T PULL THAT OR WE'RE ALL GONNA DIE!!!" lol...
) so don't macro your 2 hour
. 
Comment