Quote Originally Posted by KikoriL View Post
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.