Good afternoon lads and lasses! Welcome back to another of our beta reads. With fresh raid testing under our belt (the last ones were in the first week of May), we need to share some updates. The most recent raid testing took place on Friday the 17th and Monday the 20th of June. On top of that, this morning a patch hit the beta realms with an abundance of patch notes to dig through. Let’s get started!
Oh hello cloudburst
We made it crystal clear before. We don’t like cloudburst totem. We do our main testing in raids, and that means that until this Friday our opinions were over a month and a half old. Making it easy to miss some of the fun people were having with this talent meanwhile. So now you may wonder, what changed? How did cloudburst go from the worst of the worst, to the best. Even now that it is competing with echo?
Cloudburst today on live (Warlords) is clunky. It will collect all healing spells (and their multistrikes) for 15 seconds. After that it distributes 20% of healing done while it was active, equally amongst all injured allies within 40 yards. To clarify, it collect all effective healing done by direct healing spells. This means your healing wave, your healing surge and your chain heal, but not your totems like healing stream and healing tide. Making it similar to the current working of ascendance to the degree that only direct healing spells are affected. Once the healing is collected and the stored healing is released, it heals injured allies and distributes evenly. This means that if half the raid is not full hp, and 2 are extremely injured, ten players will be healed for a little bit. Resulting in mostly overhealing and only two semi effective heals. Adding the fact that overhealing is not counted during the charging up period of the totem, it is losing even more potential. All of this together made cloudburst no match for high tide in warlords.
So what changed?
In the early alpha, cloudburst was put on the same tier with bottomless depths and ancestral guidance. At least, that is how it was patched together by sites like Mmo-champion and Wowhead. At that point we could see it becoming viable given the competition it had. After that, Blizzard released a talent tree putting ancestral guidance on a different tier and matching cloudburst with bottomless depths and echo of the elements. Different story. Echo was still strong at this point, and cloudburst still clunky. And that’s when it happened. Somewhere in between raid testing, a bunch of guys went into dungeons and started producing giant cloudburst numbers. As new raid testing occurred, we had to try this out for ourselves. On the boss Krosus (AoE healing dream) this is what Keehn did:
Yeah.. so that happened. Some words of encouragement for struggling resto shamans out there. Notice how his overhealing is under 19%? Your time is coming: god-mode moments are about to arrive. There’s nothing like the start of an expansion for a resto shaman. Soon you’ll be able to breathe, to unleash the elements. Ok Dorelei, I get that you’re excited, but can we see a break down of these numbers? Sure you can! If you want to dig through these logs yourself, then you can find them right here. Disclaimer: obviously we chose a very shaman friendly fight and pull. This is by no means the number display in all scenario’s.
Our point is, cloudburst is strong. Don’t mind healing tide in this example though, for that we need some different logs. Let’s examine why cloudburst is so strong right now. First of all, it stores more healing (30%), secondly it stores overhealing (big one). Still overhealing is not mana efficient, nor does it benefit from your mastery, but it is a big change from not counting at all. Thirdly, it benefits from ancestral guidance. All these factors make for a very strong talent.
In the distance there is a faint echo
Echo, on the other hand, got nerfed a few weeks ago and got nerfed again today. There is nothing left of it. It is now a remnant of its glorious past. The change logs today read:
Echo of the Elements (Restoration) In addition, when you
cast Healing Wave, Healing Surge, Riptide, or Chain Heal, you have a 10% chance to generate a charge of Riptide.
They really don’t want us using this talent anymore. That is pretty obvious. So what else changed?
- Astral Shift Shift partially into the elemental planes, taking 40% less damage for
6sec. Instant. 1.5 min cooldown.
- Healing Tide Totem Summons a totem at your feet for 10 sec, which pulses every 2 sec, healing all party or raid members within 40 yards for [ 1 +
80%of Spell Power ]. Shaman – Restoration Spec. 5.6% of Base Mana. Instant. 3 min cooldown.
- Healing Wave A slow but efficient wave of healing energy that restores
[ 450%of Spell Power ] of a friendly target’s health. Shaman – Restoration Spec. 9% of Base Mana. 40 yd range. 2.5 sec cast.
- Healing Surge A quick but expensive surge of healing energy that restores
[ 450%of Spell Power ] of a friendly target’s health. Shaman – Restoration & Elemental Spec. 18%of Base Mana. 40 yd range. 1.5 sec cast.
We can summarize this as a buff to our raid cooldown and buffs to our direct healing. So what happened to other healers?
- Holy priest: buff to raid cooldown (divine hymn 720% of spell power instead of 600%), nerf to single target heals (500 to 475% of spell power for flash heal and heal);
- Disc priest: buff to shields (550% of spell power instead of 500%)
- Mistweaver monk: buff to raid cooldown (revival 720% vs 600% of spell power), nerf to renewing mists (70% instead of 75%) and buff to vivify (3 target heal) of 250 to 275% of spell power.
- Holy paladin: no apparent changes (?)
- Resto druid: buff to raid cooldown (tranquility to 900% vs 750% of spell power), buff to healing touch (direct heal) from 360% to 400%.
There seems to be generic buffing of raid cooldowns, and some balancing of direct heal power. It is interesting to see how much love tranquility gets, considering it was already a very strong cooldown. Worst case scenario: we will have to bribe a priest to leap the druid mid-tranq.
Did you spot more changes to the resto shaman? Let us know in the comments!