Tales from Duty Finder: Some make you laugh, some make you cry. Let's vent.

[Aosha]

I think it was around the time of Sophia that they decided to kinda stop with the permadeaths.
I still remember the good old days of Titan, getting knocked to the bottom of the arena, and just having to stare at the rocks for a few minutes. Good times.

[Aosha]

On another note, I'm finally starting to give up on trying to fight Savage Chaos in party finder. I've now seen all of the following, in supposed "weekly clear" parties (not all in the same party, thank god):

- A party where we had the boss at 33% when he cast the Earthquake in his enrage sequence. On a "good" run.
- A party leader who had written the usual "multiple fails = replace", failing more mechanics than everyone else combined. (expected)
- A summoner, having Ifrit use Flaming Crush (NOT Radiant Shield) before pull, switching to Garuda, using Contagion, and then hardcasting Ifrit back in right after. (why??)
- Healers failing to heal the OFFtank back up during Earthquakes (no hope for the MT, obviously).
- Healers completely neglecting to heal the main tank before an incoming tank buster. For half a health bar's worth of blocked auto attacks.
- A party leader demanding that we do the orb transition phase the "healers/tanks inside" way and then failing to do his part in it several times.
- A red mage in i250-260 gear dying to the unavoidable jump damage in water phase, just by not having enough max HP.
- A summoner (party lead) for whom having Chaos jump from one corner to the opposite during tornado was "too far to run", so I had to tank him near the middle, with one flank in the tornado. Apparently he didn't take into consideration that he's RANGED and can thus hang around wherever he pleases. But no, HAD to have Chaos exactly there.
- A black mage not comprehending "get hit by both implosions" in Earthquake phase.
- A black mage insisting everyone else stack in his Leylines in the enrage water circle part. Leylines which he had plopped down outside melee range...
- And to top it all off, the one time I found a good party where we almost had Chaos (the boss) down, someone apparently downed Chaos (the data center), so half the party got booted out...

[Hestzhyen]

Alphascape 4.0 - had a lovely MCH who died because he ripped aggro from the MT right before Omega-M began to charge up the tank buster. Tank got it back but was too late, MCH bit the dust and crumbled into a pile of salt. They sat there dead on the floor and refused all raises, choosing to whine at the tank for swapping to Sword Oath instead. Even when the SCH used LB3 they purposely ran off the ledge. I know it's frustrating to rip aggro even with using enmity reducers (and to his credit he did use them)... and the tank's gear wasn't that great compared to the MCH's... but there's no need to wail and cry like a spoiled brat because of one death in normal mode. At least they didn't win any of their loot rolls.

On another note, still entirely possible to clear the fight down a DPS and hitting the "enrage" by killing one of the Omega-people early. The SCH and I hardly broke a sweat keeping everyone up through the laser disco until Omega-M was killed. Was kind of surprised at how weak the enrage was honestly, but then again it's NM so maybe I shouldn't be.

[Bright-Flower]

I have a story as well as a bit of a confession. I just went through ex roulette as tank, got arboretum hard.

I ask the group if they want big or small pulls. Neither the dragoon nor ninja answer, but healer says big is fine. So I do big pulls.

We get by just fine but I notice things are taking a while to die, and they're generally dying one at a time. And I don't see any dotons from the ninja. So I assume the ninja is just single targeting instead of aoeing. Maybe I was wrong, maybe the ninja was the one aoeing and just not using doton and the dragoon was single targeting, but I'm pretty sure with the way damage was going out one of them was aoeing and the other wasn't, and I'm guessing the ninja was the culprit since I didn't see any dotons.

This isn't the end of the world. It irks me a bit but not enough to say anything in party chat. So I continue the run and we get to the last boss. I've had groups before where multiple people start hitting the mud pie, and cause it to ping pong around and get hit by the mud aoes and thus hit the group with lots of aoe damage because of this. So instead of immediately pulling, I start to type out in party chat if anyone in particular wants to take mud pie duty. It's not like I was afk for 5 minutes or something. I was simply trying to type out a simple question before pulling the boss, but apparently the ninja was in that much of a hurry despite not saying a thing the entire run.

Before I can finish typing out that simple question the ninja pulls the boss. And at that point, I decided I was done. I let the group die, including myself, tell the ninja to look up what doton is and to not pull bosses, and then I promptly leave the group. I didn't try to kick the ninja or make anyone kick me, I just left and ate the 30 minute timer.

I know that the mature and responsible thing to do would be to just pick up threat on the boss, kill it like normal and finish the run, then say something to the ninja during or after the boss fight. And on most days that's probably what I would have done. But for some reason, the ninja pulling the boss like that without even asking why I hadn't pulled yet or waiting for me to finish typing my question, I just decided I was done. Didn't care if the nice or pragmatic thing was to finish the dungeon and leave. Another tank can come in and get a fast roulette filling the gap. I can get another instant tank queue tomorrow to finish off my weekly tomes. But I was tired and frustrated and just decided **** it.

Ultimately, the lack of aoe wasn't really what what made me mad. I don't always play perfectly. I probably made mistakes in that run even. That was just a minor thing, and the impatient pulling of the boss set me off.

[van_arn]

I have a story as well as a bit of a confession. I just went through ex roulette as tank, got arboretum hard.

I ask the group if they want big or small pulls. Neither the dragoon nor ninja answer, but healer says big is fine. So I do big pulls.

We get by just fine but I notice things are taking a while to die, and they're generally dying one at a time. And I don't see any dotons from the ninja. So I assume the ninja is just single targeting instead of aoeing. Maybe I was wrong, maybe the ninja was the one aoeing and just not using doton and the dragoon was single targeting, but I'm pretty sure with the way damage was going out one of them was aoeing and the other wasn't, and I'm guessing the ninja was the culprit since I didn't see any dotons.

This isn't the end of the world. It irks me a bit but not enough to say anything in party chat. So I continue the run and we get to the last boss. I've had groups before where multiple people start hitting the mud pie, and cause it to ping pong around and get hit by the mud aoes and thus hit the group with lots of aoe damage because of this. So instead of immediately pulling, I start to type out in party chat if anyone in particular wants to take mud pie duty. It's not like I was afk for 5 minutes or something. I was simply trying to type out a simple question before pulling the boss, but apparently the ninja was in that much of a hurry despite not saying a thing the entire run.

Before I can finish typing out that simple question the ninja pulls the boss. And at that point, I decided I was done. I let the group die, including myself, tell the ninja to look up what doton is and to not pull bosses, and then I promptly leave the group. I didn't try to kick the ninja or make anyone kick me, I just left and ate the 30 minute timer.

I know that the mature and responsible thing to do would be to just pick up threat on the boss, kill it like normal and finish the run, then say something to the ninja during or after the boss fight. And on most days that's probably what I would have done. But for some reason, the ninja pulling the boss like that without even asking why I hadn't pulled yet or waiting for me to finish typing my question, I just decided I was done. Didn't care if the nice or pragmatic thing was to finish the dungeon and leave. Another tank can come in and get a fast roulette filling the gap. I can get another instant tank queue tomorrow to finish off my weekly tomes. But I was tired and frustrated and just decided **** it.

Ultimately, the lack of aoe wasn't really what what made me mad. I don't always play perfectly. I probably made mistakes in that run even. That was just a minor thing, and the impatient pulling of the boss set me off.

Don't ever finish a run you don't want to finish. You did the right thing bailing, since you didn't want to kick.

[MarniDawg]

- A summoner, having Ifrit use Flaming Crush (NOT Radiant Shield) before pull, switching to Garuda, using Contagion, and then hardcasting Ifrit back in right after. (why??)

This is so that garuda's skill is on cooldown and she will immediately cast contagion then you can swap back to ifrit for more damage. But they definitely shouldn't be hard casting ifrit.

[Berteaux_Braumegain]

Just got kicked from a party for not Verraising someone.

On Ravana normal mode.

For someone who got a ring out.

Um......

Amazing.

How do you even fall off on that? It's way more forgiving than Titan.

[dragonseth07]

We just had to vote abandon O11N. Neither healer could figure out how to survive, at all. The Larboard/Starboard always claimed at least one Healer, the other often dying shortly thereafter. Meteor circles were a shit show, often not possible because people were dead when they showed up. The giant fists on the outside were invisible to half the raid, only half of us could apparently see them coming.

I ended up fucking up a Mustard Bomb because I got distracted trying to help keep everything else afloat with Clemency and Cover. It was just awful.

We tried explaining stuff, but there was no learning going on. It was abysmal.

[TheMightyMollusk]

Amazing.

How do you even fall off on that? It's way more forgiving than Titan.

Ravana does have a knockback attack that can throw you off if you're not paying attention when the walls crumble after Bloody Fuller.

[Zeich]

Ran O11 last night on DRK, partnered with a WAR. He's in Deliverance, and I like main tanking, so y'know, works out well, right? Ahahaha no.

First 10% of the fight goes well, then out of nowhere the WAR provokes, still in Deliverance. I'm like "Uh..." okay, I'm in tank stance, I got this. I'll just pull hate back--oh wait, there goes Omega wiggling away, I have to dodge a move, WAR continues to build hate and eats the hit. So I'm busy trying to pull hate back, and Omega keeps wiggling back and forth and turning, Starboard/Larboard are in weird spots, and eventually due to all of this I died. Honestly, I should have just said "okay, he wants to tank, I'll shirk and OT." But I died, so whatever, my hate's reset, it's all his.

First thing I see when I get back up is that he's barely ahead on the hate list above one of the DPS, so I'm like "okay, I got this!" Drop Grit now that I'm acting as OT, do Provoke + Shirk to bump the MT up a good chunk. Immediately after I Shirk, he Shirks me back. Suddenly I'm MT at about 1/2 of my health, not in tank stance. I fumble my buttons instead of putting up The Darkest Night as a Mustard Bomb goes off, bam, I'm on the floor again. I get back up, we move on with the fight, slowly making progress. We made it past the DPS check before my second death, so all's well, I guess, it's just the grind down to the end. Once more, now that I'm double-weakened, I'm like "okay, he'll surely hold hate this time." Just in case, have a Provoke+Shirk - I try and be thoughtful as an OT since he's maintaining Deliverance instead of swapping to Defiance, so that way he doesn't have to swap. Nope! Moment I hit Shirk, he Shirks me back, and again I'm not in Grit, so ow. Managed to keep alive this time, but he kept ping-ponging hate the rest of the fight with random Provokes.

At least we cleared but uuuuuuugh. That was a headache.