DF withdrawl has become the new "Fatigue" system

[Laraul]

FFXIV 1.0 originally had the notorious fatigue system, where experience earned for a particular class would slowly deplete to nothing after eight hours, and required a week to fully replenish. I believe the idea was that it would modify player behavior, encouraging players to ration time played as any particular class. From the player perspective, it felt like a punishment for playing.

Now we're being punished for trying to participate in an instance! If you or your a party member can't click in on time because you forget to use /readycheck, 30 min reprimand! Or because you changed class to participate and hunt or battle... or because you forgot to deselect a previous duty... the controllers dies, the call of nature, a crying baby, a misbehaving pet or any other one of the things that happen in life, regardless if it's your life or a party member...

I do not understand why this was added. People generally don't queue the duty finder, wait a few minutes and click withdrawl over and over again. When a player queues for a duty it's because they WANT to participate in one. I mean "DUH!". And I see no evidence this has had any impact on the number of withdrawls...

[Zaft]

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.

If you're missing it three times, the problem is with you.

[Riepah]

If you're missing it three times, the problem is with you.

Party leader signs up without ready check, one person happens to be afk? Strike for the whole group.
Party leader accidentally signs up for wrong duty? Strike for the whole group.
Sign up, friend/FC mate of yours logs in or asks to join, just as the queue comes up? Either a strike, or leaving your friend waiting for ~30 minutes depending on what the queue was for.

I'm all for preventing in-progress abuse, but giving a strike to the whole group just because ONE person in the group messes up stinks.

[314159265358979323846264338327]

I do not understand why this was added.

A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
Finding new member.

[Ruri]

I do not understand why this was added. People generally don't queue the duty finder, wait a few minutes and click withdrawl over and over again. When a player queues for a duty it's because they WANT to participate in one. I mean "DUH!". And I see no evidence this has had any impact on the number of withdrawls...

Have you ever tried to que CT or ST? On average before the update to the DF withdrawl I would see 15-20 reque's happening.

[Kaze3434]

Party leader signs up without ready check, one person happens to be afk? Strike for the whole group.
Party leader accidentally signs up for wrong duty? Strike for the whole group.
Sign up, friend/FC mate of yours logs in or asks to join, just as the queue comes up? Either a strike, or leaving your friend waiting for ~30 minutes depending on what the queue was for.

I'm all for preventing in-progress abuse, but giving a strike to the whole group just because ONE person in the group messes up stinks.

people are misunderstanding how the lockout works from how you are wording it. if you are a full party of light party (8 and 4) you will not get a strike. for ST or CT it requires 24 for a full alliance.

[LunaHoshino]

Sign up, friend/FC mate of yours logs in or asks to join, just as the queue comes up? Either a strike, or leaving your friend waiting for ~30 minutes depending on what the queue was for.

I've been on both sides of that. You know what you do? You say "Sorry, but my queue just popped. I can help you when I'm done." If you're the person who gets told that, you wait politely and find something else to do.

[Laraul]

A party member has withdrawn from the duty.
Finding new member.
A party member has withdrawn from the duty.
.....

This is a flaw in the design of the duty finder. IE if there is a group of 34 people and one person click abandon, the other 33 people all see it pop again and all have click in again... it's annoying I agree and should be fixed. Punishing a player for clicking with drawl is a lousy fix.

Fifteen seconds is enough time to click in... meaning you shouldn't see the duty finder window pop more than twice a minute.

I'm just saying the fix lies in making the duty finder more user friendly, not less.

[RiceisNice]

This is a flaw in the design of the duty finder. IE if there is a group of 34 people and one person click abandon, the other 33 people all see it pop again and all have click in again... it's annoying I agree. Why don't they fix this? Fifteen seconds is enough time to click in... meaning you shouldn't see the duty finder window pop more than twice a minute.

How do you suppose to implement a way to stop people from doing that in the first place? Even if you were to move in as 33 people, you'd still be down a person (who is most likely going to be a tank or healer in order to get queued like that).

[Fyrebrand]

I'm not convinced that the DF lockout is working. In theory, it is meant to lessen wait time in DF queues. But in practice, I'm not sure it actually is doing that. Queues are as long as they have ever been, and people are failing to click Commence when it pops just as much as before. It just seems to be punishing innocent people for making easy mistakes, stepping away from the game for a minute to go to the bathroom, or partying with someone who failed to click in time. Like, if I queue for a dungeon with an FC buddy, and 30 minutes later he is AFK at that exact moment and fails to click Commence, I get penalized for it. No matter how you look at it, that is pretty ridiculous.

A couple of DPS who miss their queue have already waited 30-60 minutes for their dungeon. And if they even want to re-queue, they will have to wait just as long again. That is punishment enough. But if a tank and healer queue up, and one of them isn't ready or has to take care of something, now you're preventing much-needed roles from re-queuing if they get enough strikes. DF is worse off without them, even if they do fail to catch their queues a few times.

People who fail to click Commence are not why DF queues are so long. It is, and has always been, because parties require a balance of roles, but certain roles are far less played than others. Perhaps the greatest contributor to the problem was SE's boneheaded decision to make Light Parties with only 2 DPS. But rather than do the hard work it would take to address the real issue, we have a penalty system that points fingers at a scapegoat, and blames the players for problems in the game's foundations. I wouldn't call it "the new Fatigue system," but I would certainly call it a system that needlessly punishes players for having real lives and not really doing anything wrong.