Crusader's Coliseum - Gladiatorial Combat Without the Annoyance of Arenas - Page 12

Exemplar · 08/26/09, 11:35 AM

Originally Posted by tommynt

I would like to add a question aswell - most of our healers were not able to see firedebuff from the 2nd boss in raidaddons like grid or decursive - any advice to heal the person with the debuff fast appart checking raidchat/listening to vent?

It cannot be cleansed/decursed/etc so would not show in decursive and would not show by default in grid. Just add "Legion Flame" to your frames (Grid, Xperl, etc).

Angstonit · 08/26/09, 11:36 AM

As a troll rogue, if I sidestrafe, I can kill my own snobold fairly quickly, but I cannot stop strafing at all or I lose line of sight again.

McInaction · 08/26/09, 11:38 AM

Originally Posted by Shandara

I suspect the warlock stomping is deliberate.

Whenever our Warlocks would not banish they would be left alone (well as much as any raid member). Whenever they cast a single banish on the druid, instantly they would get ganked by whatever mobs were free of CC at that time.

Same behavior when I feared the hunter's pet and trapped. It was rather useful in our 10 man when we went for 'resilience will fix it' to keep the dk and enhance off our healer, as every time I feared they would run after me.

Nagisamuro · 08/26/09, 1:45 PM

Originally Posted by Exemplar

It cannot be cleansed/decursed/etc so would not show in decursive and would not show by default in grid. Just add "Legion Flame" to your frames (Grid, Xperl, etc).

I suspect he wants "Incinerate Flesh" - the debuff that does no damage as long as you give the person 60k healing before it expires. Legion Flame is the one that causes you to drop 3-4 green fires at your feet.

Exemplar · 08/26/09, 2:10 PM

Originally Posted by Nagisamuro

I suspect he wants "Incinerate Flesh" - the debuff that does no damage as long as you give the person 60k healing before it expires. Legion Flame is the one that causes you to drop 3-4 green fires at your feet.

Correct - I got distracted my the fire reference and Legion Flame has a DoT in addition to dropping the flames. Indeed, as you marked in quotes works precisely in Grid (and Xperl according to some of our healers).

Boss Mods should also announce the Incinerate victim. I know Big Wigs was doing it two weeks ago when we faced him the first time. It's also possible to have them raid marked through boss mods.

Romple · 08/26/09, 4:24 PM

Originally Posted by Pasture

As a caster I was unable to attack my own snobold due to los (it being on my back), but also AoE centred around myself (ie Arcane Explosion) didn't damage it either.

I can Living Bomb snobolds on me but that's it. So if you have DoTs, use them.

cutfang · 08/26/09, 9:35 PM

Originally Posted by Shandara

I suspect the warlock stomping is deliberate.

Whenever our Warlocks would not banish they would be left alone (well as much as any raid member). Whenever they cast a single banish on the druid, instantly they would get ganked by whatever mobs were free of CC at that time.

To add to this suspicion my holy paladin was targeted last in all bar one of our tries against the champions, regardless of how much I dispelled / turned undead. However I was a prime target for any counterspells / polys / fears.

KamPa · 08/27/09, 2:53 AM

Might as well add "Spinning Pain Spike" there, it takes ~2 seconds for Mistresses to actually hurt someone with their throw, but you can pre-shield, so it won't hurt - especially if they happen to land in a fire(seen it happen). Not so important on normal, but I guess it will be more painful on Heroic.

Cosa · 08/27/09, 3:03 AM

Just to add up on Champions strategy:
After whole discussion here, about focusing crowd controllers, and losing 5-6 people on start last week, we employed different pull.

Assigned crowd control and peelers
Charged in and used intimidating shout initially before tremor totem is down
Shout + initial "aggro" made quite attention to me that "small" crowd control on others did not produce assist trains we had last week.

Mordekhuul · 08/27/09, 8:54 AM

We had a ton of problems with Faction Champions this week, to the point we started wondering if something changed in the fight. Apparently not, or folks would already be talking here, though.

Is the difficulty that different depending which of the 14 champions show up? Our 25 man team one-shot it the first week it was out with very little prep and last night we wiped half the night on it.

I felt like folks were doing what was asked of them, and probably doing it in a more coordinated way than last week even, so it just felt odd to be losing folks so quickly (ret paladin + rogue + warrior assist trains killing healers in 0.5 seconds, etc).

I ended up going prot instead of ret and trying to wrangle the rogue the whole fight with taunts and stuns, as did another tank or two on different melee, but in the end by the time we got 2 of the champions down we'd be down by 5 players and at least 2 of them healers. Sheep wasn't effective, given the prevalence of key class DPS abilities that spread AOE and the propensity of mobs to wander through melee range.

We also had a lot of trouble trying to kill the shaman first...his heals were uninteruptable most of the time, somehow. I wouldn't think the disc priest's shield would be up long enough with 12 DPS on the shaman to prevent many casts, but we had folks punching their interrupts every cooldown during casts and being baffled by the amount of heals he got off.

KamPa · 08/27/09, 9:19 AM

Death Knights for controlling melee pretty much negate them. Between Grip and CoI, they're either crawling around, or after they decide to Shadowstep/Intercept, they're pulled into safe distance - it probably works during Bladestorm, too? Without them it might get much tricker, but I guess Prot Warrior could keep them down fairly reliable, too - between taunts, stuns and disarm.

I'm more interested in figuring out which of non-melee is most "dangerous" - as in bursty. Casters seemed pretty negligible, seeing as everyone has 130 resistance, reducing their damage. Hunter?

BeeLz · 08/27/09, 9:31 AM

Warlock was pretty annoying too since he basically spammed unstable affliction all the time so priests can't use mass dispell.

RootBreaker · 08/27/09, 11:15 AM

Originally Posted by BeeLz

Warlock was pretty annoying too since he basically spammed unstable affliction all the time so priests can't use mass dispell.

The silence from dispelling unstable affliction is itself dispellable.

Ashurbanipal · 08/27/09, 11:51 AM

Having had to run Gormok 19 times in ToC10, I was wondering if any other cat form druids have noticed that the snobolds do not jump on their back? I have seen them jump onto bipedal melee dps, but never myself, so i was wondering if Blizz was just too lazy to model the snobolds on top of a cat. I realize that for 19 encounters with a 40% chance of receiving a snobold it is still a ~2% chance of me just being lucky.

Ashen · 08/27/09, 12:07 PM

Originally Posted by Mordekhuul

We had a ton of problems with Faction Champions this week, to the point we started wondering if something changed in the fight. Apparently not, or folks would already be talking here, though.

Is the difficulty that different depending which of the 14 champions show up? Our 25 man team one-shot it the first week it was out with very little prep and last night we wiped half the night on it.

It's all dependent about your approach. If you correctly analyze the danger each one poses, the difficulty, at least on normal, is fairly equivalent. Odds are, because you facerolled it last week (which is good, no blame here), you didn't get a chance to accurately breakdown what the dangers were in the fight.

I felt like folks were doing what was asked of them, and probably doing it in a more coordinated way than last week even, so it just felt odd to be losing folks so quickly (ret paladin + rogue + warrior assist trains killing healers in 0.5 seconds, etc).

We had those 3 and the DK on our first week. We wiped the first attempt, killed them the second, but after working out a strategy around them. They need lots of control and it needs to be done appropriately.

I ended up going prot instead of ret and trying to wrangle the rogue the whole fight with taunts and stuns, as did another tank or two on different melee, but in the end by the time we got 2 of the champions down we'd be down by 5 players and at least 2 of them healers. Sheep wasn't effective, given the prevalence of key class DPS abilities that spread AOE and the propensity of mobs to wander through melee range.

How many healers do you run? And you probably shouldn't be the one trying to handle the Rogue. With our experience, the best solution was to put our Prot. Warrior on the rogue. They have a greater range of abilities to control the rogue.

We also had a lot of trouble trying to kill the shaman first...his heals were uninteruptable most of the time, somehow. I wouldn't think the disc priest's shield would be up long enough with 12 DPS on the shaman to prevent many casts, but we had folks punching their interrupts every cooldown during casts and being baffled by the amount of heals he got off.

Probably Grounding Totem. If it's melee interrupts that are missing, then I'm not sure what people are doing wrong. We never seem to have any major issues of that kind.

The key here is to have proper control on those melee faction champs. They are your worst. Kill two of the most dangerous healers first, or one if you're far too melee heavy. I tend to sacrifice several of our DPS for pure control roles while we burn down two of the healers. It's about control on that initial bit, zerging doesn't help anything.

I usually have a rogue on the target we're killing, a rogue on the other healer (or a DK / another class for better interrupts and more DPS pressure on the 2nd healer) and then DK's / Arms Warriors / Prot Warriors controlling the various melee classes. Kite using traps and actively watch who those targets are going for. Use peel CC's when they get close to a clothie, and keep people aware of their positioning and abilities.