Cure macro question

Hey, I'm playing in the PS4, and I'm using macros for attacks/dots and they work sweet.

With the Cure one I have some strange behavior. I'm using this:

/macroicon "Cure"
/ac Cure <tt>
/ac Cure <t>
/ac Cure <me>

And usually if I'm selecting a mob which it's hitting the tank and I cast Cure, it heals me =S.

My stone macro its the "same" and works:

/macroicon "Stone II"
/ac Stone II <tt>
/ac Stone II <t>

Thank you!

Well based on your macro, everything should be in working order.
What I suggest to "troubleshoot" it, is to remove the <t> and <me> portion of your macro, only keep the /ac Cure <tt> line there, and try to use your macro and see how it behaves.

A teeny tiny suggestion on the cure part, I suggest putting <t> first then <tt>. I'll explain using a scenario. You're in Titan hm, then weight of the land comes in and hits the other healer down to 200 hp so in a panic, you'll click on him and cast cure, instead of healing him you'll heal his target because <tt> is first then <t> is second.

Oh here leme give you another macro
/macroicon "Swiftcast"
/ac "Swiftcast"
/ac "raise" <t>
/ac "raise" <1>
/ac "raise" <2>
/ac "raise" <3>
/ac "raise" <4>
/ac "raise" <5>
/ac "raise" <6>
/ac "raise" <7>
/ac "raise" <8>
/wait 60
/echo <se.1> Swiftcast available

If you'll use that macro dont forget to /psort

Here's what it does, Another situation! So you're focus healing on the tank for titan hm, a new tank that's pretty squishy so you'll have to heal him often. Suddenly Titan does weight of the land and a dps dies! WITHOUT the macro you'll have to switch target to the dps and hopes the tank doesnt while you try to ress the other guy(lets assume the other healer fell down) then switch back to the tank and start healing again. WITH the macro you can just press that macro twice WITHOUT switching target and it will ress the guy without you having to switch target! But if you wanna ress a certain person you can just target the guy since <t> is at top :D REMEMBER to /psort, tank first then healers then dps!

Since we're moving into macro improvement territory:

1) <tt> should never be paired with <t> for heal spells under any circumstances for the reason below:

if you <tt> 1st then only <t>, you can ONLY heal the main tank, if you target the mob, mob's target = the tank, you heal the tank, now as Claire mention above, if you want to heal another person, you have no way to actually select him, this is because you select him , his <tt> is usually a monster, you probably think a monster is an invalid heal target, but actually it's not!! When you try to heal a monster, it will actually count as healing you yourself, so the 1st macro line with <tt>, will still be triggered, the healing target is you.



2) I assume the reasons you're doing all these <tt> and <t> stuff, is so that you can heal + dps with minimal target swapping, am I right? If yes, I propose the following improvement:

As you're a PS4 user, it's not simple to focus a target, but I highly recommend you do so, so you can keep track of monster spell casts in the future as well, what you can do is simply make a macro for focusing a target:
/focustarget <t>
This will allow you to assign your current target to be focused, next step is:

Macro ALL your dps skills to as below:
/ac AttackSkill <t>
/ac AttackSkill <f>

This allows your attack skills to 1st try to attack a targeted unit, which in a healer's case, usually is a friendly unit, so it will be invalid.
Next if you have a monster focused (as you should!! for fights such as twintania), it will attack that monster.

Thus you will be able to heal any friendly party member (usually your <t>), and dps at the same time if you have a monster focused (<f>).

Hope this is helpful!!

Quote:

---

Originally Posted by ClaireAbigail

snip due to stupid char limit

---

a few things.

1.) the /wait 60 will get overridden if you use another macro due to the fact you can only have 1 macro "running" at a time.
2.) a simple single target raise macro with a /p would be better so the other healer can know who you are attempting to raise right away. No sense both of you casting raise on the same person.
3.) there is no reason to do /psort any more since as of 2.2.8 it is auto sorted when you go into a duty.

On side note, I prefer not have my heals on macros, so I can have others macros "wait commands" running without interrupting them. Useful for some pet commands macros or getting that echo message after X seconds.

I use macros constantly, good, bad, or indifferent. I want a little micro-management, so curing and attacking spells are based on the tank or DPS that it revolves. For example, I have a Cure Tank, Cure DPS1 and Cure DPS2 for light parties. I also have Aero, Stone, and Stone II; which are all based on attacking the target of the tank. Since my main job is healing, and I don't need to draw aggro from something that isn't directly in the tank's attention, this works well. So, I have macros that look like this:

/macroicon "Cure"
/psort
/ac "Cure" <2>

Part II...

Since the party will sort self, tank, DPS in a light party, then I use the same thing, but replace the 2 with a 3 for a Cure DPS1 and 2 with a 4 for Cure DPS2. I don't leave myself out. I have a Cure Self.

To that end, since I don't want to worry about what I have targeted at that moment, when I want to attack the tank's target, I have macros that look like this:

/macroicon "Stone"
/psort
/target <2>
/ac "Stone" <tt>

If I made a mistake on line 3, forgive me, I'm typing from memory. This targets the tank and attacks his target. Don't want to lose focus his target in case he switches targets for some reason, and I don't have to wonder if I'm on the right target. No matter what I'm doing, the macro gets me to the right place.

Part III...

I also made a macro (though it's useless in the low level dungeons) to raise the tank quickly. I target the tank, do a SwiftCast, then a raise. You have to put a slight delay (I use /wait 2.5 for a 2.5 second delay). Unfortunately, since the amount of time it takes for the tank to accept the raise and reappear is not exact, you'll want to get him back to health using another macro.

Quote:

---

Originally Posted by EricCartmenez

Part III...

I also made a macro (though it's useless in the low level dungeons) to raise the tank quickly. I target the tank, do a SwiftCast, then a raise. You have to put a slight delay (I use /wait 2.5 for a 2.5 second delay). Unfortunately, since the amount of time it takes for the tank to accept the raise and reappear is not exact, you'll want to get him back to health using another macro.

---

/wait rounds to the nearest whole number so your /wait 2.5 macro will actually take 3 seconds.

Also it defeats the purpose having a /wait with swiftcast just do
/ac "Swiftcast" <me>
/ac "Raise" <t>

and just spam the button.

Quote:

---

Originally Posted by EricCartmenez

Part II...

Since the party will sort self, tank, DPS in a light party, then I use the same thing, but replace the 2 with a 3 for a Cure DPS1 and 2 with a 4 for Cure DPS2. I don't leave myself out. I have a Cure Self.

---

in 8 mans <3> will be the second tank DPS start at 5
Party order with default sort
<1> you
<2> tank
<3> tank
<4> healer
<5> DPS (Second healer if your DPS)
<6> DPS
<7> DPS
<8> DPS

For light parties
<1> You
<2> Tank
<3> DPS (Healer if DPS)
<4> DPS

I'll share my pre battle macro. This is from memory so might be slightly off but it will cast stoneskin on everyone and then protect. Very useful after a wipe in Coil

/ac "Stoneskin" <1> <wait.3>
/ac "Stoneskin" <2> <wait.3>
/ac "Stoneskin" <3> <wait.3>
/ac "Stoneskin" <4> <wait.3>
/ac "Stoneskin" <5> <wait.3>
/ac "Stoneskin" <6> <wait.3>
/ac "Stoneskin" <7> <wait.3>
/ac "Stoneskin" <8> <wait.3>
/ac "Protect" <me>

Quote:

---

Originally Posted by Yonko

a few things.

1.) the /wait 60 will get overridden if you use another macro due to the fact you can only have 1 macro "running" at a time.
2.) a simple single target raise macro with a /p would be better so the other healer can know who you are attempting to raise right away. No sense both of you casting raise on the same person.
3.) there is no reason to do /psort any more since as of 2.2.8 it is auto sorted when you go into a duty.

---

The wait thing works for me since it's the only wait macro I use.
And I stopped with the /p on a macro because it tends to be spammy so I what I do is just tell the other healer I'll raise the first one then he can grab the second dead one or like silence management with bards.
And you still have to /psort if let's say a tank leaves and another one joins the new tank is number 8. To be honest it's just a nice habit to have.

Yonko, your pre-battle macro is identical to mine except I cast protect then stoneskin. It's invaluable, but I can't tell you how many times people rush out of range before I can get stoneskin on them (or maybe it doesn't cross their minds), so I figure I get protect on them immediately as soon as the lasso (or whatever that circle is called) drops away. Yeah, I didn't go into the 8 party macro only because the WHM I have is only LVL 43, so no 8's for me yet. That said, I'm working on it. I need more buttons on my PS4 controller interface. LOL.

Yonko, the statement about /psort being unnecessary is not entirely true, because if your tank drops for any reason (DC, needs to leave, is an A-hole), and you get a replacement, the replacement goes to the bottom of the list. Found that out the hard way. Luckily, I have a bluetooth Apple keyboard connected to the PS4, so I quickly typed /psort and once it's done, it's done. /psort puts things right with the world. Since it's a macro, the time delay on it is milliseconds or microseconds, so no skin off my nose and no detriment to the party.