May 6, 2011

3's Kittycleave with holy pally

Sadly we are still struggling for 2.2k. We have good strats against TSG, KFC, RMP and hybrid melee+caster cleaves, double casters are the teams which are fuck us over.

Especially lock mage shaman. I dunno what should we do. I stay mage most of the time, warri on lock to mitigate cc and spilt damage to run shaman oom or overextend, but after a few minutes of struggling they cc us over and they score a kill.

I am thinking maybe we should go heavy on lock every 45 secs when throwdown is up,else we should stay on lock / mage as usual. The problem is they have so many cc's they can easily lock down 2 people at once.

RMP is a double edged blade, but usually we open up priest, i put up bleeds then go for mage all match. cc on rogue (most of the time as soon as sdance pops(msbt trigger <3)), playing pally/feral against mage/rogue, while my warrior kills the priest in a minute. the priest has to overextend, cannot fear due to hamstring, mage cannot cast freely, and i can peel the rogue off me well. has to keep up focus FF on rogue, NG when smoke, keep trinket and survi instincts for oh shit moments. they could go to the warrior to prevent this (2k rmps rarely do this) then we should exchange tasks with warrior.

TSG is a problem if the healer is shaman. FrostDK and warrior can really put out huge pressure. We usually go for DK swap cc's on warrior+paladin. Most of the times my pally calls a HOJ on enemy healer which cc i extend with a cyclone on my own. That is the window for a kill.

LSD 2.0 Lock+balancedruid+restoshaman
I focus kick, cyclone, bash balance druid mostly all match, ride the lock. Retreat when in danger, onto paladin, warrior stays out if he has def. cds or comes back as well for a breather. After topping us up, paladin lets us go out again. Instants are ridiculous in this match, balance druid simply keeps up Insect swarm, moonfire+sunfire spams all the time. NG treants. I kill lockpet when not in imminent danger, preferably behind pillar when going back to my paladin.

No comments: