"In-Progress" queue fishing has to stop

[Grailer]

A solution to this problem would be to add a 10-30min lockout upon multiple withdrawals from a ready DF que, either that or just hide the in progress(1/4 bosses down etc) display as suggested above.

1) If they hide the progress then people would just join , then leave . They don't get penalty for leaving a group in progress .

2) 30min lockout for multiple withdrawals would slow down the spam, but say the number is 4 withdrawals = 30 mins lockout . People would just join on the 4th and leave instantly the group is made and get 30 min lock out . But now you have group missing 1 player in which you have to wait for spot to get filled .. which might be a healer or tank spot usually . See 1)

The solution is to allow players who want group in progress to get group in progress and not a group that isn't in progress.

[synaesthetic]

The solution is to allow players who want group in progress to get group in progress and not a group that isn't in progress.

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.

[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?

[BloodPact]

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.

My main is a DPS but I tank most of the time in dungeons to evade this problem, and agreed, the best solution would be to remove all visible indication that you will (or won't) be joining a party in progress and place the 30 minute wait for any type of instance drop except for full premades.

[Bankai305]

Please, tell us how queue fishers not using DF will slow down those trying to start new parties? Because right now, they only effect they have on them is already slowing them down. How does wanting queues for starting new parties justify the tool being used for fishing? A 30 minute penalty for fishing hurts new parties how? The fisher isn't going to stay in the party anyways, so how does removing them from the queue hurt the new party? Please, tell us.

The reason why you stay queued for 30 minutes with people dropping is because NO ONE is queuing for NEW content. EVERYONE is queuing for In-Progress, and they ditch when they get put in a new one. So, if you removed the fishers, trust me you will STILL sit for 30 minutes queued, but with the difference than now instead of getting a pop/withdraw, you won't get a single pop and your queue will take forever.

If people were queuing for NEW instances, you would NOT be waiting 30 minutes, would you now?

[Maxthunder]

Let them fish for a party in progress it is their choice. Either way you will have to wait regardless. If they took out the join in progress those players will more than likely just form a pre made and guess what that's less players join your solo or duo or trio Q. Personally when I do something its always in a pre-made so I dont have to worry about other player's that dont wanna perform or be carried thru a run.

[Nysneirdre]

Let them fish for a party in progress it is their choice. Either way you will have to wait regardless. If they took out the join in progress those players will more than likely just form a pre made and guess what that's less players join your solo or duo or trio Q. Personally when I do something its always in a pre-made so I dont have to worry about other player's that dont wanna perform or be carried thru a run.

That's fine, have them stop joining. At least I don't have to switch to my main class and wait as the stupid window pops up 200 times forcing me to wait it out and not let me continue on with what I was doing before. I would RATHER WAIT longer and keep on doing what I was before.

[Raucent]

aye, when we queue up for a CT and get 23/24 "a party member has Withdrawn" 10+ times it gets Aggravating
i can understand someone afking while waiting for DF, however SE could implement a check such as weekly queues backed out of if over lets say 20 in the course of a week every withdrawal after comes with a 5-10 min lockout (20 is just a random # they can set to whatever they wish)

[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.