Post Your Tanking Horror Stories!

[Seipheris]

Thornmarch on Hard.

Our DPS was phoning it in, no focus, no correct order of adds killed.

We wiped to Momento Moogle. As MT, I pointed out that all the Moogles but the WAR needed to die ASAP, while one of the DPS was trolling by saying to leave them all with no health.

Rinse and repeat for 3 attempts before we end it. Had to down the boss with another group, wasn't even hard.

[Ebonwings]

Ok here's another tanking horror which happened last M4 run which made me question my tanking skill...When Brute Justice showed up and did his raid wide aoe, I shield lob him, he still targeted my WHM, I provoked and rage of halone him, he still target WHM ( when I watched my status bar there were medica II and regen on me), did his tank buster to the party. We wiped 3 times to this....I never had any problem with any other WHM before.

Now here's the question, am I a bad tank or is Brute justice aggro on WHM because of the regen and medica II ticked after I provoked him the first time he targeting that WHM? Should I wait for that WHM to use medica 2 and regen after the aoe first before I provoke?

[LDR]

I tanked the entirety of Antitower no problem yesterday.

Don't see how this is a horror story? check my lodestone for which classes I DONT have leveled

[Destous]

Ok here's another tanking horror which happened last M4 run which made me question my tanking skill..

Sounds like the WHM was the problem. Hitting Medica II prior to the tank grabbing an enemy means you have to aggro fight for the mob. Sounds like he landed it after your taunt but before you followed up with an attack. To avoid this, wait a half second after he comes down before doing Taunt + Shield Lob. All the healers are going to be spamming heals during that phase because of the landing damage, and since everyone is already on the hate list, they act as way stronger aggro generators than any tank opener; so let them get the heal off first, then turn their aggro into your aggro with Taunt.

[Februs]

Sounds like the WHM was the problem.

I agree, but I do find it odd that he was unable to grab aggro back after the voke. A voke followed by a enmity move of any kind should be enough to secure enmity off of any other job with the exception of another tank. Not being able to grab it back right away makes me question what went wrong.

My first assumption is that the voke missed, somehow. It sounds crazy, but I have seen it happen before. I've seen it a few times where a Tank throws out a voke that has absolutely no effect at all (not even a wiggle on the boss enmity). I've only seen it a few times, though, so I'm not sure if it's a latency thing or a glitch or what. The other options is what you mentioned: A late AoE heal caused a wrinkle with the enmity ... But I still find it odd that it would generate that much enmity. A full RoH combo should have been enough to secure hate. Without seeing the exact sequence of events, it's difficult to speculate on what exactly might have gone wrong there. Sounds kinda weird to me.

Regardless, it provides for one of those rare instances in which Cover can come in handy until enmity is secured.

[Pells]

Ok here's another tanking horror which happened last M4 run which made me question my tanking skill...When Brute Justice showed up and did his raid wide aoe, I shield lob him, he still targeted my WHM, I provoked and rage of halone him, he still target WHM ( when I watched my status bar there were medica II and regen on me), did his tank buster to the party. We wiped 3 times to this....I never had any problem with any other WHM before.

Now here's the question, am I a bad tank or is Brute justice aggro on WHM because of the regen and medica II ticked after I provoked him the first time he targeting that WHM? Should I wait for that WHM to use medica 2 and regen after the aoe first before I provoke?

Sometimes I find this to be a latency problem. It's more visible in trash pulls, where you lose enmity on a lone mob for a fraction of a second. I'll still hit it with flash/halone/whatever, but it will run alllll the way back to smack the healer (or bard) before running back to me, since I still have enmity on it. It's just in that tiny amount of time I didn't, it decided to hit someone else, and nothing I can do will change that.

Double Rocket Punch comes very soon after the jump, and if your enmity isn't solid by then, there's a small chance it will target someone else with it. And it -will- hit them, regardless of whether you pull it back before it lands, or even if they move out from in front of him. If you wait to provoke, this only makes it even more certain the tank buster won't be targeting you.

The jump really should be shielded before hand, then mass healing held off until things are settled -- the party isn't going to be taking any more damage before the double rockets. There is plenty of time beforehand. WHM should be using Stoneskin2 rather than Medica2. SCH have Adloquium and Deployment. I don't know AST well enough to say about them.

Having both Medica2 and Regen running when BJ appears is equivalent to doing the same during a long pull. The healer is just begging to get smacked. Unfortunately, the next smack is going to kill them. And one other person. The really sly WHMs who do this deliberately will stand next to the other healer when attempting this.

What you can do is Divine Veil and Clemency yourself while he's forming, then move closer to where he lands. Use Tempered Will to avoid the knockback and then go straight into the Halone combo, while punching him with Circle of Scorn and Spirits Within. Fight or Flight if you can fit it in before then. This should give you a better burst enmity lead than Shield Lob alone while running into melee range.

TLDR: It's a healer error. To reduce this risk as a tank, you have to be proactive. If you need to Provoke, it's too late.

[Februs]

Sometimes I find this to be a latency problem. It's more visible in trash pulls, where you lose enmity on a lone mob for a fraction of a second. I'll still hit it with flash/halone/whatever, but it will run alllll the way back to smack the healer (or bard) before running back to me, since I still have enmity on it.

This is definitely a possibility as well, though it's not necessarily a latency issue.

It's kind of hard to explain, but enemy attack rotations work the same way as ours. If they execute an attack on a target, that attack must be finished on that target, regardless of if their enmity changes midway. The way this functions is similar to the temporary target function used on Ps4. On console, if you hard fix a target (not to be confused with lock-on, which is different) and then tap the D-pad onto a new target, your character will generate a temporary targeting reticle on the new target without dropping their hard-fixed target. To hard-fix onto that new target, you have to confirm with the X button; however, if you execute an attack without confirming the new target, the system will execute that attack onto the temporary target before automatically returning your character onto it's first, primary, target. It's a strange little system they probably incorporated to make up for a controller's slower targeting potential (lack of point-and-click).

Monsters work the same way. If you lose aggro on a monster (meaning they are now targeting someone new) and they execute an attack during that time they are registered by the system as executing an attack on a different player. Because of this, even if the tank grabs aggro back before the attack is completed, the monster must complete that attack on it's original target before switching back to the tank. Hence, the mob will run all the way too that target, smack them once, and then run all the way back to you. Monster attacks and auto attacks are fairly infrequent; so it's not something that is too noticeable, but when it does happen it can be annoying, especially if that target is ranged and is pulled outside of your AoE's.

[Noxifer]

WHM should be using Stoneskin2 rather than Medica2.

Mostly I agree. There's really no need to heal anyone right away, since only the tanks are going to be taking damage until after DRP. And sure, healing the tanks, but... I know as OT, I stick to Defiance through the pre-buffing/healing until after Brute Justice lands, and without any healing landing on me after the raidwide, I'm at max HP again when I switch to Deliverance. Meaning I've taken less than 20% of my HP pool in damage. So... yeah, it's not going to be that much of an issue during the first few seconds.

But... Stoneskin2? Mid-combat? O.o What have you been smoking?

[Pells]

Mostly I agree. There's really no need to heal anyone right away, since only the tanks are going to be taking damage until after DRP. And sure, healing the tanks, but... I know as OT, I stick to Defiance through the pre-buffing/healing until after Brute Justice lands, and without any healing landing on me after the raidwide, I'm at max HP again when I switch to Deliverance. Meaning I've taken less than 20% of my HP pool in damage. So... yeah, it's not going to be that much of an issue during the first few seconds.

But... Stoneskin2? Mid-combat? O.o What have you been smoking?

Casting it mid combat isn't a huge problem. Similar to casting Raise mid-combat.
Swiftcast is a thing.

[KeiranOlive]

Casting it mid combat isn't a huge problem. Similar to casting Raise mid-combat.
Swiftcast is a thing.

What he meant was that stoneskin 2 cannot be used during combat. Only the single target stoneskin can be casted mid fight.