Rancidclunge - Restoration Druid Review Sheet

Encounter: Crown of the Cosmos Mythic

Fight length: ~8:33.6

Source: Uploaded Warcraft Logs

1) Overall verdict

Rancidclunge is very active and clearly understands the high-button-volume nature of Restoration Druid. The log shows strong usage of Wild Growth, Swiftmend, Rejuvenation, Convoke the Spirits, and repeated ramp attempts. This is not a “low activity” healer log.

The main issue is not button volume. The main issue is ramp consistency and cooldown conversion. Some windows look well structured, especially around the 3:25–3:30 ramp, but other major cooldowns are used with much weaker setup. That means the same cooldown count can produce very different healing value depending on whether the raid is already covered in Rejuvenations and whether the payoff sequence follows correctly.

Biggest gains would come from:

making every Convoke/Tranquility window look more like the clean 3:25 ramp,
tightening Lifebloom / maintenance discipline,
using Innervate and major cooldowns with more deliberate ramp planning,
reducing isolated filler/damage globals inside or near healing windows.

2) What the player did well

Very strong core button activity. Across an 8:33 fight, the log shows:

Spell	Count
Rejuvenation	139
Rejuvenation (Germination)	59
Regrowth	104
Wild Growth	47
Swiftmend	39
Convoke the Spirits	8
Tranquility ticks / entries	24, representing 3 channels
Lifebloom	15
Starsurge	42
Nature’s Swiftness	7
Innervate	2
Barkskin	4
Ironbark	2
Nature’s Cure	2

Wild Growth and Swiftmend usage are good. Wild Growth was cast 47 times, with an average gap of about 11.2 seconds. Swiftmend was cast 39 times, with an average gap of about 13.3 seconds. That is a strong sign that you is pressing the spec’s high-priority short cooldowns regularly. Current guides specifically puts Swiftmend and Wild Growth high in the maintenance/cooldown flow and says to use them frequently when the raid has taken damage.

Swiftmend → Rejuvenation sequencing is mostly excellent. After 38 of 39 Swiftmends, a Rejuvenation or Germination followed within roughly two seconds. That lines up very well with the guide’s recommendation to follow Swiftmend with Rejuvenation because Swiftmend procs Soul of the Forest / Power of the Archdruid-style value.

There is at least one very good ramp window. The 03:15–03:30 section is the best example in the log. It contains heavy Rejuvenation setup, Wild Growth, Convoke, Swiftmend, more Rejuvenation, then Tranquility. That is the clearest “this player understands the spec” moment.

3) Highest-priority improvement areas

Issue 1 — Ramp quality is inconsistent

What happened: Some cooldown windows had strong setup, but others had very little Rejuvenation coverage before the cooldown.

Examples:

Cooldown window	Rejuvenation + Germination in previous ~15 sec	Notes
02:25 Convoke	1 total	Very weak setup
03:25 Convoke	13 total	Strong setup
03:30 Tranquility	13 total	Strong setup
04:27 Convoke	9 total	Good setup
05:31 Convoke	5 total	Light setup
06:31 Convoke	7 total	Okay but not exceptional
07:33 Convoke	8 total	Decent setup

Why it matters: Restoration Druid gets its biggest raid value by preparing the raid before damage, then converting that prep with Wild Growth, Convoke, Tranquility, and Regrowth.

Severity: High

Issue 2 — Innervate calls are too infrequent / too delayed

What happened: Innervate was cast twice, both times on Nolikita:

00:55.457 on Nolikita
05:36.097 on Nolikita

That is a 4:40 gap between Innervates.

Why it matters: Since Innervate is being assigned to another healer, the key point is not that Rancidclunge failed to use it for personal mana, but that the external Innervate requests/calls appear too spread out

Coaching interpretation: This looks assignment-dependent. If Nolikita is the planned Innervate target, then Rancidclunge is correctly giving it away. However, the long gap suggests that Nolikita may not be calling for Innervate often enough.

Rancidclunge should remind Nolikita that Innervate is available and encourage them to call for it earlier/more often, especially before planned high-healing ramp windows.

Severity: Low

Issue 3 — Tranquility usage has one excellent setup and two questionable ones

What happened: There are three Tranquility channels:

00:13.630
03:30.265
07:39.711

The 03:30 Tranquility is well prepared: in the previous ~15 seconds there were 8 Rejuvenations + 5 Germinations, plus Wild Growth and Convoke nearby.

The 00:13 Tranquility has some setup, but it occurs extremely early.

The 07:39 Tranquility has moderate setup, but less than the 03:30 ramp.

Why it matters: Tranquility should be lined up with dangerous moments and you should work on how you play before using it: put out Wild Growth and as many Rejuvenations as possible, then extend them with Tranquility.

Coaching interpretation: The 03:30 ramp shows you can do this correctly. The goal is to make every assigned Tranquility window look like that.

Severity: Medium to High

Issue 4 — All Swiftmends and Lifeblooms were self-targeted

What happened: Every Swiftmend targeted Rancidclunge. Every Lifebloom also targeted Rancidclunge.

Why it matters: Self-Lifebloom can be legitimate if used for Efflorescence control, and placing Lifebloom on yourself can give better control in some situations. However, every Swiftmend going on self may indicate a macro/default-target habit rather than active target selection.

Coaching interpretation: This is not automatically wrong, but it is worth reviewing. If the purpose is to extend self-Lifebloom and control Efflorescence, fine. If it is happening because you are always self-casting Swiftmend by habit, then you are losing the ability to use Swiftmend as a targeted emergency heal or to extend important HoTs on priority targets.

Severity: Low to Medium

4) Defensive cooldown usage

Your defensive usage should be more planned around damage spikes. The main issue is not that Barkskin was never used, but that it was often used too early, too late, or held for too long.

Key findings

Barkskin usage was too delayed. First Barkskin was at 04:18, despite several earlier damage events. In an ~8:33 Mythic fight, this gives away multiple possible uses.

Late-fight Barkskins missed the biggest spikes.

Barkskin	What happened	Coaching read
06:21	Used before the major ~06:42–07:00 damage cluster	Too early
07:28	Fell off before the huge ~07:40–07:55 spike	Too early
08:29	Used after most of the ~08:18–08:30 damage had already happened	Too late

The best fix is to pre-plan Barkskin timings. Based on the damage-taken, the strongest candidate windows are around:

01:20 — Silverstrike Arrow / Echoing Darkness spike
04:50 — Voidstalker Sting / Simulacrum Backlash overlap
06:42–06:46 — major Gravity Collapse / Cosmic Barrier overlap
07:40–07:43 — largest late-fight overlap
08:18–08:20 — final Gravity Collapse / Grasp sequence, if available

Ironbark note

Ironbark was used twice, at 04:54 on Diadrin and 07:16 on Homietron. This is likely too low. Ironbark has a short cooldown and could have been used much more often across the fight, either on assigned targets or to cover predictable danger moments. You should look for more planned uses and aim to avoid sitting on Ironbark for long periods.

Coaching takeaway

Use Barkskin as a planned mitigation tool, not as a reaction to feeling low. The biggest improvement is to Barkskin the actual stacked damage windows, especially around 06:42 and 07:40, rather than pressing it on earlier warning hits.

5) Timestamp review — good and bad examples

Good example — 03:12 to 03:30: clean ramp into Convoke + Tranquility

Approx. sequence:

03:12.580 — Swiftmend
03:13–03:20 — multiple Rejuvenation / Germination casts
03:15.154 — Wild Growth
03:24.467 — Wild Growth
03:25.455 — Convoke the Spirits
03:28.598 — Swiftmend
03:29.432 — Rejuvenation + Germination
03:30.265 — Tranquility

Why this is good: This is the best ramp in the log. In the ~15 seconds before Convoke, you applied 8 Rejuvenations and 5 Germinations, used Wild Growth twice, then converted with Convoke and Tranquility. This is close to the ideal logic: build HoTs first, then use cooldowns to amplify/extend/convert the setup.

Coach note: This is the model. Copy this structure for every major planned damage event.

Weaker example — 02:15 to 02:25: Convoke with very low preparation

Approx. sequence:

02:15.324 — Swiftmend
02:16.544 — Rejuvenation
02:18.681 — Wild Growth
02:19.348 — Starsurge
02:20.647 — Lifebloom
02:22.374 — Cat Form
02:25.452 — Convoke the Spirits

What is weak: In the ~15 seconds before this Convoke, there was only 1 Rejuvenation and 0 Germinations. That is a very light setup for a major healing cooldown.

Coaching interpretation: This looks more like Convoke being used because it was ready, not because a ramp had been built. Even though raid damage was low here, the setup was too thin.

Fix: Start the ramp earlier. Aim for a clear Rejuvenation block before Convoke, then Wild Growth / Swiftmend / Convoke into Regrowth follow-up.

Mixed example — 07:33 to 07:44: good cooldown chain, but lighter than the best ramp

Approx. sequence:

07:29.275 — Wild Growth
07:30.310 — Lifebloom
07:33.113 — Convoke the Spirits
07:36.415 — Swiftmend
07:37.491 — Rejuvenation + Germination
07:37.695 — Potion of Recklessness
07:39.460 — Wild Growth
07:39.711 — Tranquility
07:44.031 — Rejuvenation + Germination

What is good: Cooldowns are chained together well: Convoke into Swiftmend / Rejuv / Wild Growth / Tranquility.

What is weaker: The pre-Tranquility setup is not as dense as the 03:30 window. In the previous ~15 seconds, there were 3 Rejuvenations + 3 Germinations. That is not terrible, but it is not the strongest possible Tranquility setup.

Coaching interpretation: This is a decent ramp, but it could be stronger with more deliberate Rejuvenation loading before the Tranquility.

6) Mechanical / execution notes

Swiftmend follow-up is strong. 38 of 39 Swiftmends were followed very quickly by Rejuvenation or Germination. That is a major positive.

Wild Growth usage is strong. 47 casts over 8:33 is good activity. The average gap is ~11.2 seconds, and there were no massive long-term gaps.

Nature’s Swiftness use is decent but not perfect. 7 casts is reasonable. There is one very long gap from 01:24 to 03:56. This may be damage-pattern dependent, but it is worth checking whether NS was being held too long.

Barkskin usage starts late. Barkskin was used at 04:18, 06:21, 07:28, and 08:29. There is no Barkskin in the first four minutes. This may be fine if no personal danger existed, but on Mythic progression/kill logs, earlier planned Barkskins are often free survivability.

Ironbark usage is low but assignment-dependent. Only 2 Ironbarks: 04:54 on Diadrin and 07:16 on Homietron. This may be correct if externals were assigned, but if not assigned, there may be missed tank/target support.

Damage contribution exists. 42 Starsurges and 4 Ferocious Bites show you are contributing damage during the fight. That is good, but damage globals should not appear inside weak healing setup windows. The 02:19 Starsurge shortly before a lightly prepared Convoke is an example to review.

7) What to fix first, in order

Priority 1 — Standardize ramp setup before major cooldowns. Before Convoke or Tranquility, deliberately load Rejuvenations for 10–15 seconds, then Wild Growth / Swiftmend, then the major cooldown.

Priority 2 — Review self-cast habits. Self-Lifebloom can be fine. Every Swiftmend on self is worth questioning. Make sure it is intentional, not just macro autopilot.

8) Practice goals for next time

Focus: Focus on ramp prep. Before every planned Convoke/Tranquility, ask: “Do I have enough Rejuvenations out, and is Lifebloom active?”

Short in-head checklist during the fight:

Lifebloom active?
Damage in 10–15 seconds?
Start Rejuvenation ramp now.
Wild Growth before payoff.
Swiftmend → Rejuvenation.
Convoke / Tranquility.
Regrowth while Abundance value is high.
Do not spend filler damage globals if the ramp is underbuilt.

9) Final coach summary for the player

Rancidclunge, your activity is good. You are pressing the important buttons often, your Wild Growth and Swiftmend usage are strong, and your Swiftmend → Rejuvenation habit is genuinely solid.

The thing holding the log back is not effort or APM, it is ramp consistency. Your best window around 03:25–03:30 looks like proper Restoration Druid gameplay: prep HoTs, then convert with Convoke and Tranquility. But some other cooldowns, especially the 02:25 Convoke, are much thinner and look reactive or cooldown-driven rather than planned.

If you fix that, your healing profile should become much more stable and your cooldowns should gain a lot more real value without needing dramatically more casts.