A party member has withdrawn. Finding new members.

This has been happening with increasing frequency for me. I queue up in the DF, a party is formed, then someone withdrawals. Not just once, but over and over and over again. Once for a wp run yesterday it happened 35 times in 3 minutes. In that case it was the tank. I can only assume it was the same person doing it repeatedly. But what I'm
Curious about is why?

If this only happened once I would write that tank off as being an ass. But it's been happening a lot in the last few days.

Has anyone else experienced this? Or have any clue what the benefit to withdrawing repeatedly gives?

They're fishing for runs that are almost done where the tank ditched, so they don't have to do the whole instance for Myth Tomes.

Not me, I'd usually rather join a fresh run. If the [my role] ditched, there's probably a reason and only a 33% (it was either a dps, the tank, or the healer) chance the cause was my predecessor. WP 1/3 could mean a giant tonberry gibbed them (it happens) or it could mean the group doesn't have the intelligence to down the second boss. I'm a relic tank, I do some dps, but not likely enough to kill the adds if the group couldn't.

Quote:

---

Originally Posted by RyuujinZERO

Or perhaps it's nobody's fault, and your predecessor was simply victim of an internet outage? - In about half the runs where we lose a party member, it's due to the dreaded 90k, not due to any kind've failing on the team's part (The other half is usually the tank ragequitting in the first 5 minutes because the rest of the team isn't full allagan/psychic/perfect)

GG for continuing to hold up my suspicion that most tanks are elitist jerks who instantly assume everyone else are morons.

---

Wait, what? I'm one of the tanks that queues and takes what pops. I don't bottleneck you guys with repeatedly canceling and I'm an elitist jerk? I really think you need to reconsider your perspective.

I also didn't nail it to just tanks, I play healers too, and most times when I join a group in progress on healer (I don't mind doing it on a tank, I hate doing it on a healer), I find out the tank can't . . . tank or he's level 50 and hasn't figured out the benefit of marking one target, and even if he's spamming flash.

Thanks for the prompt reply. You must be right as that makes perfect sense.

It's still pretty damn aggravating when it happens!

It's worse early in the week when people just want to cap myth, and less frequent towards the weekend when they are capped and actually want philo.

Quote:

---

Originally Posted by Steeled

Not me, I'd usually rather join a fresh run. If the [my role] ditched, there's probably a reason and only a 33% (it was either a dps, the tank, or the healer) chance the cause was my predecessor. WP 1/3 could mean a giant tonberry gibbed them (it happens) or it could mean the group doesn't have the intelligence to down the second boss. I'm a relic tank, I do some dps, but not likely enough to kill the adds if the group couldn't.

---

Or perhaps it's nobody's fault, and your predecessor was simply victim of an internet outage? - In about half the runs where we lose a party member, it's due to the dreaded 90k, not due to any kind've failing on the team's part (The other half is usually the tank ragequitting in the first 5 minutes because the rest of the team isn't full allagan/psychic/perfect)

GG for continuing to hold up my suspicion that most tanks are elitist jerks who instantly assume everyone else are morons.

Yeah, it's people that want to only do a third of the dungeon for full mythology points. And let's face it, by people, I mean tanks.

It is so aggravating waiting for DF to pop only to watch the same tank withdraw every 10 seconds until he gets bored, deigns to grace us with his attendance or gets his 2/3 AK, it's like they don't realise they are dicking other people around. Or don't care.

This is sooooooooooooooooooooooooooooooooo annoying. Happens almost every time I queue now, for a good 5 mins or longer

Quote:

---

Originally Posted by Steeled

Wait, what? I'm one of the tanks that queues and takes what pops. I don't bottleneck you guys with repeatedly canceling and I'm an elitist jerk? I really think you need to reconsider your perspective.

I also didn't nail it to just tanks, I play healers too, and most times when I join a group in progress on healer (I don't mind doing it on a tank, I hate doing it on a healer), I find out the tank can't . . . tank or he's level 50 and hasn't figured out the benefit of marking one target, and even if he's spamming flash.

---

Ignore RyuujinZERO. This person is extremely toxic to tanks on these forums and seems ignorant that tanks see the same behavior from healers when using the DF. It's not all tanks that do this nor healers. Damage dealers would be guilty of it as well if they didn't suffer queue times.

There was a dev post in the JP forums saying they know there's a problem with the DF that it sometimes withdraws the party even while nobody withdrew. I forgot when they say they will patch it, but they know about the problem and are working on it.

Quote:

---

Originally Posted by RyuujinZERO

Or perhaps it's nobody's fault, and your predecessor was simply victim of an internet outage? - In about half the runs where we lose a party member, it's due to the dreaded 90k, not due to any kind've failing on the team's part (The other half is usually the tank ragequitting in the first 5 minutes because the rest of the team isn't full allagan/psychic/perfect)

GG for continuing to hold up my suspicion that most tanks are elitist jerks who instantly assume everyone else are morons.

---

I think you're misunderstanding.. the OP is talking about before the dungeon even starts, not people who leave during the dungeon. I've experienced this a few times on scholar too, the instance que pops up for a few seconds and then the tank drops and it displays the message in the title of this thread. One night it happened to me over 20 times in a row over the course of 5-10 minutes.

Simple solution, declining the queue should put you on a 3 or 5 minute "can't queue". There are legit reasons a person must decline right now, but 3 or 5 minutes barely hurts anything.

Quote:

---

Originally Posted by DoctorPepper

I think you're misunderstanding.. the OP is talking about before the dungeon even starts, not people who leave during the dungeon. I've experienced this a few times on scholar too, the instance que pops up for a few seconds and then the tank drops and it displays the message in the title of this thread. One night it happened to me over 20 times in a row over the course of 5-10 minutes.

---

He was talking to me, not the OP, because I stated that I prefer a fresh run. I'll take what pops, if an in-progress pops, I go, but I prefer a fresh run.

Somehow, I'm the elitist jerk.

Tanks in AK have been doing it for a while, join up rush to first boss then dip out. I have had several lately..shrug

As a Tank that always does full runs because I only go in with my hubby. It happens to me to. So Healer or DPS doing it to.

Quote:

---

Originally Posted by Zfz

There was a dev post in the JP forums saying they know there's a problem with the DF that it sometimes withdraws the party even while nobody withdrew. I forgot when they say they will patch it, but they know about the problem and are working on it.

---

I've had this happen many times while waiting for a queue and someone starts spamming withdrawal.

After a while, it stops happening so I'll check my queue because the window just stops popping up and suddenly I'm in a new queue.

As in, if I'm on WHM, It'll be 0/1[T] 1/1[H] 0/2[DD].

I was wondering if it was a glitch or if it's just something that happens after someone withdrawals a certain number of times.

I'm glad to know that they are looking into it though because it's really not fair to be stuck back at the end of the queue because someone else is being stupid.

Make the final reward based on the amount of bosses you have defeated.

3 Bosses killed: 40 Tomes.
2 Bosses killed: 20 Tomes.
1 Boss killed: 10 Tomes.

And the tomes will be granted only if you kill the final boss (as it is right now).

Problem solved.

Quote:

---

Originally Posted by Odd

This has been happening with increasing frequency for me. I queue up in the DF, a party is formed, then someone withdrawals. Not just once, but over and over and over again. Once for a wp run yesterday it happened 35 times in 3 minutes. In that case it was the tank. I can only assume it was the same person doing it repeatedly. But what I'm
Curious about is why?

If this only happened once I would write that tank off as being an ass. But it's been happening a lot in the last few days.

Has anyone else experienced this? Or have any clue what the benefit to withdrawing repeatedly gives?

---

your relief coming 2.1......................................................................

By far the easiest solution that helps the most people, make those that queue for in progress runs only get in progress runs.

Quote:

---

Originally Posted by Besbeset

Make the final reward based on the amount of bosses you have defeated.

3 Bosses killed: 40 Tomes.
2 Bosses killed: 20 Tomes.
1 Boss killed: 10 Tomes.

And the tomes will be granted only if you kill the final boss (as it is right now).

Problem solved.

---

Yay, then when a tank dc's or is bad and leave you will NEVER get a rep.

Yeah... people who choose to join in-progress duties to help people who lost a member should be punished.

As someone else mentioned earlier, there was a known bug about this and it was stated that a fix is coming from SE. Queuing as a dps I've noticed a different annoyance while leveling in dungeons. When I've clicked the "in progress" box I will often get sent to a group that just has me and another dps (I guess cause the finding new members thing doesn't find all of the members before teleporting them in.. just does it as it gets them). I've even got a dungeon pop where I entered the instance and I was the only one there (presumably the last person left right after I clicked accept).

Quote:

---

Originally Posted by Tule

Yay, then when a tank dc's or is bad and leave you will NEVER get a rep.

---

Correct me If I'm wrong, but are you actually earning any tokens if you don't finish the instance?

Quote:

---

Originally Posted by Zfz

There was a dev post in the JP forums saying they know there's a problem with the DF that it sometimes withdraws the party even while nobody withdrew. I forgot when they say they will patch it, but they know about the problem and are working on it.

---

And there was a post on the english forums. That had a Dev recognizing there was a problem of people withdrawing on endgame dungeons repeatedly, because they are trying to join a partially completed run. And that the new Duty Finder that comes with the 2.1 update, that it would no longer be possible to do. And that they weren't going to punish anybody who did, because there is a chance its not the players fault, and there is no way for them to know if it is,

Quote:

---

Originally Posted by Evangela

Yeah... people who choose to join in-progress duties to help people who lost a member should be punished.

---

You aren't punishing anyone with that system. You'll earn the same rewards that in a normal run. Is just based on the boss you have killed.
I can't see how unfair can be that.

Quote:

---

Originally Posted by Besbeset

You aren't punishing anyone with that system. You'll earn the same rewards that in a normal run. Is just based on the boss you have killed.
I can't see how unfair can be that.

---

It's not necessarily that it's unfair, but it's less incentive to click the "in progress" box. I think what others are trying to say is people aren't going to want to run for less tomes, so they'll be less likely to click the box and join an in progress.

Quote:

---

Originally Posted by Besbeset

But I think that it would be completely fair to base the reward on the time spent, isn't it?

I agree with adding an extra reward for helping others, but I don't like when that system is being exploited.
So they either need to change the way the rewards are granted, or implement some kind of penalty for those that intentionally "fish" for dungeons.

---

Just because something is fair doesn't mean people will use it. I think it's probably right to assume that a tank/healer who get a (near) instant queue most the time will go for whatever nets them the most tomes most of the time. So if you adjust the tomes, it will likely have a negative effect on those who lose a tank/healer during a dungeon.

That being said, they've already stated in one of the other threads on this topic that they will be introducing a penalty for people who constantly queue and withdraw immediately, and that they are fixing the bug that causes it to happen on it's own sometimes. I like that fix better than taking tomes away from people who queue to help. Even if that makes it equal, it's still less than what they can get now, so it is taking them away.

Quote:

---

Originally Posted by Sunarie

It's not necessarily that it's unfair, but it's less incentive to click the "in progress" box. I think what others are trying to say is people aren't going to want to run for less tomes, so they'll be less likely to click the box and join an in progress.

---

But I think that it would be completely fair to base the reward on the time spent, isn't it?

I agree with adding an extra reward for helping others, but I don't like when that system is being exploited.
So they either need to change the way the rewards are granted, or implement some kind of penalty for those that intentionally "fish" for dungeons.

Quote:

---

Originally Posted by Highlanderx

And there was a post on the english forums. That had a Dev recognizing there was a problem of people withdrawing on endgame dungeons repeatedly, because they are trying to join a partially completed run. And that the new Duty Finder that comes with the 2.1 update, that it would no longer be possible to do. And that they weren't going to punish anybody who did, because there is a chance its not the players fault, and there is no way for them to know if it is,

---

I guess I missed that post even though I read the dev tracker every day! But I'm glad they're aware of it.

Fine. Do not comeback and start "hard to find a replacement when we lost members in-progress" threads.

Quote:

---

Originally Posted by Evangela

Fine. Do not comeback and start "hard to find a replacement when we lost members in-progress" threads.

---

Isn't that already the case? I don't know about AK runs, but on dungeons before that, if tanks leaves before the end, it's faster to leave and re-queue than wait for a potential tank to join in progress that willl most likely not happen before the end of the dungeon (even as DPS).

I remember once running halatali as ACN, with another ACN as DPS. After the first batch of mobs, right at the start, even though it went smoothly, tank and heal both leave without a word for no appearant reason. We ended up finishing the whole dungeon 2 man team (with like 5 minutes to spare) while DF was looking for replacements that never came.

Quote:

---

Originally Posted by Evangela

Yeah... people who choose to join in-progress duties to help people who lost a member should be punished.

---

I don't see how you can consider not getting the full reward for NOT doing the full dungeon a punishment...

I know, every coin has two sides, and either way there will be people trying to abuse the system, but...

A few days ago my modem hooked up just as we started last boss fight in CM. By the time i reset everything and got back online, i was back in Gridania and got nothing out of that run. Also, chances are some other healer got the "join in progress" message, joined and watched the PT take down the boss from outside the locked area for the full 100 ToP...

I'm not complaining, sh## happens and ToP isn't hard to come by, but in my book getting full reward for little to no effort and no reward for d/c-ing at last boss is NOT fair...