Printable View
It will still cast Verraise even if Swiftcast is on cool down. In fact, I know tanks that use this fact to place all their defensive buffs in one macro to rotate their abilities that’s not on cool down. The issue might have to do with latency for some.Quote:
Originally Posted by CelestialWyrm
I actually had another quick question: When setting up the multi-line target code, is there a certain way to have the party message specify who's getting rezzed, or is it better to just make a generic message with no character name?
Ex: Verraise ends up cycling through the priority to party member 4 since no one was specifically targeted. The macro is set as "/p (message start) <t> (message end)". In this situation, it probably won't print a name in the message, correct? Basically I just want to know if there's a sort of wildcard character to display the rezzed character regardless of where they are in the priority list.
As for Swiftcast, I've already decided to leave it out of the macro altogether. At first I was curious if there was a practical way of adding it in for convenience, but the consensus seems to be that it's more trouble than help. Which I suspected, but I figured it wouldn't hurt to ask lol.
If you're doing multiple targets, there's no reliable way to print the recipient, which can lead to overlapping raises if multiple people are down and the other raiser can't read your mind, especially when everyone agrees about the priorities. You can work around it by letting the other person cast first, then using a manual target; or agreeing beforehand who casts first.
For reference, there's a <lt> or <lasttarget> tag that will print the name of the last thing you untargeted (by deselecting or by targeting something else). Sadfacedly, it won't print the name of the last target you performed an action on, unless you also hard targeted that person, which would defeat the convenience of a RaiseAnyoneWithoutChangingTarget macro.
Rezz macros don't do anything beneficial most of the times.
Usually both healers use their Swiftcasts+rezz at the same time anyway.
You notice that quite easy if both use such macros, lol.
Before casting a rezz people should look if the person has a rezz-buff. That simple.
That isn't harder than scanning the chat for whatever caused that annoying <se.8>. ;)
For hard rezzes on healers I got a text macro I can press, I mean, we have about 5+s casting anyway.
And how do you want to monitor the chat for names if rezzing is an 'asap' thing? A healer might be busy, too.Quote:
The thing is if a situation has deteriorated to the point where I'm going to need to do any resurrecting I'm probably going to need to act as fast as possible, especially given that I'm probably saving a healer. With Dualcast, that's still at least a two second delay for me to Vercure someone before Dualcast gets its proc. With Swiftcast, I can immediately rez and then heal or rez someone else as needed. At least that's my figuring.
When someone dies, select him while you cast, hit rezz if no buff yet applied, select enemy and continue attacking.
And don't wait for healers, SC might be on CD.
That also prevents things like hitting the macro, then realizing you don't have the MP for a rezz. Do you have a macro to retract your statement, too?
I'm not a rdm, so this might be useless to you. but my favorite "oh shit" raise macro is
/macroicon "Raise"
/ac "Resurrection" <t>
/ac "Resurrection" <2>
/ac "Resurrection" <3>
/ac "Resurrection" <4>
/ac "Resurrection" <5>
/ac "Resurrection" <6>
/ac "Resurrection" <7>
/ac "Resurrection" <8>
/p I've got your Res
or
/p Raise
I have another macro that's literally just /p You Heal, I'll Raise <se.7>
and I have a single target res macro that's funnier and for when I need to specify exactly who I'm raising. But the above is when things are dire and people are dropping like flies. It has saved many a party.