mrdsp 
The problem with your ress macro, if I'm not mistaken, is using a castsequence. A castsequence will never "skip" casting a spell in the sequence, so it'll just get stuck trying to ress your Party1, even if it is not dead. However, what we can do is use conditionals to make a simple /cast macro that will only try to ress dead characters. Something along the lines of:
This is hardcoded with exact names, but I assume Party1-5 would work fine as well. Atleast with a quick test I did, the macro skipped over the first two toons since they were alive and automatically ressed the third (which I dropped from a mount).Code:/cast [@wubsíe,dead] Raise Ally; [@wubsìe,dead] Raise Ally; [@wubsie,dead] Raise Ally;
As far as the healer... It's down to preference really as there are a multitude of ways you could choose to set it up. Naturally the most efficient would be to control each ability of the Paladin manually, IF you can do that while handling everything on the DKs as well.
Personally I use a combination of multiple different methods and am quite happy with how it's working. My healers respond to the same keys that do my different DPS rotations (AOE, single target, applying dots, etc), but they all trigger the same "basic" healing rotation. Then I use virtualization actions to change that rotation to a different one, such as AOE Spam, TargetOfTarget, Slow PVE Healing, Fistweaving... All of the rotations are built using a combination macros, all of which have conditional [@focus,exist] line at the start, so that if I set a focus target on them, they heal that target rather than whatever they were previously doing. Setting focus is simply done with a repeater region (essentially an area of your screen where mouse clicks/movements are sent over to the specified target) over my raid/party frame and a click. Dropping focus I have keybound, same as larger healing cooldowns. If any of that was unclear, I (badly) demonstrated the basics of my setup here.
Connect With Us