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

[Aeloria]

Alright here goes. I've been playing on an alt working on story the past couple of days. It has gone pretty well except for a couple of things I had to run today. The first incident I guess that really stood out to me as wow what is going on was during final steps of faith. The Scholar used the one ability I think emergency tactics? That doubles the heal instead of providing shield on cooldown regardless of current HP. Like everyone would be at full health and pop off a double heal succor. Ugh. This i could have overlooked cause whatever, but what happened later in the find was just mind numbing. I died twice because I would stack for ahk morn(sp) and suddenly mister emergency tactics or the AST didn't know where their heal buttons were. Not to mention only 3 or 4 people would stack. The last round of the ability no one stacked which as you can imagine killed me and proceeded to kill a few others. The only reason we didn't wipe was because of the 2 tanks knowing how to play their job. The tank from gilgamesh did not disappoint was a bit snarky about people not stacking, I don't normally like snark but this guy earned the right to be snarky. (Side note: Why is almost every Gilgamesh person I run into snarky? Seems so common.)

Second thing today was I was running Xelphatol, which after waiting for 25min for my queue to pop I knew regardless I was going to stick it out. I get loaded in and sprout LANCER, I just knew we were in for a rough ride. Dungeon took nearly 30min. The tank mentioned something to the lancer first, but the due gave no response. The healer said something next after the first boss took forever and a day. I said something that their job stone is in the bottom slot on accessory and that they need to equip it because it will increase their dps, granted im sure their bar's would be screwed. They responded this time and just said "Cant xD" So I guess question here is was the person locked to lancer because they were already in duty? The healer took it to mean they didn't have a job crystal and said that they need to do their class/job quests. This is the first time I ran into this tbh. Anyway it was a long run. They didn't know what a stack marker was BUT after they ran from us trying to stack on them I told them what it was and while they never responded they did start stacking. So I guess that was a win? Well anyway. I really wish SE would find a way to retcon some job lore and just do away with the classes so everyone starts as their job from lvl 1 and would alleviate this issue completely..

Thanks or listening. I just needed to let it go I'm a pretty chill guy most of the time and I didn't say 90% of the things I was thinking but ya today my patience was tried

[Seraph522]

Second thing today was I was running Xelphatol, which after waiting for 25min for my queue to pop I knew regardless I was going to stick it out. I get loaded in and sprout LANCER, I just knew we were in for a rough ride. Dungeon took nearly 30min. The tank mentioned something to the lancer first, but the due gave no response. The healer said something next after the first boss took forever and a day. I said something that their job stone is in the bottom slot on accessory and that they need to equip it because it will increase their dps, granted im sure their bar's would be screwed. They responded this time and just said "Cant xD" So I guess question here is was the person locked to lancer because they were already in duty? The healer took it to mean they didn't have a job crystal and said that they need to do their class/job quests.

Yeah, you can't equip job crystals while you're in an instance (dungeon, trial, raid, etc.). It's to keep people from queuing up as tanks/healers and then swapping or other troll-ish actions. Of course, this is a problem when someone queues up as a class instead of a job in above-30 content. They really should just lock you out of level 30+ content if you don't have a job crystal equipped. In your case, I would have just kicked the lancer, maybe after explaining why; the guy seemed to at least be paying attention and not deliberately trolling or something (maybe... always hard to tell), but being in a class in Xelphatol is just going to give everyone headaches.

[CodingSession]

Second thing today was I was running Xelphatol, which after waiting for 25min for my queue to pop I knew regardless I was going to stick it out. I get loaded in and sprout LANCER, I just knew we were in for a rough ride.

A few days ago, I got grouped with a PGL in Brayflox. His reasoning was he's leveling too fast he didn't have time to do the job quest. I don't know how to respond to that, so I didn't say anything for the rest of the dungeon. Granted, the run went without incident, if a bit slow.

I hope this doesn't become a new trend. Too lazy to get your gear up-to-date is bad enough, too lazy to complete the job quest is a whole another level of laziness.

[Iscah]

[Amdapor Keep], nothing intresting happens.
...until we kill the demon wall and proceed to find our way to the last boss totally mob-free. No succubi, no ahriman, no dulhans patrolling... nothing.
And I have no idea why. Did they nerf the dungeon again by removing not only the bees but also a third of the trash-mobs? Can anyone enlighten me?

That sounds like a glitch. There should definitely still be enemies patrolling the upper floors.

I said something that their job stone is in the bottom slot on accessory and that they need to equip it because it will increase their dps, granted im sure their bar's would be screwed. They responded this time and just said "Cant xD" So I guess question here is was the person locked to lancer because they were already in duty?

The simplest answer is that the game doesn't see lancer and dragoon as the same class, and you're not allowed to change class within a dungeon.

A few days ago, I got grouped with a PGL in Brayflox. His reasoning was he's leveling too fast he didn't have time to do the job quest. I don't know how to respond to that, so I didn't say anything for the rest of the dungeon. Granted, the run went without incident, if a bit slow.

I hope this doesn't become a new trend. Too lazy to get your gear up-to-date is bad enough, too lazy to complete the job quest is a whole another level of laziness.

While it's not ideal, I don't think it's that much of a sign that someone is "lazy" just because they haven't done a Lv30 sidequest by the time they get to a Lv32 MSQ dungeon.

[Kallistra]

First story is actually from earlier this week, on Wednesday. I don't get home until really late on Tuesdays and Thursdays so I run the 24man on Wednesday for my token and loot so I don't have to worry about it over the weekend. So I'm running it with my fiancee and one of our FC members and Selli disconnects right after we wipe on Cid. Selli's ISP is pretty garbage so this is really normal (she usually disconnects about 3-4 times a day), but because this happens right after a wipe it just looks really bad and intentional.

Thankfully the party was really understanding and didn't vote dismiss her even though she was gone for almost 15 minutes. I think we wiped while she was gone and a third time after she came back before we cleared? I know there was at least two wipes, but I'm not sure if there was a third. Either way, I'm glad the pugs didn't boot her and everyone in our little premade got their loot for the week.

Now I am going to completely ruin this happy narrative with my second story. Buckle up.

Second story is from last night. I decided to do Alliance Raid Roulette by myself and boy was that a mistake. I queue in and get Dun Scaith, I had gotten Dun literally the day before so I wasn't overly thrilled, but my WAR is almost 70 and I want the EXP. One of the other tanks is MTing when they go down to the first mechanic on the first boss. His draw in sometimes gets me by surprise still so I don't think much of it, I voke the boss off a DPS, pop Defiance, and do a couple BB combos. By now then the old MT is up, so I let him take the boss back and go back to Fell Cleaving. A few mechanics later and he is dead again, so I once again voke the boss, pop Defiance, do a couple BB combos, let old MT have it back when he's ressed and healed.

Fight ends and as we're making our way to the trash pack afterward, the MT is very angrily speaking to me in Alliance chat, "Kallistra, I'm the main tank, so back off." I point out, "I was picking the boss up after you died so it didn't murder our DPS or healers. I have no issues with you MTing." They don't say anything else so I assume it's over and done with.

But how so very wrong I was. It is very much not over and done with.

We get to the second boss and MT manages to die again. So I voke the boss, pop Defiance, do a couple BB combos, and wait for the MT to grab it back... except he's not taking it back, he's still on the floor and freaking out in Alliance chat. "You guys are intentionally getting me killed because you want this stupid WAR to main tank even though I called main tank" just some straight up paranoid conspiracy theory nonsense.

But now I notice that my health is getting dangerously low. I've been popping my cooldowns, avoiding the AoEs that can be avoided and I'm watching the healers DPS. When I hit sub 20% I pop Holmgang, I still don't get a single heal and die. As soon as I go down the old MT gets up, doesn't wait for any heals, and vokes the boss which causes him to die instantly again anyway. The third tank doesn't bother to pick up the boss, but Mr. MT waits for a heal after his second raise before voking this time. And I spend the rest of the fight on the floor. None of my healers raise me and none of the other Alliance healers notice. I don't return until after someone uses LB3 so we don't lose it (and by then the boss is sub 10%), then I sit outside to avoid the weakness debuff.

On our way to the next set of trash, MT is talking trash saying things like, "I don't know why you think you can main tank when you spent the whole fight on the floor" and "you think you're tough s***t because you're Gilgamesh elitist trash" and "did you even know the mechanics of the fight? Omegalul". I really don't care about this guy's opinion so I don't say anything. I know I didn't do anything wrong and if he's not going to listen then I'm not going to try to justify myself to him.

Now we're on Scathach. Again, the MT goes down fairly early and again I pick up the boss. Scathach hits a little harder than the last few so she actually one-shots the WHM who took aggro but no one else. Again the old MT is throwing a fit in Alliance chat and again I notice I'm not getting any heals and die. Scathach chews through about 2-3 people before old MT is up and vokes. Again, I get no raises. We manage to get to the point in the fight where the add comes down and the third tank doesn't pick it up (unless the MT voked it? He might have and I just missed it). Either way, the add get too close and the raid wipes.

I tell my healers that if they raise me I can pick up the add and that when the MT goes down I pick up the boss and heals would be appreciated. One of them tells me to, "stop being elitist" and the other says, "we weren't healing you on purpose because of how you've been treating that other tank".

HOW I'VE BEEN TREATING THAT OTHER TANK!? You mean by covering his a** when he dies, letting him take the boss back, and not responding to his aggressive comments? Yet I'M the one in the wrong here??

Fine. Whatever. We're on the second last boss, the raid is almost done. I really don't want to argue and I really don't want to get kicked so I just respond to my healers with, "Sorry".

We try the fight again, the MT goes down, and this time I DON'T pick up the boss. I watch Scathach chew through about 3-4 people before the MT is up and gets her back. Two of the people Scathach chewed through where the MT's healers, so he is down basically as soon as he gets back up. So, once again, I pop Defiance, voke the boss, do a couple BB combos, and wait. No heals. I die. The raid wipes.

MT has dissolved into nothing but caps lock and swearing at this point. I'm frustrated and I don't know what to do. The third tank is probably too scared to try and help. I really don't want us to wipe, so I'm really just trying to help. Now the DPS who have been pretty silent about the issue start to back up the healers, saying that the wipes have been my fault and that if I just stopped trying to massage my "raider ego" this could have all been avoided.

Not long after that I'm vote dismissed. RIP EXP. RIP patience. I am d o n e. Is it petty of me to say that I hope they didn't clear the raid after all that? Because I kind of hope that they didn't.

[Bonbori]

I really wish SE would find a way to retcon some job lore and just do away with the classes so everyone starts as their job from lvl 1 and would alleviate this issue completely..

I feel there is a simpler solution. They could just add a job stone requirement to all content above lvl 30 in DF. There are no jobs that don't get a job stone by level 30 and jobs added after AAR can't even unequip it.

They were able to specifically exclude BLU from DF so SE has no excuse for allowing classes to enter matchmaking for duties exceeding their maximum level. Party finder? Whatevs, anything goes, but DF should be restricted.

[linay]

I feel there is a simpler solution. They could just add a job stone requirement to all content above lvl 30 in DF. There are no jobs that don't get a job stone by level 30 and jobs added after AAR can't even unequip it.

They were able to specifically exclude BLU from DF so SE has no excuse for allowing classes to enter matchmaking for duties exceeding their maximum level. Party finder? Whatevs, anything goes, but DF should be restricted.

They won't do that for one simple reason: leveling and/or guildhest roulettes. If they restrict you from entering duty based on equipping job stone, people can just unequip job stone to limit themselves to just getting the lower level dungeons/guildhests.

[Seraphor]

They won't do that for one simple reason: leveling and/or guildhest roulettes. If they restrict you from entering duty based on equipping job stone, people can just unequip job stone to limit themselves to just getting the lower level dungeons/guildhests.

But leveling roulette only exists to get people to play the lower level dungeons...
Who in the right mind would rather get Sastasha than say... Snowcloak?

If anything, this would be a bonus for those trying to do low level content, with those few nutjobs who are unequipping their stones helping out the longer queues for sastasha and halatali.

[KaivaC]

Dun Scaith nightmares

Pardon my language...

...actually, no, forget that, it seems you what you ran into were a large bunch of jackasses. The main tank is an idiot. If you keep dying to mechanics like that WITH heals, then you have no right to talk about anything. If the healers were so idiotic that they did not notice that the main tank had died, and then acted petty because they thought you were intentionally snatching aggro (even though you were letting the MT take his precious little aggro back after death), then those healers are idiots. I love how even in Alliance raids, doing the sensible thing like being the tank to take aggro after the main tank dies is somehow 'raider ego'. Ignore those idiots and blacklist them.

[Iscah]

But leveling roulette only exists to get people to play the lower level dungeons...
Who in the right mind would rather get Sastasha than say... Snowcloak?

If anything, this would be a bonus for those trying to do low level content, with those few nutjobs who are unequipping their stones helping out the longer queues for sastasha and halatali.

It's not about Snowcloak, it's about Aurum Vale.

Also, people are lazy.


Also also, the game's spaghetti coding probably can't handle such a prospect.