Our cries have been answered!

[Codek]

From patch notes:

"Players who select Withdraw from the Duty Ready confirmation window or allow the window to time out without making a selection three times or more in one day, will be temporarily prohibited from registering for duties via the Duty Finder."

"This count will reset every day at 9:00 a.m. (PDT)."

[Ganvire]

This could be the entirety of patch 2.4 and I'd still be brought to tears of joy.

[LittleArrow]

From patch notes:

"Players who select Withdraw from the Duty Ready confirmation window or allow the window to time out without making a selection three times or more in one day, will be temporarily prohibited from registering for duties via the Duty Finder."

"This count will reset every day at 9:00 a.m. (PDT)."

Wow that seems a little harsh. You only get 3 withdraws? I know it's frustrating to get constant withdraws in the duty finder, but a 3 strike your locked out of content for a day method is way overboard. A 30min - 1hr cooldown would've been way more appropriate.

[EDIT] I'm referring to times that I've withdrawn b/c FC members and friends asked to join my party as soon as the que popped. That's happened - a lot. Also, I'm not saying this is bad, just the way I read the passage it sounded harsh in context of what I just typed. Hopefully I misread it though.

[Nadrojj]

Wow that seems a little harsh. You only get 3 withdraws? I know it's frustrating to get constant withdraws in the duty finder, but a 3 strike your locked out of content for a day method is way overboard. A 30min - 1hr cooldown would've been way more appropriate.

^ Seems like this guy is one of the people who will be affected by this change.


This is excellent. You queue'd for something, you withdraw more than three times, now you can't queue for a day. This is excellent.

[LittleArrow]

^ Seems like this guy is one of the people who will be affected by this change.


This is excellent. You queue'd for something, you withdraw more than three times, now you can't queue for a day. This is excellent.

So you've never made a premade group and then a FC member asked if they could go just as the que popped and withdrew? That happens all the time when I play.

[NyarukoW]

So you've never made a premade group and then a FC member asked if they could go just as the que popped and withdrew? That happens all the time when I play.

Easy solution to that. Click commence go into instance. If they really have to go, they can take a 30 minute penalty and leave. Done, piece of cake. Otherwise if it is just the bathroom, people can wait 2 minute in the instance it will be better than the endless withdrawal nonsense. This way people are communicating and working it out.

Some queues can get pretty long. You get up for a drink, have to use the restroom, you're in the middle of crafting or you're in battle on the wrong class at the wrong time and all of a sudden you're down a strike.
...

No you won't. Run away from the monster and you will be able to switch class in less than 30 seconds. Abandon your craft. You are taking for granted the time of other players. Beside you got 45 seconds to wrap up whatever you are doing.

[Giantbane]

No you won't. Run away from the monster and you will be able to switch class in less than 30 seconds. Abandon your craft. You are taking for granted the time of other players. Beside you got 45 seconds to wrap up whatever you are doing.

Yes you will. There are a number of very dense areas in the game where it can take you over a minute to get out of combat, particularly beastman strongholds where a lot of daily quests are (that should be a reasonable thing to do during a long queue). Abandoning your craft is not a good solution, crafting should be a reasonable thing to do during a long queue but now you have to risk potentially expensive materials against losing a strike in a queue because it pops at the wrong time. 1 minute is just not all that long when you're in the middle of doing something else. Any bit of lag or disruption will cause a problem

You have to realize the the PRIMARY problem with this is fishing for in progress queues. There's no other reason why you see the abandon queue with the frequency we do now. Why hurt everyone when they should be addressing that specific problem. Instead they release a poorly thought out, overly strict solution and call it a day.

The withdrawals from queues IS a problem and it DID need to be fixed. But they can do much better, and it is very disappointing that this is all they have come up with.

I don't think so at all, you're queuing up for something which is essentially saying "I'm ready, lets do this." Sure you have to wait if your a DPS generally but if you know somethings going to come up than withdraw before the notice pops up and or once your in your dungeon let your party know that "Hey I need to go to the restroom or can I grab a snack real quick." and generally I'd think most people would be ok to this having to wait 2-4 minutes more than having someone drop out and letting DF take another 10-20 minutes finding a rep.

If it takes 10-20 minutes to find a rep, it's because the person that dropped has no desire to start at the beginning of the dungeon right now, and he was the only person available to join your group. If the person goes to the bathroom, they will be back in the queue within that same period of time, and your group is still at the front of the line, so he will rejoin and you will not have to wait any longer (although you'll not be sitting around in a dungeon twiddling your thumbs either).

[Giantbane]

^ Seems like this guy is one of the people who will be affected by this change.


This is excellent. You queue'd for something, you withdraw more than three times, now you can't queue for a day. This is excellent.

Some queues can get pretty long. You get up for a drink, have to use the restroom, you're in the middle of crafting or you're in battle on the wrong class at the wrong time and all of a sudden you're down a strike.

This kind of thing was bad when it's repetitive, 1 day seems very very strict. 3 withdraws within an hour or so seems like it should be more than sufficient to curb bad behavior.

Besides, depending on how bad the penalty is, it may be better to just join the queue and withdraw or "disconnect" immediately. How is that any better? I'ts not. This solution is incredibly ham fisted and is just asking for trouble.

So you've never made a premade group and then a FC member asked if they could go just as the que popped and withdrew? That happens all the time when I play.

this too.


EDIT: Honestly, the real problem is people fishing for in progress runs. They really need another option that is *in progress only* and then change *every* in progress display to work like it does for CT, ie: it only displays 0/1 so you don't know what boss it's on. Those who absolutely *must* have in progress queues can fight with each other over them (without knowing if it's last boss or not) while the rest of us can actually queue for a dungeon.

The OTHER thing they should do is not completely drop the group if one person withdraws. If you have 23 people all ready to go for CT/ST and one person drops or doesn't click ok, immediately replace with another member and restart the timer without having to wait for everyone to confirm. Only drop the full group if there are no more of the needed type in the queue or this has happened a couple times in a row. Something to that effect would also improve things greatly.

[Codek]

Wow that seems a little harsh. You only get 3 withdraws? I know it's frustrating to get constant withdraws in the duty finder, but a 3 strike your locked out of content for a day method is way overboard. A 30min - 1hr cooldown would've been way more appropriate.

I was also kind of thinking that but at the same time, I personally can not recall a time where I did withdraw 3 times (for good reasons) in a day.

[Teirshin]

Wow that seems a little harsh. You only get 3 withdraws? I know it's frustrating to get constant withdraws in the duty finder, but a 3 strike your locked out of content for a day method is way overboard. A 30min - 1hr cooldown would've been way more appropriate.

SE seems to have great difficulty finding that "middle ground"......