Resto PvE Compendium and General Discussion - Page 25

diegoa · 06/29/10, 5:46 PM

Originally Posted by Arawethion

Here's my current local sheet, so you can make sure everything lines up currently. Then I can start from here with properly noting changes (which I might not be doing much with the Tree sheet for the rest of WLK).

Done - version 1.1 is up. I've updated NG Uptime for chaincast RG and some non-math things.

About changes: the easiest for me is just to see which cells were changed, if many - range or sheet

• Hamlet · 06/29/10, 11:58 PM

As a quick note, for people going to work on Halion, I'd recommend 3/3 Subtlety. (I mean, I always said that people may as well have it instead of the junk point in Tranquil Spirit, but you'll probably be happy to have it here).

• Hamlet · 06/30/10, 1:40 AM

Checked Regrowth coefficient.* 0.188 per tick is more accurate that the elaborate calculation I was trying to do to determine it precisely (I wonder why though, that works for other partial direct/partial HoT things).

*Ticks for 994 with 3506 spellpower, in my Moonkin spec, out of form, no buffs.

Hagen · 06/30/10, 4:50 AM

diegoa: Are you modelling the Nourish glyph? Since the site shows me the same HPET for Nourish with 1 or 2 HoTs when glyphed.

Erdluf · 06/30/10, 7:52 AM

Originally Posted by Hagen

diegoa: Are you modelling the Nourish glyph? Since the site shows me the same HPET for Nourish with 1 or 2 HoTs when glyphed.

Missplaced parenthesis in one of his scripts:

a.AverageNourish*(1+(c>0?0.2:0))+b*c+(this.character.getCurrentSpec().hasGlyphOfNourish()?0.06*c:0)+
this.basicCalc.TraumaTick;

The underlined close-paren (the second close-paren) should be moved to just after the last close-paren.

In the above, 'c' is the number of HoTs, and 'b' is the 4t7 bonus (zero if you don't have 4t7).

As currently written, an extra HoT increases the heal by +0.06, instead of by 6% of the non-HoT heal.

diegoa · 06/30/10, 9:50 AM

Originally Posted by Erdluf

Missplaced parenthesis in one of his scripts:

a.AverageNourish*(1+(c>0?0.2:0))+b*c+(this.character.getCurrentSpec().hasGlyphOfNourish()?0.06*c:0)+
this.basicCalc.TraumaTick;

The underlined close-paren (the second close-paren) should be moved to just after the last close-paren.

In the above, 'c' is the number of HoTs, and 'b' is the 4t7 bonus (zero if you don't have 4t7).

As currently written, an extra HoT increases the heal by +0.06, instead of by 6% of the non-HoT heal.

Exactly

Already corrected, will update web a bit later today.

Thanks Erdluf and Hagen.

UPD: Fixed on web site.

Eyece · 07/01/10, 5:46 AM

Thoughts on heroic Halion for resto druids? We obviously work extremely well in the 'twilight realm' since we can move+cast while dodging beams. Now that i think about it the entire fight is pretty movement oriented. I'm glad its not another heroic LK repeat of being sat.
The fight probably should be 3 healed on 10 man heroic to make things easier, but we killed it with 2 healers (resto+disc).
I healed the 'twilight realm' while the disc priest remained in the normal realm. It took awhile for us to adjust to handling the tank dmg while handling the debuff..especially if either healer got the debuff.

10 man heroic kill for those interested: YouTube - Tasty Beverage vs Halion 10 Heroic
resto druid pov in the twilight realm (beams).

EDIT: killed 25 man: YouTube - Tasty Beverage vs Halion 25 Heroic (Resto Druid PoV)

silly purple dargons

• Hamlet · 07/01/10, 1:08 PM

I've only attempted 25m Heroic. Trees do seem strong, yes, we've been bringing two. We're still shuffling our setup around a little though. I mentioned above that Subtlety is a good idea.

Otherwise, I'd just make sure people have the basics down--proper UI to alert you to important debuffs makes them easy to handle. General proficiency at healing while moving is important. In addition, if you have Remove Curse on an awkward keybind that can't easily be used smoothly while moving quickly, you might want to change that.

Arythorn · 07/02/10, 2:47 AM

Beat him on Heroic 10 tonight using a 4 healer, 2 tank, 4 dps setup. There doesn't really seem to be an enrage timer so this kept it the most stable. Otherwise, in P3 you run the risk of things getting ugly when the healer you leave alone gets marked. We tried 3 healing it first with me and a shaman down and a paladin up. and then later with just me down below and the paladin / shaman up top. It was workable but sketchy at times. I actually think we could've beat it that way but for some bad placements on combustion drops that hosed us below.

However,when one of our DPS had to log, we figured to try it with a 4th healer just to see and I have to say this put the encounter on complete cruise control. In P3, 1 tank, 2 healers, 2 dps up top and the same down below. Kept melee dps and mobile healers (me and a shaman) down below and ranged dps and more stationary healers (2 paladins) up top. In addition to keeping healing more stable, it also kept dps more even in both locations given 2 up and 2 down instead or 3 in one and 2 in the other.

Anywho, it's more fun 3-healing it but way easier to beat with 4. I'll post a vid tomorrow but my feedback on 10 or 25 would be to go healer heavy as necessary to keep the encounter stable.

EDIT: Vid finished uploading: YouTube - Intent - Halion 10 Heroic - Resto Druid View

• Hamlet · 07/04/10, 12:54 AM

Grabbed some guild members to bang out 10H. As expected, after working on the 25H version that has adds, all the other modes are kind of silly. Video (still processing at time of this post):

YouTube - Juggernaut vs. Halion, 10-man Heroic
The video shows me facing outwards for phases 2-3. I'd recommend that for people learning the fight--you're always looking at the orbs so you basically can't die to them, you can move out easily with Mark, and there's no reason to face inwards as a healer.

Agreed, 3 healers would be doable but 4 is easy. We wiped twice at the P3 transition trying to get set up with one healer upstairs then just decided it was silly--I respecced Resto and it became very easy. DPS is easier to balance with 2 on each side anyway.

• Hamlet · 07/04/10, 3:29 AM

Random note, it seems like they fixed the Tree form + Hurricane bug at some point.

• Hamlet · 07/10/10, 1:52 AM

Totally random--has anyone looked into how Wild Growth selects its targets if everyone is at full HP?

Athari · 07/10/10, 6:38 AM

Pets seem to eat alot of the charges when all at full health. Maybe it goes by least total HP.

• RobotChicken · 07/18/10, 7:15 PM

We're on an AFK break right now, and I'm testing this out - I'm pretty sure it has to do with proximity to Wild Growth target. Also, every time it has targeted the only pet in the raid, so that could be it as well. It almost certainly isn't going by least health because one of our tanks has been getting it every time.

It's also possible that it's just plain old random.

• Hamlet · 07/18/10, 7:23 PM

Originally Posted by RobotChicken

We're on an AFK break right now, and I'm testing this out - I'm pretty sure it has to do with proximity to Wild Growth target. Also, every time it has targeted the only pet in the raid, so that could be it as well. It almost certainly isn't going by least health because one of our tanks has been getting it every time.

Oh, that might be it. Yeah, the reason I asked is that my observations were:
1) It tends to hit the same people repeatedly when everyone's at full HP (you can easily see this if you're casting it on melee for Revitalize procs at Saurfang, for example, or even if you're just standing around spamming WG before combat). So it's something nonrandom.
2) It's not the lowest-HP people.

Also, when I asked others about smart-targeting once, a Shaman told me that Ancestral Awakening always seems to target himself (can't really verify). But that would be consistent since AA is a self-centered smart heal.

The only issue is that, if I recall, WG doesn't necessarily apply to its target. I'll check this later.