White Mage Macro guide
Everyone In a party are expected to always give it their all and be as efficent as possible, both for your own sake and for the party. With efficent macros, you can both do your job more reliably, and people will see how good you really are. No, honestly.
As a White Mage you are expected to always keep up with cures, buffs and debuffs. You need to cure that status ailment the goblin just cast on you within seconds or the party may be in big trouble. So many things could go wrong if the tank is paralyzed or petrified.
Before you decide how to make your own macros, make sure you follow the following guideline:
- Find the targetting style that matches your way of playing
- Try to use the spells or abilities you need the most, then add “extras” afterwards
- Do not under ANY circumstance use /sh, /s or /em unless it’s of general interest to the people around you
-
A few words about the use of /p
- Use /p only when neccesary
- Make simple /p if you are going to use them, make sure they are auto-translated
-
About the <call>s
- Use <call??> unless it’s a warning that people should be aware of
- Do not use <call> through <call05> for anything but warnings!
- Make sure pulling macros always include a <call??>
- Do not put the <call??> in a macro commonly used (like Cure macros)
The CTRL set
Bar~spell (CTRL-1)
/echo ** Buffing
/ma “Barfira” <me>
Protectra (CTRL-2)
/p ‹ ‹!› › {Protectra} @ 3 byou
/wait 3
/ma “Protectra IV” <me>
Shellra (CTRL-3)
/ma “Shellra IV” <me>
Regen (CTRL-4)
/echo ** Regen ›<t>‹
/ma “Regen III” <t>
Haste (CTRL-5)
/echo ** Haste ›<t>‹
/ma “Haste” <t>
Erase (CTRL-6)
/echo ** Erase ›<t>‹
/ma “Erase” <t>
Poisona (CTRL-7)
/echo ** Poisona ›<t>‹
/ma “Poisona” <t>
Silena (CTRL-8)
/echo ** Silena ›<t>‹
/ma “Silena” <t>
Paralyna (CTRL-9)
/echo ** Paralyna ›<t>‹
/ma “Paralyna” <t>
Stona (CTRL-0)
/echo ** Stona ›<t>‹
/ma “Stona” <t>
The ALT set
Target (ALT-1)
/echo ** Target ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
/target <bt>
Cure II (ALT-2)
/ma “Cure II” <t>
Cure III (ALT-3)
/ma “Cure III” <t>
Divine Seal (ALT-4)
/echo ** Divine Seal
/ja “Divine Seal” <me>
Cure V (ALT-5)
/ma “Cure V” <t>
Raise III (ALT-6)
/s ‹ ‹!› › Raise III ›<t>‹
/ma “Raise III” <t>
MP Status (ALT-7)
/p ›{White Mage}‹ MP: <mp> ›<mpp>‹
Active (ALT-8)
/echo ** Mode: Active
/equip main “Light Staff”
/wait 1
/equip body “Healer’s Briault”
/heal
/echo ** Completed
Rest (ALT-9)
/echo ** Mode: Resting
/equip main “Dark Staff”
/wait 1
/equip body “Errant Houppelande”
/heal
/echo ** Completed
Huggie (ALT-0)
/em wraps <t> in a huggle.
/welcome motion
As you may have noticed, I’m using /echo instead of /p on most macros.. in fact, I have only one /p ^^; I know a lot of people love using /p in their macros, but I hate seeing them being used unnecessarily, so I use /echo so that only I can see the text.
On other jobs I use ALT-8 as a Panic-button (read: Two Hour ability). On a WHM it would have looked like this:
/p ‹ ‹!› › WARNING: {Benediction!} ‹Confirm?› <call>
/ja “Benediction” <stpc>
Notice the <stpc> in there? That’s to ensure I don’t pull out the macro by error, so I need to confirm the selection by hitting ENTER. That’s also why I have the ‹Confirm?t>› text in my macro so that people will know that I’m about to use a two hour ability.
I don’t use Benediction very often, so I usually CTRL-J and pick it manually when needed. Also, you might have noticed that spells like Curaga, Reraise III and so on aren’t added. Neither are Cursna, Dia, Paralyze and Slow. I prefer writing them out by hand when needed. It doesn’t take long to write:
/ma Curaga <t>
no matter how busy things are. ^^; I will however change the status ailment treatment macros to match the monsters I’m fighting. The same goes for the Bar~spell macro.
I prefer using F1-F6 to target my party members instead of having one macro for each party member. Some people like using <stpc> to target their party members, but I prefer using <t> in my macros since it’s more efficent in my opinion. Use <stpc> if you are a Paladin or a melee mage. Having one cure macro for each party member is a waste of macro space and comes at the cost of the other macros that you might really need. There are times when you could make a macro with hardcoded targets (for alliances with tanks) though.