"In-Progress" queue fishing has to stop

[synaesthetic]

Please, Square, adjust your Duty Finder system so that players are not told whether the instance they queue into is in progress or a new instance. This queue fishing is absolutely ridiculous. I have been trying to get into CT for the past twenty minutes and the queue failed over thirty times, but I am forced to deal with this because a number of people will continually turn the queue down when it isn't putting them right at the final boss.

There is absolutely no reason to tell players where the dungeon party is before they queue into the instance; the party already in the instance can tell them where to go once they get in. Allowing them to leave the queue before entering only results in this selfish behavior.

[cotti]

And what about your statement is so special that it deserves a whole thread, instead of posting in any other that deals with the same issue?

[Zaels]

And while we're at it, let's go yell at those "I QUIT DIS GAME SUX" posters for feeling special enough to make their own threads instead of posting on someone else's.

[Doo]

To be fair, this topic deserves multiple threads. It's really that bad for anyone wanting to do CT.

[MeiUshu]

your answer, Cotti, is kind of silly, I understand the point of OP, she has the right to post that, it is an annoyance, it is a problem, when in DF and you click, you shouldnt have the choice to leave. You go and deal with whatever comes your way, there are other people involved that you (general you) use the time for nothing, if you each time leave you in fact use the time of others, it is annoying. You already chose what you want to do by clicking DF, from there on it shouldnt be anymore a choice, but that is me

Mei

[synaesthetic]

And what about your statement is so special that it deserves a whole thread, instead of posting in any other that deals with the same issue?

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.

[Nysneirdre]

And what about your statement is so special that it deserves a whole thread, instead of posting in any other that deals with the same issue?

Just about a much as you trolling every topic that comes up. Hit that back button if you don't like the topic. No one hired you to be the forum police.

[Mezolitik]

This thing is moving backwards just as quickly as it's consuming the high-end raids. It's an issue in Dzemael Darkhold at level 44.

The 'join in progress' function is a double-edged sword. On the one hand, it helps restore crippled parties; on the other, it's exploitable. We can't get rid of it...but it can't really stay in its current state.

[synaesthetic]

What'll end up happening is more and more people will use the party finder, which will only make solo queues even longer. The Duty Finder will only place 8-player parties queueing for CT with other 8-player parties. People are getting really annoyed by this and it's not going to just go away. The easiest fix is to simply prevent the Duty Finder from telling players if the dungeon queue they just popped is a fresh instance or an in-progress run. That way they won't know if the dungeon's been half-cleared until they queue inside and at that point, leaving would result in a 30 minute deserter penalty.

[wildgalax]

seems its either make seperate ques or penalties. Problem with that there will be less healers and tanks to que up. As a fisher i probably wont be using df again. However if left as it is or seperate ques i will at least use it and try help and finish some dungeons off.