Sunday, September 6, 2009 at 12:45PM |
Llyra When do you use Tidal Force?

Limited availability spells force the player into a difficult decision. Do I save it for when I really need it, or use it frequently to get the maximum return for it? How you answer that question probably says more about your psychology than the spell itself. How quickly must a spell be available again before you will use it without hesitation?
An example. I have been noticing recently that there is a Priest in my raids who uses Shadowfiend as their first action in a boss encounter. With a 5 minute cooldown in a fight that will probably last more than 5 minutes, that allows them to squeeze in 2 casts for maximum mana restoration. My Mana Tide Totem is on the same 5 minute cooldown and serves the same purpose, but I do not use it right away. My conservative use of that limited ability reduces its overall effectiveness.
For a long time I used Tidal Force like I would a 2 minute trinket. I wired it into a macro for a commonly cast spell, Chain Heal. Every time it was off cooldown, it would automatically reapply itself. In time I grew frustrated with wasting one of my few panic button spells during wipe recovery, an action that guaranteed it was not available in the first 3 minutes of a fight. I shifted it to my Nature’s Swiftness panic button and left it there.
At the time those two abilities shared a 3 minute cooldown. An instant-cast, guaranteed crit Healing Wave or Chain Heal is a pretty good rescue ability. Not as good as some, but solid. And if I only cast it maybe once a night? No big deal, right? That just meant there weren’t that many emergencies to handle.
Since then, Blizzard’s designers reduced the Nature’s Swiftness cooldown to 2 minutes. By doing so, they challenge the risk/reward curve that had me saving it for an entire night. At 2 minutes, my brain agitated, it’s okay to use it on struggling melee. It will probably still be available for the tank, when you need it.
Now Tidal Force is feeling stranded in that macro. Half the time it’s not available when I use it, which generates a harmless error. Is it time to shift its priority? Yes.
Today I restored it to my Chain Heal macro, with the tiny addition of “[combat]” to its cast. That will skip it during wipe recovery periods, and save it for when it matters more (but not most). Here is the complete macro:
/console Sound_EnableSFX 0
/use [combat] Energy Siphon
/cast [combat] Tidal Force
/console Sound_EnableSFX 1
/run UIErrorsFrame:Clear()
/cast [target=mouseover] Chain Heal
P.S. I had to share this page, found googling “tidal waves” for a picture to use with this post. A frozen tidal wave! Gorgeous!



