"In-Progress" queue fishing has to stop

[Choyi]

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.

As a "in progress fisher" you do realise you contribute to waste the time of 23 other people, maybe take a moment and think about that.

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.
Seperate ques would be a bad idea since it would just split the population up making for much logner DF ques.

This problem is the reason I just run one CT per week, with a 8person premade. Would probably run it more often if it didn't involve 10-20min of que ready popping up/withdrawn.

[wildgalax]

As a "in progress fisher" you do realise you contribute to waste the time of 23 other people, maybe take a moment and think about that.

.

sorry but where did i state i did ct? Maybe take a moment and think what people write first. I havnt even unlocked that as a matter of fact, i just happen to join 'in progress' high level roullete as of recent, and actually help a lot of groups out who are stuck without healer, or once that couldn't clear it, even those that we have 2 min on the clock to beat the last boss. I dont know the situation on ct, however if someone wants an in progress ct run and doesnt que up repeatedly, i dont see a problem.

[Bigpurpleharness]

sorry but where did i state i did ct? Maybe take a moment and think what people write first. I havnt even unlocked that as a matter of fact, i just happen to join 'in progress' high level roullete as of recent, and actually help a lot of groups out who are stuck without healer, or once that couldn't clear it, even those that we have 2 min on the clock to beat the last boss. I dont know the situation on ct, however if someone wants an in progress ct run and doesnt que up repeatedly, i dont see a problem.

Yeah.... You're still wasting people's time.

[Choyi]

snip.

So you are saying wasting the time of 3 people is just fine then?

But yeah, since you haven't done CT, a bit of infomation on the in progress que problem here:
It can take a DD 30min to get to the front of the que, then due to people fishing in progress they could end up waiting an additional 20min as the que pops de-pop and during this time they can't change class or do other content while waiting first in line (as they will repeatedly be asked to get ready o ntheir selected class).
Queing as tank and/or healer will remove the 30min initial wait that the DD has, but you might still get stuck seing the DF ready pop and withdraw over and over again for a good 10-20min before you can enter.

This just slows down the whole duty finder, as even tanks and healers who just would join whatever in progress or not, are stuck in limbo due to withdrawls from fishers.

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

[wildgalax]

[QUOTE=Choyi;1789837]

Well sorry if you feel offended that im 'wasting people's time'. i however don't buy that, and seems pretty childish to think that. As far as i know you will be immidiately put back into the front of the que, since i decide i dont wish to participate in a whole dungeon. I can understand to an extent if done like 20 times, to which im not supporting, and i doubt that is the typical case. Personally I would try once or twice, and cancel, and maybe try again later. If that causes a tantrum to people, then im shocked.

Anyway im all up for the penalty, and actually really eager to see just how much that 'fixes' the df ques.

[Zfz]

As far as i know you will be immidiately put back into the front of the que

This is my reply to another thread:

This is because you are getting a different group of people each time.

The matching system works in a two-stage process.

Stage 1: form a party from each of the role queues. Once the party is formed, send them to stage 2.
Stage 2: allocate instance, then pop the Commence dialog.

When someone withdraws, you restart from stage one, from scratch. That means the party is completely dissolved, everyone (except the one who withdrew) is thrown back to their respective role queues, and the system starts forming you into a new party as if you've never went past stage 1 in the first place.

This process is also why you can pop the Commence dialog (meaning you have been successfully allocated an instance), then someone withdraws, and then you form a new party only to sit at the Server Reservation.

It's also why at odd hours when there's only 1 tank in the world queueing dungeons, you could have 1 DD timeout (i.e. 1/1, 1/1, 1/2 at the Commence dialog) and then go back to staring at 0/1 1/1 2/2. It's because that only tank got sent to a different party.

So yes, we're put back to the front of the queue, but each time you withdraw from the Commence dialog, you force the other 3 people to reform a party.

Just accept that you are wasting people's time. Because it's a fact.

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

[wildgalax]

This is my reply to another thread:



So yes, we're put back to the front of the queue, but each time you withdraw from the Commence dialog, you force the other 3 people to reform a party.


Just accept that you are wasting people's time. Because it's a fact.

Theres no proof that it works that way so its not a fact. Even if it did that still leaves x amount of healers that are willing to click commence and y that aern't, whether the 'y's never logged in, or qued. Even if your case was true, the long run you will likely be favoured and pushed to the front other times to the back, so it would even out.