Don't be "that DPS"

[Syzygian]

As a tank, this isn't what bothers me. If I lose a mob, I'll get it back, its whatever. However...

What bothers me is more along the lines of this scenario:

After all the shit in the OP's post happens, I voke+Unmend the mob, y'know, like ya do. This always starts with me doing a big AoE pull and the DPS in question decides to cherry pick 1 out of 10 mobs to be their BFF of Eternal Fucking Bonding.

The DPS, invariably a ranged DPS (like, literally always) doesn't move, just sits there like a SACK OF LEAD, and continues hitting the same mob.

I know the expectation is that the tank will about face and run his ass over there to melee it off the squishy little caster/brd/ whatever, in the process turning his back to the 10 other things he's tanking (no parrying/blocking) and throwing everything else out of positional range for the melee DPS/possibly cleaving them or healer. All the other mobs get pulled out of Flaming Arrow/Doton/Shadow Flare/Salted Earth. All the while fucking up EVERYBODY else's DPS, hurting the tank's mitigation, fucking up positioning, wasting my MP or TP (ranged tank abilities are not cheap), all so you could... whatever.

If you see voke+Unmend/Tomahawk/Shield Lob, STOP HITTING THAT SAME MOB, and if you're going to insist on fucking up the pull like that, at least run it over to the tank's melee range. I'm not going to OOM spamming Unmend to try and rip that thing off you only to have you make snarky comments about me "not doing my job".

Mmmm. Makes me seethe. Don't be THAT DPS.

[AniCelestine]

in the process turning his back to the 10 other things he's tanking (no parrying/blocking)

As far as I know you still block and parry even if the things hitting you are at your back, only exception being while under the effect of Raw Intuition CD by warrior.

But in the scenario you had just let that dps die and tell him he wasn't doing his job, you're meant to work as a team not against each other, this scenario is also one of the reasons I refuse to tank anything with random people

[ruskie]

As far as I know you still block and parry even if the things hitting you are at your back, only exception being while under the effect of Raw Intuition CD by warrior.

But in the scenario you had just let that dps die and tell him he wasn't doing his job, you're meant to work as a team not against each other, this scenario is also one of the reasons I refuse to tank anything with random people

Nope parry and block are only frontal.

[AniCelestine]

Nope parry and block are only frontal.

Guess they have changed it then, we tested that for some progression in 2.1 I think it was and our pld was blocking while back turned to the boss

[Jim_Berry]

Nope parry and block are only frontal.

Guess they have changed it then, we tested that for some progression in 2.1 I think it was and our pld was blocking while back turned to the boss

I can say this...

When I'm pulling mobs, I get hit. BUT....

There's that one mob that hits me from behind during the pull while I'm running. This mob makes my character's head look in its' direction. That particular mob causes my PLD to Block to Parry.

[FunkyBunch]

As a tank, this isn't what bothers me. If I lose a mob, I'll get it back, its whatever. However...

What bothers me is more along the lines of this scenario:

After all the shit in the OP's post happens, I voke+Unmend the mob, y'know, like ya do. This always starts with me doing a big AoE pull and the DPS in question decides to cherry pick 1 out of 10 mobs to be their BFF of Eternal Fucking Bonding.

The DPS, invariably a ranged DPS (like, literally always) doesn't move, just sits there like a SACK OF LEAD, and continues hitting the same mob.

I know the expectation is that the tank will about face and run his ass over there to melee it off the squishy little caster/brd/ whatever, in the process turning his back to the 10 other things he's tanking (no parrying/blocking)

*snip*
make snarky comments about me "not doing my job".

Mmmm. Makes me seethe. Don't be THAT DPS.

Maybe don't lose the mob in the first place? I always AoE with 3+ mobs and sometimes tanks will ignore the fact that they have to control hate on all the mobs. On the second or third flare I'll routinely rib a mob or 3 away. I used to switch to single target damage and switch targets when I noticed an enemy go orange, but I stopped because I'm really just enabling a bad tank.

The problem is tanks will be in DPS stance and then get mad when mobs are ripped away from them. I do more DPS doing AoE than you do extra in DPS stance. Please don't let me rip mobs from you because you want to increase your DPS a little bit. Further the whole group dies faster if you don't try and burst mobs down one at a time. Every mob that dies early is 2.2k F2 damage that is lost or 2.5k+ of Flare damage that is lost (about 600 DPS loss per dead mob). Granted this is melee DPS problem as well.

Further, if I rip a mob away from you, if it's only one, it's probably fine to let me handle it. Manaward/Manawall and single target burst I can handle myself until the rest of the mobs are dead and the group can attack the mob attacking me.

[Syzygian]

snip

This happens before the pull has settled. I AoE like a madman. The problem occurs when I have pulled 6-10 targets and somebody picks ONE and goes ham on it while I'm still running. I'm sorry but i'm not going to spam Unmend to keep that one mob from somebody's single target dps when I'm trying to give everyone a nice clean speedrun aoe pull.

But sure blame the tank.


I just realized we're on the same server. Talk is cheap. Hit me up sometime for a roulette and I'll take you for a ride >:]

[FunkyBunch]

*Snip*

I just realized we're on the same server. Talk is cheap. Hit me up sometime for a roulette and I'll take you for a ride >:]

Hey I'll gladly take a Roulette ride. Tank Queues are amazing.

I was more specifically talking about the tank who focuses down one mob and may even rank each mob for order to die.
If someone is a dork and single target focuses a mob, they deserve to die if they grab aggro. It's also probably not worth it to grab hate back from that player as most classes can take one mob long enough for the group of mobs to die if 'Voke and Tomahawk/shield lob don't grab the mob back.
I also said it's also a melee DPS problem not just a tank problem. Proper target rotation is needed.

It's really disheartening to see a mob die when the group is focusing one mob and the other 6 mobs are at half health due solely to my AoE.
If I rip hate away when I'm doing AoE after the pull has solidified, that's when I SMH.

[Februs]

This happens before the pull has settled.

I can sympathize with this, even if just from more of any annoyance stand point. Dps can go AoE crazy or focus down targets all they want when I'm stopped and running my own rotation, but it's a different story if I haven't finished the pull yet.

It can happen when a tank is approaching a pull with 2 or more sets. 9 times out of 10, this usually goes just fine, because most Dps are considerate enough to wait for the Tank to actually complete their pull before they start the heavy metal music. Unfortunately, sometimes you run into this one Dps who insists on going balls to the walls on the first target you touched before everything is in position. Instead of a nice, clean, efficient, and fast pull, you end up with the tank running to the next set, the mob chasing the tank, and "that dps" chasing the mob while they desperately try to upkeep their dps (which they typically fail at). If they pull hate, then the Tank has to turn the whole train around just to go backwards to save the squishy idiot who couldn't wait 2 seconds for you to settle everything into a nice orderly pile.

The absolute worst cases of this are when the Dps in question stuns the mob you touched. You end up getting to the end of the pull, got everyone nice and lined up, and you're about to pop CoS .... and then you see that one mob way back in the distance who's still trying to catch up with the group cuz someone stunned him.

Why do they do this? I dunno. It doesn't increase dps (it actually lowers it since it's unlikely they'll score positoinals or AoE's on a moving set of mobs), it doesn't work for the other dps (since mobs that are out of place get missed for AoE's), it hurt's the healers Mp pool (since a longer, less efficient, pull = more healing required), and reduces Tank enmity and mitigation (for the same reason that the healer's mp pool suffers).

Thankfully, this is a rare flower in the garden of Dps players. I get players who apply DoT's and get the odd hit off on in-progress pulls all the time, but that special snowflake who thinks that it's a good idea to go throttle to the max before the tank has stopped moving is not as common. It's just a little irritating when you see that kind of short-sighted behavior, and not just to the tank (I've seen a smn bitch at a Mnk who did this, because their AoE's were consistently missing the targets he was pulling out of the group).

[Syzygian]

.... and then you see that one mob way back in the distance who's still trying to catch up with the group

Oh god. The worst, most frustrating thing ever.

And here I am with this work of art, this beautiful stained-glass-window of a pull just waiting to be gloriously AoE'd to holy-mother-of-hell-and-back-again, and now I've gotta step over it, shattering it, to babysit a childish, impatient DPS.

There's a special place in hell for people that rob a DRK of his Sea Urchin spam like that.