"In-Progress" queue fishing has to stop

[Grailer]

aye, when we queue up for a CT and get 23/24 "a party member has Withdrawn" 10+ times it gets Aggravating

Its usually a tank that backs out . I think the solution is to ban the tank from DF for 48 hours . And if a tank leaves a dungeon mid run 72 hr ban from using DF .

They have to get harsher penalties on tanks for backing out since 30 minutes is a bit of a joke right.

[Ri_ri]

Its usually a tank that backs out . I think the solution is to ban the tank from DF for 48 hours . And if a tank leaves a dungeon mid run 72 hr ban from using DF .

They have to get harsher penalties on tanks for backing out since 30 minutes is a bit of a joke right.

I so wish they actually did this, just to read all the cries about queue times later.

[NovaUltimatum]

Its usually a tank that backs out . I think the solution is to ban the tank from DF for 48 hours . And if a tank leaves a dungeon mid run 72 hr ban from using DF .

They have to get harsher penalties on tanks for backing out since 30 minutes is a bit of a joke right.

This is one step backwards, it would cause even longer queue times than what we currently have.

[Skotie]

That is the colossally retarded idea that everyone else is bandying around. Do you realize how much worse that would make DPS queues? Queue fishers are almost exclusively tanks, because only tanks have no or nearly no queue times.

The Duty Finder should, under no circumstances, tell you whether the group is new or in-progress. You should have no way of knowing until you get inside. Upon getting into a new instance, if you leave, then you will eat a 30 minute penalty.

This small change will stop queue fishers instantly.

Lets assume they change it to what you propose. What is there to stop upset tanks from joining then preforming horribly on purpose to get booted so they can just rejoin another queue anyways? Are we also going to give those booted a cooldown timer? How do we know it was there fault and they weren't just having an off day?

[Zfz]

Theres no proof that it works that way so its not a fact.

The Commence dialog means you have been allocated instance resource. It means "You may enter RIGHT NOW."
When someone withdraws, we are thrown back to the front of our respective role queues. (This was confirmed by devs.)
A system message says reforming party, and then, as many of us have experienced, we sit at "Server Reservation".

The above are the facts.

Why, after we have been given resources, would we need to wait for that resource again? Obviously because the resource have been given to other people. (Unless you think each time someone withdraws, it creates an empty instance that nobody can access.)

This means even though we were at the front of our queues (hence the Commence dialog), when someone withdraw, others take over our "entitled resources" and get into an instance before us.

Hence whoever withdraws, is wasting people's time.

--

And even out or not isn't the problem. The problem is wasting people's time.

[kuikui]

What Zfz said is the problem. It is the only thing that explains why 23/24 queue pop, the 24th drops or times out, then you are placed back at 1/24. If you were REALLY being places at the top of the queue, it would immediately reassign 23/24 but it doesn't.

[Bankai305]

What other threads? Are you talking about the countless threads inanely suggesting that the in-progress queue and the normal queue be completely separated, so that all of our queue times become terrible?

Yeah. That's a completely stupid idea. I didn't want my objection to be lumped in with an idea that colossally retarded. This is a different fix. Besides, this post was directed at the developers, not the forum whiteknights.

Talk about retarded ideas. If they remove the ability to see if you are joining an in-progress party, many tanks won't be using DF, because if you dont know if you're joining an in-progress group, or starting a new one, they are better off joining a group through PF to make sure they have a competent team, instead of joining a random group.

Also FYI, you're not posting in the correct section if you're request is towards developers. This is the WHITEKNIGHT forum, I suggest you go to the FEEDBACK section of the forum, not general discussion.

[Muzy]

Also FYI, you're not posting in the correct section if you're request is towards developers. This is the WHINEWHINEANDBELLYACHE forum, I suggest you go to the FEEDBACK section of the forum, not general discussion.

Fixed it for you.

[wildgalax]

The Commence diale.

i still dont see how that proves that we are losing our spots in the que, and if we did go to the back of the line thats probably something se should've thought and changed by now.

And like i said earlier, even if that was the case with the ques in the long run you would have almost the same waiting time as if no one had withdrawn, since you would be favoured at times and other times not.

You may also want to think if your stuck in one of those dungeons and are waiting for a healer/tank, wouldn't you rather 1 join then them being in a fresh dungeon? So look at the big picture. At the end you have to weigh it out, there's no way anything will be perfect. However if they implement changes like some people have suggested of locking people out, i dont see that as a positive implementation. Either way its not going to affect me, it may just mean i wont be able to help people out in dungeons that they are struggling in.

[BoomerOU]

Simply hide the progress. Penalties only have the chance of having collateral damage if they aren't implemented correctly. Hiding the 'in progress' solves the problem without infringing on the right of the player to choose to cancel the df if they want to finish up a fate or something.