Why Rogues Do It From Behind

by Jon on April 18th, 2008

The following is a post I made to our guild’s mesage boards as a response to some of our newer players not knowing rule three of melee fight club:

When you fight, you fight from behind.

Figh Club

The following applies to anyone who is doing melee damage on a mob or raid boss: unless you are the tank, you want to be behind the mob when you attack.

Why? Because a mob cannot parry (or block) your attacks when you hit it from behind.

That’s awesome right?

Yes it is and here’s why: besides the obvious benefit of increasing your personal DPS because your attacks are actually connecting, a parried attack will reduce the mob’s swing timer (effectively increasing its attack speed).

An easier way to think of it is that a parry on a mob will result in a counterattack. This counterattack is directed at the mob’s target (which should be the tank in most situations). Now the tank has his own parries to worry about and probably doesn’t want someone else buffing the boss.

An unlucky string of parries from the mob, whether caused by the tank or from other melee DPS, can result in some nasty damage spikes, putting unnecessary stress on your healers and increasing the risk of your tank biting the dust.

But wait there’s more. There are plenty of raid bosses out there that have a cleave attack that hits everyone in their frontal arc. You don’t want to be affected by this but it’s easy to avoid: just hit it from behind*.

*Behind means behind. Make sure you’re not on top of the boss as your attacks can technically pass through the mob and be counted as frontal hits.

The only exception to this method is when fighting dragons (tails hurt, attack the hind legs) or mobs with a knock-back that require special positioning.

1 Comment
  1. Ralph permalink

    Rogues should still attack dragons from the side, not the front :] Usually boss mobs have a huge hit-box, and I can’t think of a time where a rogue would want to be meleeing literally on top of the boss.

Leave a Reply

Note: XHTML is allowed. Your email address will never be published.

Subscribe to this comment feed via RSS