Monday, February 15, 2010

Tanking Crib Sheet – Sindragosa Rough Draft


Finally killed her, so hopefully this will help some folks trying the old girl out. One thing I really loved about this fight, it actually penalizes you for just mashing your buttons. I thought it was brilliant, though our mage doesn’t agree (of course he argues that the sun isn’t even real).

The Setup

This is, for probably anyone not rocking full 264 gear, a two tank fight. Phase 1 requires one tank (though 2 can be used), and Phase 2 is a tankless phase (think Ony/Sapph air phase). Phase 3 is where it really gets interesting though, so you’ll have to be on your toes.

We’re using three healers for this right now, as there is a pretty nasty debuff that they can get – but more on that after I cover the important parts.

Key Abilities – for Tanks

· Cleave – it’s huge. Don’t point her towards the raid.

· Tail Swipe – Forget the slackness we got with Malygos, not only does she have a tail swipe, she’ll also randomly smack someone who’s not actually behind her.

· Ice Breath – Think Ony, but frost. On steroids. Stacks a chilling debuff that reduces movement speed and attack speed. Can be temporarily offset by Hand of Freedom, but it doesn’t fully remove the debuff (no clue on druid shapeshifting).

· Pulse AoE – Every 45 seconds or so she will pull everyone into melee range. Start moonwalking to get about 15-25yds away from her. You can eat one in P1, but in P3 you can’t afford to eat the damage.

· Melee DoT – There’s a 20% chance on every swing to apply a DoT to yourself. If you have enough threat, just stop attacking for a few seconds. This is VERY important in P3 when you get the debuff that will increase magic damage taken.

· Arcane Buffet – Applied in P3, this increases the amount of magical damage taken. You will need to swap with your OT at around 5 or so stacks. With the speed that this is applied, you will be in constant motion between ice-blocks to drop your stacks, and tanking Sin.

The Pull

Sindragosa will pull immediately after the 2nd of her two Frostwyrm buddies is killed. They’re fairly straight-forward, and you’ll recognize Rimefang from PoS. Rimefang has a frost ability similar to PoS, the other drake fears. Kill whichever one you want first.

When Sindragosa lands you’ll want to point her North, away from the stairs you just came down. If you use the center floor diagram as a marker (I’ll try and get some screenshots tonight), hold her right in the center of the compass rose. If you just backpedal on her first pull/AoE, she should come right to the top of the circle. Hold her here for the duration of the phases (most important in P3).

Once she takes off into the air, P2 starts. Your biggest challenge will be getting to the frozen players since you’re slowed. Tips on positioning them is down below.

The Crux – Phase 3

Once you get her to 35%, P3 begins. This is the crux of the encounter. Players will be getting frost tombed, so make sure you have two areas designated for them to run to that is at least 10yds away from anyone else. Tanks will be taunt swapping, and running behind the ice blocks to help break them, and to drop their Arcane Buffet debuffs. As soon as your stacks are gone, start the tank swap dance again. You should be able to time it so you don’t both eat a frost breath.

It’s important to keep your head in this phase and just focus on your role. Hold the boss long enough for the OT to drop their stacks, then drop yours. Be ready with cooldowns if you get above 6 or 7 stacks, as you can easily be one shot at that point. Ardent Defender and our 4pc T9 bonuses are our friends here. Save your HoF for moving away to drop your Buffet stacks, as you can easily moonwalk to avoid the AoE.

Everyone else

Phase 1 – DPS like you mean it. There is a chance to get a stacking DoT every time you melee or cast a spell. It hits for 2k per tick, and it can add up pretty fast. Watch the tail swipe, and the cleave. Run away when you get pulled into her (really – it’s a dragon, and you’re tasty).

Phase 2 – This is her air phase. Two people will be ice blocked. Stand with the block between you and her breath animation, while breaking them out. 2 breaths per block.

Phase 3 – Pick two points 10yds away from everyone else to stand when you get chosen for the ice block. LoS her to drop your Arcane Buffet stacks, and break the ice blocks. Healers will have to take turns LoSing and healing.

Friday, February 12, 2010

The guild alliance that works


About four weeks ago, and formed a guild raiding alliance to tackle ICC 25. This alliance got its legs back in ToC25, when we joined up in an informal manner to help leverage ’s raiding skills with ’s larger raid pool. After some initial rocky starts, we managed to regularly clear the instance, and even managed to get the farming run down to a fairly reasonable time.

When ICC came out, we faced the decision of trying to stay on top of the now cleared 10 man strict rankings released by Guild-Ox, or forging a new alliance to get the gear from the 25 mans. We went back and forth quite a bit over this decision, but ultimately we decided to plow ahead and give it a go.

I’ll detail our reasoning below, but we knew going into this that we needed a tighter control over the raid than we had in ToC. Our raiding style is markedly different than that of , and we needed to make sure that we were all operating from the same page. We drew up a list of our expectations, negotiated some details, and away we went.

The rocky start

Like most collaborative efforts, our alliance wasn’t all roses and candy at the start. We had some issues, with either player capability, or with player availability. I’m pretty sure our first raid started about 10-15 min late, and we had a ton of random afk’s after every Saurfang wipe. Fortunately the two GMs work together to resolve any issues, and it’s been fairly smooth sailing.

Our contract and expectations

Our contract was laid out with one specific purpose in mind – to keep the same 25 people showing up every week for ICC content. Nothing hurts progression more than having to teach the same fight over and over, because Joepally decided he didn’t want to go that week. To help enforce this, we setup a set roster of players that would be invited every week. As an incentive, any guild who had a member no-show was either responsible for providing an equally geared replacement. Failure to do so results in a 2k gold fine to the guild. Not a bad deal really.

Our contract covered loot, legendaries, tier tokens, etc. Flasks are mandatory for all boss fights, and there’s always a fish feast. Saronite is /rolled on for the first one, and then alternated between GMs after that. BoE epics have to be equipped and then socketed with some green gems we carry specifically for this purpose (or enchanted).

How we’ve done

With just 12 hours of raid time (4x3 hour sessions) we’ve managed to clear the Lower Spire, Festergut, and Rotface. Are we a little late to the party? Sure, but we’re certainly being fashionable about it. Our pulls now start exactly on time, and much of the original fuss has dissipated. A few folks have been replaced due to poor performance, and that’s really woken the whole team up. I do consider the steady raid group to be a major part of our success, and I have to tip my hat to the GMs that pulled it off.

This week we’ll be heading into the Blood Wing, and with any luck we’ll notch up the Princes and maybe Dreamwalker before we start taking on stage bosses. It’d be interesting to see what we could accomplish if we added a second night to the schedule, but I’d only do that if it was the same raid team. Adding new members every day is ftl.

Tuesday, February 9, 2010

Blood Princes Kill Video

Shot by Mongr - resident Disc priest. Remember to watch it in HD, and hope you enjoy the music. We use 2 tanks and three healers for this fight in 10 normal, and don't use a ranged tank at all.

Enjoy!

Monday, February 8, 2010

Exploits vs. Creative game mechanic use


Well, it’s happened. In case you’ve been disconnected from the internet for the last week, let me give you a quick rundown. Ensidia defeated Arthas in ICC25 for the world first kill – and promptly got a 72 hour ban for using an ‘exploit’ to trivialize the encounter. I’m not saying they intentionally used an exploit, or that Blizzard’s reaction was right (or fair). I instead want to examine the use of ‘creative game mechanics’.

The exploit in question seems to be the use of Engineering charges/bombs on some ice-blocks that appear during the encounter. While I’m not quite sure as to what these blocks are exactly (I plan on seeing the first pull blind), this sounds exactly like something Ensidia (or any other top guild) would do. Utilize every advantage possible to get through an encounter – even if they knowingly use a bug. While the data from mmo-champion seems to absolve any intentional misuse, and I don’t believe anyone was able to actually test the fight on the PTR, the fact remains that Blizzard felt it was an exploit – and took action.

Using every trick in the book

Let’s flash back to Vanilla WoW for just a minute, and I’m not even going to touch AQ-40 or Naxx – I’m just going to look at BWL.

Now my guild wasn’t anywhere near server firsts, let along world firsts, at the time – but we still tried to use every option that was available to us – outside of downright cheating. Need more Fire Resist for Vael? MC a mob in BRS and get the buff (what a nightmare that was). Problems gathering all the adds on Nef? Use Battle Shout spam.

Both of these were eventually removed/changed in the game, but it shows that bugs and exploits have been available for a long time. Remember the rogue who solo’d the chess event in Kara by sneaking in (and maybe wall hacking) past all the trash? Well, now the trash can see through stealth.

Were these exploits, hacks, or just clever use of in game mechanics? What about standing on the stables roof in AB? Using the ledge in HoR? Door strategy for Twins? Zerging Sarth 3D? Pet tanking? Some of these are specifically forbidden by Blizzard (you can catch a ban for using the AB tactic), but some are either overlooked or encouraged (door strat). Some get fixed through game changes (pet tanking Sarth 3D), and some are just ignored because the content is now a year old (zerging Sarth before a single drake can land).

To cheat, or not to cheat – that is the question

Regardless if you agree that any of the above (or any of the other exploits that have taken place in Wrath) are technically cheats – you can’t deny that they are bypassing certain elements of the encounter that were intended to be a part of it. The choice to use these methods is entirely in the hands of the raiders (and the guild leadership), and ultimately on the shoulders of the leadership.

The question is though – is it really a cheat? Let’s look at Ensidia’s hard mode Hodir kill. In order to get the requisite DPS buff, they kited/chained/MC’d mobs from Freya’s room over to Hodir – and then proceeded to roll him. I’m not saying it was easy, but it certainly allowed them to complete the achievement ahead of the expected curve.

Is it really cheating though? It’s not like someone was able to Google some cheat-codes and punch in the Contra 40 lives code to make this happen. Instead some extremely creative players saw an opportunity and the raid tried it with great success. How many other times did this end in disaster? Where is that invisible line between amazing side effect (using a /cancelaura on a Paladin’s Divine Sacrifice) to game breaking exploit (holding Yogg’s adds by healing from the brain room)?

So does the punishment fit the crime?

Short of any evidence proving that Ensidia was aware that their actions were exploitive, I’d have to say no. This action will have ramifications far beyond losing the world first title – they will now be a full week behind in progression against any other guild that takes Arthas down this week. The only way I can see this as being ‘fair’ is if no other 25 man guild actually downs Arthas (yeah, good luck with that) before the reset.

Of course if they knew it was an exploit, then I’d say perma-ban them. I mean really, it’s one thing to utilize an existing mechanic; it’s another entirely if they had someone standing at a specific point doing a specific action every time.

Conclusion

Most of us have that niggling voice inside that lets us know that something about your actions is wrong. Say what you want about this being just a game – if that was the case nobody would be upset about this and bloggers everywhere would have to find a new topic for the day.

I don’t condone cheating, but I applaud the creative use of in game mechanics. Blizzard will never be able to catch every bug, simply due to the ratio of players to staff. There are some amazingly creative players out there, and trying to come up with every possible solution just isn’t viable. Right or wrong though, it’s Blizzard’s game in the end.

Who knows, this may speak of things yet to come. Watch out wall walkers.

Friday, February 5, 2010

The slap I missed


So apparently the Paladin tanking community has just been slapped in the face with a nerf to our Sacred Duty talent – reducing the overall bonus stamina from +8% to +4%. This was hotfixed in yesterday, and if I read the Paladin forums correctly, I should be up in arms and using my massive blogging base to slam Blizzard for the affront to my tanking manliness.

Or I could just come clean and admit that this nerf was so massive that I missed it entirely.

That’s right. This huge slap in the face was so big, that I failed to notice any change. Maybe it’s because it was late, or we continued to have problems with Sindaragosa (we’re making progress though), or because – hell I don’t know. Regardless, I seemed to have glazed right over it.

The nerf I’m expecting

What I do expect to see though is some kind of nerf to SoC. It’s got to be pretty difficult to fix though, because it’s a seal, not a spell (in and of itself). This single talent, one tiny talent point in the ret tree, is such a huge part of why Protadins are insane DPS machines in heroics. Here’s why.

1) SoC is not affected by any kind of AoE reducing coefficient. While the tooltip states that it will strike up to 2 additional targets, I know my SCT shows a lot more ticks going off (maybe due to the next issue).

2) SoC can proc off of 2 of our base 9/6/9 rotational abilities, plus all white swings. This now means that 4 of 5 of the 9/6/9 abilities are AoE attacks.

3) Reckoning can cause more strikes – so the more mobs you pull, the greater your chances of getting reckoning to proc. I believe that SoC cannot proc off Reckoning, but I could be wrong.

4) SoC is holy damage that works off the physical damage table. This means with enough expertise and hit (which most tankadins have), your SoCs will hit for incredibly large numbers. It’s not uncommon for me to pull 5k+ DPS in heroics whle tanking, and I’m pushing 9k in 25 man raids.

5) Minimal cost to get SoC. While I lose Vindication, this talent isn’t especially needed for heroic/trash tanking.

How did this happen?

First – you can blame dual specs. If we didn’t have the ability to swap between a trash/heroic spec and our progression spec with the click of a button, I highly doubt you’d see this going on as much (though there would be other problems to contend with). Just switching glyphs out would get expensive, and giving up Vindication and Divine Guardian/Sacrifice is a nice hit to survivability.

Second – blame the retadins. SoC was changed to give them the ability to produce adequate DPS on non boss fights, and is really their first ‘interesting’ talent when leveling. You still don’t have any more buttons to push, but at least the numbers are flashier than you get with say, Seal of Righteousness.

Finally – blame arenas and PvP. This spec was born in the blood soaked soil of the arena, in a retadin’s desperate attempt to do good damage, and still have an interrupt of some kind. A clear lack of an interrupt on a decent CD pushed some players in this direction.

OK – so how do we fix it?

This is a lot more challenging (I believe) than say, fixing HotR to only work with 1H weapons. It’s not a spell in and of itself, it’s an ability. While the coded it to specifically not work (SoC) with HotR, I believe it would be a lot more difficult to set it to not proc when using a 1H weapon. While they could shove it down in the ret tree another rung, making it a 21 point talent, they would do so at the risk of hindering ret paladin leveling. Waiting until level 31 for a new damage seal is a long time.

This issue would be fixed (and quite a few others) by using stances, but as someone who played a warrior for many years, stances are aggravating. It’s one thing for an ability to not work as well (say, self healing for a DK), it’s another to be locked out completely. They also have done a great job of keeping the tank classes relatively unique. Bears have forms, Warriors have stances, and DKs have presences. Paladins – well, we have everything I suppose.

What it means in the end

We’re still going to be viable tanks. If anyone shows up to raid tonight and loses their spot over this nerf, well – let’s just say I’ll eat the proverbial hat. Then I’ll kick their raid leader right in the syrup maker.

The tanks classes are fairly well balanced. We have some great AoE tanking and AD. Warriors have interrupts, stuns, and the ability to close distances in a hurry. DKs have, uh, pets? They actually have amazing versatility and CDs, plus the ability to tank in three completely different styles. Druids have amazing HP and armor, great CDs, and the ability to strap a rocket to their ass. That has to be worth something in the end.

We’ll be fine. Even if they do make SoC a 21 point talent.