The thing about the Spam OT1 is that you need to be casting a high enough rank that he's getting healed to full every other second (or something like that) I really see no reason why anyone should be downranking to heals worse than 2k. If the guys healing OT2 can get him to full in 3 seconds instead of 6, so much the better, if he doesn't get hit for a while, they can regen mana.

I like to thank to all the suggestions within this thread that helped us to kill Patchwerk faster than we thought. As a tribute I am sharing my parser (written for Linux) for patchwerk data.

parser: http://www.clanbase.ro/wow/patchwerk/parse.patchwerk
patchwerk data: http://www.clanbase.ro/wow/patchwerk/patchwerk.1st.txt

Data from our first kill.
HS Hits: 265
HS Total Time: 6:33.375 [393.375]
HS Average Time: 1.490 seconds
HS Missed: 36 [13.58%]
HS Parried: 37 [13.96%]
HS Dodged: 21 [7.92%]
HS Landed: 171 [64.52%]
HS Total Damage: 1138872 [6660.07 damage/hit]

Rygars can you explain the use of the parser? seems interesting.

I believe we go

5/4/2 or 4/4/3, I forget exactly.

FSRT. Very useful little addon.

And Rygars, thanks for sharing your code there, good stuff.

^^ What mutagen said.

FSRT is incredibly useful for a healer. It gives you feedback on your performance for any given fight, and the numbers can help you choose what gear you need to use to maximize your performance. I typically spend 90-93% of my time in the FSR on Patchwerk, for example, so it's a fight where I should stack MP5 (as opposed to spirit) for maximum regen. As a point of comparison, I usually spend about 65% of my time in the FSR on Twin Emps. This is the kind of info I need to optimize my gear selections for encounters.

Our main tank uses a mod that sends HS hits to raid channel in a format like this:

I use chatlog mod to save all the channels to a log file. If you are under linux, you can filter the raid channel from the rest of the log like this:
grep "\[Raid" filename1 > filename2
filename2 was in my case patchwerk.1st.txt
Delete all the unimportant lines before *** Enrage in 7 minutes *** and after the last HS. Save the file. Check the file again for unimportant messages sent in raid channel during fight like commands, cheers etc. Now you should have a text file wiht Raid Warnings and Hateful Strikes. This is the file that parser can read.

Before running the parser make sure the execute flag is set. You can set it like this:
chmod 755 parse.patchwerk

You can run the parser by typing:
./parse.patchwerk

Enjoy the fight stats.

PS: I am working on stats filtered by unique players that received a Hateful Strike.

Just to give a quick update about how helpfull this thread has been.

As a raidleader this has been my big nightmare honestly, and as we cleared the trash last night i felt a slight touch of panic...

All for nothing :p

We wanted 16 healers, but only got 15..

Used 4/5/4/2 first 6 or so pulls...

The first 2 pulls we managed to last 2+ mins, so we started going all out.

6th pull we got him to 1%! Eventho i (As MT) died at like 80% and he chewed up like 3 DPS wars before 20%.

We got 0 TF and 0 ppl in 5/5 conq... Damage on MT was brutal tbh. (Yeah yeah, i got cocky and thought 4 healers could manage me anyway... I was wrong :p )

We switched 1 more healer to me and went 5 4/4/2... This worked alot better, but MT healers dropped the ball and got me killed the remaining tries of the night. (In all honesty it was only them to blame... I often died when 2 of them didn't cast a heal for 5+ seconds, which isn't acceptable.)

He's going down next week for sure, and if we have 16 healers we'll more or less 1-shot him im certain.

So just wanted to give huge thanks for all the discussions, tips, strategies and whatever that came from this thread.

We stacked our raid with our best gear tonight because of the so-called buff... didn't wanna risk it... so we dropped him with time to spare.
But can someone explain to me how patchwerk was changed exactly?

We dropped him last night, first real night of going at him. Everybody brought their consumables.

we started with a 4/5/4/2 configuration because we only had 15 healers. 3 paladins and a druid on mt. we have a thunderfury.

the offtank with 4 kept dying, so we went 3/5/5/2 , which went ok, but after a minute or 2 the MT just died.

Then we got another paladin in the raid and we went 4/5/5/2 with 3 pallies and the feral druid on MT. Killed him that try with about 45 secs to spare.

Fury warrior beat our best rogue on the 10% marker because of reck execute spam. We lost only the maintank on the kill on 2% or so because she popped shieldwall earlier in the fight.

priest mainly used flasheal spam, rank4,5 and the druids healing touches. flashheal spam for the added security and more chances to proc inspiration. OT1 had 3 priests, OT2 had 2, OT3 had 1 priest and 1 druid.

its really a doable fight.

yeah if anyone knows something, i'm very curious as we planned to clean abo wing first after the patch today. :)

Well, it's not like you could survived to his 7 min enrage before, shield wall or not. This change is just here to avoid kiting.

Well, from what i gather you could pop shieldwall and still get 10+ seconds alive thrue the enrage... But with them stacking it's harder...

We've never really been that stable at Patchwerk using a 4/4/4/4 strategy for the last few months. Last night we decided to change it to 4/7/3/1, and it worked great; got him first try. However, around 40% the last OT dropped off the HS list due to tanks 1 and 2 being topped very fast. Lost the 2 OTs around 7% and kited him to death. Was a shame, since we were on track for a 5.5 min kill, our fastest yet. We're going to revise it to 4/7/1/3 so that doesn't happen next week (second highest HP OT with the least healers, allowing last OT to get smacked more often).

They always stacked...

One is the enrage.

The other is a BERSERK.

Our video clearly shows both going off, and they've stacked since day one. One makes him hit harder and faster... one makes him instagib people - evasion tanks ftw at that point.

Sounds to me when he berserks, he has an antikite feature now - where anyone isn't in melee range he wipes the raid.

Anyway thanks for the help :)

Data filtered by tanks. I could find some nice hints like OT1 getting less HS than OT2 aka healing on OT1 was not that fast as we thought. Also you can notice the average time between two HS on each OT. We are puzzled by the lack of parries and dodges on OT1. We can't figure out why there is no parry and no dodge.

clanbase patchwerk # ./split.tanks
-rw-r--r-- 1 apache apache 19850 Sep 26 17:01 ./patchwerk.1st.txt
========================================================
Select a Patchwerk Log file for parsing: ./patchwerk.1st.txt
========================================================

Parsing Lixxy
HS Hits: 98
HS Total Time: 5:21.516 [321.516]
HS Average Time: 3.314 seconds
HS Missed: 24 [24.48%]
HS Parried: 0 [0%]
HS Dodged: 0 [0%]
HS Landed: 74 [75.51%]
HS Total Damage: 462263 [6246.79 damage/hit]

Parsing Ghimli
HS Hits: 129
HS Total Time: 6:29.266 [389.266]
HS Average Time: 3.041 seconds
HS Missed: 11 [8.52%]
HS Parried: 26 [20.15%]
HS Dodged: 16 [12.40%]
HS Landed: 76 [58.91%]
HS Total Damage: 495768 [6523.26 damage/hit]

Parsing Waitandbleed
HS Hits: 33
HS Total Time: 6:22.062 [382.062]
HS Average Time: 11.939 seconds
HS Missed: 1 [3.03%]
HS Parried: 10 [30.30%]
HS Dodged: 4 [12.12%]
HS Landed: 18 [54.54%]
HS Total Damage: 129471 [7192.83 damage/hit]

Parsing Arazor
HS Hits: 3
HS Total Time: 0:3.578 [3.578]
HS Average Time: 1.789 seconds
HS Missed: 0 [0%]
HS Parried: 1 [33.33%]
HS Dodged: 1 [33.33%]
HS Landed: 1 [33.33%]
HS Total Damage: 7351 [7351.00 damage/hit]

Can anyone explain why MT's sometimes get the HS? and somehow we had an OT become our MT... about 1 min in the fight, both of them unique in our experiences... or atleast the switch, MT might dodge/parry the random HS's he gets...

But is it just something healers need to take into account? that MT will get the occasional HS? if so how can you compensate for it?

No, its not something you have to take into account. Your MT is losing aggro to a HS tank. (I'm not sure if an OT stepping out of range might have the same effect, maybe someone else can confirm that).

Everytime we've seen it the logs showed it to be an overaggro, ie he's meleeing some other guy.

It could be confusing though, you have to check the logs instead of looking at tot. Many healers don't realize that his hott is backwards (targets the HS tank isntead of the guy he's meleeing), so if they look at that they think the mt is taking both.

Tried this tonight with a single OT strategy. The healers just couldnt work out how to make it happen though. I would rather use the single OT strategy because of one big thing: im tired of fishing stonescale eels.

Any tips on making single OT healing work?

Last time we tried single OT:

9/27 22:03:26.312 Patchwerk attacks. You dodge.
9/27 22:03:27.000 Patchwerk's Hateful Strike hits you for 6233. (216 blocked)
9/27 22:03:27.140 Patchwerk hits you for 1956.
9/27 22:03:27.468 Patchwerk hits you for 1769. (216 blocked)
9/27 22:03:28.281 Patchwerk attacks. You parry.
9/27 22:03:29.031 Patchwerk hits you for 1948.
9/27 22:03:29.062 Your equipped items suffer a 10% durability loss.

I was MT from the start, so no switch.

yer, make a profile.