Aero III and II macro

Quote:

---

Originally Posted by Comfort

I will admit I use something similar to this as BRD because it makes mages ballad easier.

But I still think an aero macro like the one requested is probably still not a good as there is not as much gain as with this BRD macro.

However as someone with small hands i appreciate minimal keybinds. 5.0 surely helps with this in a way and also makes the macro uneccessary ^^

---

Yea I am expecting to revise/remove some macros once we get patched. Lots of changes coming :)

RIP aero 3 animation in ShB :( one of my favs... dia using same old and glare is same as stone IV... no new cast animations unlike previous expansions.

Hi, i'm a gamepad user so i enjoy to keep my targets on my team. Just dont forget to enable focus on the target's target to keep track of their casts.

Code:

---

/macroicon "Aero"
/macroerror off
/ac "Aero III" <tt>
/ac "Aero III"
/wait 2.5
/ac "Aero II" <tt>
/ac "Aero" <tt>
/ac "Aero II"
/ac "Aero"

---

The macro you requested on target's target or target if you dont have a target's target
nb : it may not work if you're too low lvl to cast Aero III (need some tests)

Code:

---

/macroicon "Aero"
/macroerror off
/ac "Aero II" <tt>
/ac "Aero" <tt>
/ac "Aero II"
/ac "Aero"

---

Cast Aero or aero II on target's target. If there's no target's target it cast the spell on your target.

Code:

---

/macroicon "Stone"
/ac "Stone IV" <tt>
/ac "Stone III" <tt>
/ac "Stone II" <tt>
/ac "Stone" <tt>
/ac "Stone IV"
/ac "Stone III"
/ac "Stone II"
/ac "Stone"

---

Cast the strongest stone available on target's target. If there's no target's target it casts the spell on your target.

Code:

---

/macroicon "Aero III"
/macroerror off
/ac "Aero III" <tt>
/ac "Aero III"

---

Cast Aero III on target's target. If there's no target's target it cast the spell on your target.

Code:

---

/macroicon "Asylum"
/ac "Asylum" <t>

---

Cast Asylum on your target.

NB: The macro are for 4.0 , they may change with the 5.0 release.

Haven't toyed a ton with macros for combat (other than the typical "announce what I'm doing" macros so my co-healer is aware I'm ressing player that decided jumping off the cliff was a good idea)...but is it necessary anymore to have the macro differentiate between Aero/Aero2 and Stone/Stone2/Stone3/Stone4? I ask because if you put all the abilities on your bar (or had them all on your bar from a setup before the Stormblood changes hit)...it automatically upgrades...i.e. Aero automatically becomes Aero2 when available...wouldn't that work with macros as well?

Quote:

---

Originally Posted by galbsadi

Haven't toyed a ton with macros for combat (other than the typical "announce what I'm doing" macros so my co-healer is aware I'm ressing player that decided jumping off the cliff was a good idea)...but is it necessary anymore to have the macro differentiate between Aero/Aero2 and Stone/Stone2/Stone3/Stone4? I ask because if you put all the abilities on your bar (or had them all on your bar from a setup before the Stormblood changes hit)...it automatically upgrades...i.e. Aero automatically becomes Aero2 when available...wouldn't that work with macros as well?

---

Not that I can recall. The macro should automatically use the appropriate rank of spell if it's a spell that upgrades.

Quote:

---

Originally Posted by galbsadi

wouldn't that work with macros as well?

---

Yes.

Macro's will use the appropriate level spell even if you just plop the basic name of the first rank spell in there.

This also works for conditional upgrades, such as I currently use a macro on MCH and don't distinguish between Split Shot/Slug Shot/Clean Shot and Heated Split Shot/Heated Slug Shot/Heated Clean Shot. The macro simply uses whatever is the currently available one when using just the base name.

Should mean that for ShB a Macro that uses /ac "Aero" should also cast Dia when you unlock it.

Quote:

---

Originally Posted by Yanyami

Code:

---

/wait 2.5

---

---

I'd just like to reiterate because we still keep seeing these here and even in advice given in game.

Waits can only be integer seconds. If you try to wait 2.5, it will implicitly call for a wait 3. If you try to wait 2.4, it will call a wait 2. This is true whether you use /wait x.y or <wait.x.y>. It will always round to the nearest whole second. This is the biggest immediate loss in macros, as waiting for 3s when your GCD is 2.44s means you perform actions at 81% speed; and waiting for 2s means your second action just won't fire. Worse, if there's a three step combo macro, waiting for 2s means you'll do the first action, then do nothing for four seconds, then skip to the third action without the combo bonus.