Need some healer macros

[Drasyra]

OK, not everyone will agree but here's my take on it: don't use macros to heal. Just don't do it. It stops ability queuing which can lead to things simply not going off if there is any kind of latency.

Text echo macros to let your co-healer know you've cast raise etc? Fine. Make them separate to the actual cast though.

[KikoriL]

OK, not everyone will agree but here's my take on it: don't use macros to heal. Just don't do it. It stops ability queuing which can lead to things simply not going off if there is any kind of latency.

Text echo macros to let your co-healer know you've cast raise etc? Fine. Make them separate to the actual cast though.

Are you implying to make two macros for some reason to one does the revive and one voices the revival to the party? I can understand not wanting to macro two actions together, since that's almost always an efficiency lost, but it seems like you're dividing it further than that...

[Menae]

Are you implying to make two macros for some reason to one does the revive and one voices the revival to the party? I can understand not wanting to macro two actions together, since that's almost always an efficiency lost, but it seems like you're dividing it further than that...

Yes, that is what Drasyra is implying. It's clunky as hell, I agree, but he is correct in that any spell in a macro cannot be queued up. If you do so, the game will not accept the input until after your previous spell finishes casting, meaning there's a small delay between when finish your previous spell and when the new one can start. On the other hand, if you just hit the spell shortcut, you can press the button while the previous spell is casting and the game will automatically start casting the new spell as soon as possible. It allows for less delay between spells.

That said, I think a Raise/announce Raise macro is fine, because A) you'll likely be using it after Swiftcast, so you don't have to worry about the queuing problem most of the time, and B) when you aren't, a half a second delay likely won't change much. Just don't macro Swiftcast into the actual Raise macro.

[Sida]

Are you implying to make two macros for some reason to one does the revive and one voices the revival to the party? I can understand not wanting to macro two actions together, since that's almost always an efficiency lost, but it seems like you're dividing it further than that...

I think she's saying that you should use the raise skill as a pure skill, not as a macro. But in addition to that, have macro which announces in chat that you're raising someone. So yes, two button presses in case you do the announcement too. (And three if swiftcast was used) The reason being, you can get action sort of queued up even if you press it a bit before the previous cool down ends, that way making it launch exactly on the earliest possible moment. No such thing with macros, you can only use them after the previous cool down has ended and due reflexes, latency and all other fun stuff, it can cause from hardly noticeable to even serious delays.

[Spoekes]

OK, not everyone will agree but here's my take on it: don't use macros to heal. Just don't do it. It stops ability queuing which can lead to things simply not going off if there is any kind of latency.

Text echo macros to let your co-healer know you've cast raise etc? Fine. Make them separate to the actual cast though.

I like bashing the use of macros too, but a raise+announce is really not a problem.
virus+announce I would not do, virus is oGCD that can be queued perfectly so those are to be separated but raise.. cmon.

[Sida]

I like bashing the use of macros too, but a raise+announce is really not a problem.
virus+announce I would not do, virus is oGCD that can be queued perfrectly so those are to be separated but raise.. cmon.

Was explaining the post that was referred earlier, not saying it is my opinion ^^.

[Spoekes]

yeah sorry I changed the quote now