i got a question for you dps..

[FridgePanic]

Cause I ain't leveling ARC to 34 when I want to play BLM, lol.

[JackFross]

Having been on both sides of this issue:

As a tank, you should never have issue with hate. People talk about undergeared this and that - I successfully held against top-of-the line dps in i60 tank gear as a Warrior on Titan HM against full i110 dps without even a remote issue, while keeping Storm's Eye up. With my current Paladin loadout, I hold hate against dps pulling 1000+ in Fractal while in Sword Oath with no issues at all. DPS pulling that high force me to sacrifice the like... 50? maybe 75? dps that go along with using some Rage of Halone combos, but if they're performing that well, I don't care that I drop to 850 instead of pulling 900. If I'm running with dps who are pulling 1400+, I'll just open in Shield Oath, do one (unbuffed) Rage of Halone combo and then swap to Sword. That single combo is always enough to hold hate for the rest of the encounter. This has been with Bards who don't use quelling and other such stuff. WHM is the only class who's ever come REALLY close to pulling off me (heals+dps does stupid aggro), but they had to drop hate for mana regen before they actually pulled.
As a tank, if you're having trouble with aggro, put on more strength accessories. Full VIT is really not ideal. I ran that when I was a fresh 60 in all green gear, running Shield Oath because lol 1500 defense (and still having no problems) but slowly phased out to full strength, Sword Oath as I geared up and reached i190.

As Dragoon, I made myself a macro using the [Please Draw Enmity] auto-translate followed by three irritating sound effects because I'm an asshole. I only pop it when I use Elusive Jump and STILL have hate. Which has happened before. It's a product of tanks grossly underestimating dps and rolling no tank stance + no enmity combos and then having it be FAR too late to rectify it by the time I slam my Full Thrust and see that I'm solidly 3x their hate.


The only time I blame the DPS for pulling hate is when you're pulling trash mobs. If I pull a group of 4-5 and one of my dps pops cooldowns and burns one of them down, I actually say - out loud - "Fuck 'em." and thoroughly ignore it. It's not your job as the tank to hold full single-target enmity on every one of the 5 mobs in the pull. It's their job as a DPS to not be terrible and actually use AoE when the situation calls for it. Every class has it. No class will pull single target threat off Flash, Overpower, or Unleash if they're using it. None.

[ForbiddenMonk]

1) you still had enough time to establish threat.

2) you could have dodged to the side and kept attacking.

3) provoke -> shield lob

shield lob -> provoke....

I don't understand why tanks are starting off there rotation with provoke....all you have to do is get within distance and you have an automatic provoke. Provoke should be save for lost of aggro or pulling distant adds

[JackFross]

shield lob -> provoke....

I don't understand why tanks are starting off there rotation with provoke....all you have to do is get within distance and you have an automatic provoke. Provoke should be save for lost of aggro or pulling distant adds

Malevicton was referring to ways you could fix things in the situation provided by the other poster. If you lose hate, you use Provoke > Shield Lob, not the other way around. They were criticizing the tank for losing aggro due to dodging an aoe. Your post seems to ignore the context of the quote's response.

[ForbiddenMonk]

Malevicton was referring to ways you could fix things in the situation provided by the other poster. If you lose hate, you use Provoke > Shield Lob, not the other way around. They were criticizing the tank for losing aggro due to dodging an aoe. Your post seems to ignore the context of the quote's response.

He lost aggro on opener. Provoke and a shield lob is crap way to re-establish aggro especially if lost in opener. Try that tactic in T10, lose aggro on the pull or lose aggro on wild charge, good luck provoking and shield lobbing your aggro back. Or T11 when tanking sphere and lossing aggro to caster, provoking and shield lobing aggro back from that is reckless. provoke and shield lob is pretty useless if you can't immediately land another enmity skill after.


This is coming from a SCOB(savage) and FCOB progression cleared Pld.

[CookieCakes]

To answer OP's question. Assuming a single boss encounter, if i have to use quelling strikes so the tank could keep aggro on initial pull, the tank isn't do his job properly.

[Aiselia]

To answer OP's question. Assuming a single boss encounter, if i have to use quelling strikes so the tank could keep aggro on initial pull, the tank isn't do his job properly.

If you're not using Quelling Strikes even if you don't need to, you're not doing your job properly either.

[CookieCakes]

If you're not using Quelling Strikes even if you don't need to, you're not doing your job properly either.

There is no reason for me to use quelling strikes if the tank is holding aggro confidently. If I use it randomly just because the cooldown is up, I may not be able to use it when an emergency arises, such as if the tank dies, or an add spawns

[RiceisNice]

If you're not using Quelling Strikes even if you don't need to, you're not doing your job properly either.

There's less circumstances to even need quelling strikes either nowadays; the boss splits with a mirror enmnity list, or add spawns need to be fixated on a dps anyway.

And if there was, you're better off using it for add spawns where they need to die asap as well as the tanks having to take immediate aggro on it.

[Malevicton]

If you're not using Quelling Strikes even if you don't need to, you're not doing your job properly either.

I'll precast it for my opener but past that I won't use it unless I need to. Animation lock is only like .2 seconds or so, which is pretty negligible, but it's a decision between .2 seconds of doing something that has an effect or .2 seconds of doing something that has no effect. Again, it's negligible and I get that, but I'd rather have a negligible gain than a negligible loss.