Originally Posted by Arawethion
Hmm, that's a very good point. I've been annoyed by the inability to SM anyone besides the person I Rejuv'd last cycle (actually, with my haste, I might be able to do it with perfect timing). Funny I didn't think of it when I posted that.
A few things though. First, if you're wearing enough to haste to consistently be cycling in less than 12 seconds, it means that anytime you're not Swiftmending, you need to hitch slightly every cycle to avoid clipping the previous Rejuv. This might be a pain.
More importantly, the gain is actually pretty minor--all these means is that when you Swiftmend a tank, you're consuming a Rejuv that's ticked 3 times, rather than one that's ticked twice. The bump to total Rejuv uptime will be very small.
The other benefit (added SM option each cycle) seems mostly illusory as well. When I'm locked into a cycle like at M'uru, the odds are pretty small that I ever get to truly use Swiftmend to "respond to a spike"--most spikes happen while I'm refreshing a Lifebloom. I use Swiftmend much more often as calculated way to add a little HPS to one tank (usually the Spawn tank if he starts drifting downwards even with hots up).
|
It is indeed a pain - having to watch gcd, gcd, gcd, then then rejuv timer.
However, I disagree that the gains are minor or illusory. The gain is that I always have the option of swiftmending - if a tank starts dipping low I can save him with a burst of healing at worst in 3 GCDs as opposed to 7 (assuming I don't want to drop my lifeblooms). Furthermore, consuming a 2 tick rejuv means that you will leave both tanks naked of rejuv for at least 4 GCDs, whereas consuming a 3 tick rejuv allows the rejuv on the other tank to tick for its entire duration. Even if that weren't the case - if our scope was only one tank - allowing a rejuv to tick for three times vs two is already a 50% increase in healing done by the spell.