Locked out of the Duty Finder.

[Niwashi]

The other day we had to have someone sit out on a ST run because they missed a queue in the morning. When we queued up someone was checking up on their kid while the queue popped and we missed it, then someone was on a different job than intended when we queued and didn't realize it till the queue popped and we had to withdraw from that as well, which ended up locking out the member that had missed a queue in the morning.

I know it's somewhat of an extreme case but it still blows that they had nothing to do for 30 minutes because of a missed queue like 10 hours before. I mean it really hurts people with low playtime much harder than it should.

Someone who's still playing after 10 hours hardly fits the "people with low playtime" category. People with limited playtime are generally only going to be in one or two queues in a day, so won't withdraw (or be withdrawn by a teammate) from three of them. And for days when people are playing all day long, a 30 minute penalty doesn't amount to much, at least not for such a rare combination of occurrences.

(Note: This doesn't mean I disagree with the thread's point. I do indeed think it's rather unfair to be penalized for something somebody else did. I just think the problem is a minor and unusual one.)

[Bixby]

Someone who's still playing after 10 hours hardly fits the "people with low playtime" category. People with limited playtime are generally only going to be in one or two queues in a day, so won't withdraw (or be withdrawn by a teammate) from three of them. And for days when people are playing all day long, a 30 minute penalty doesn't amount to much, at least not for such a rare combination of occurrences.

10 hours before =/= 10 hours straight. One solo queue earlier in the day, then work etc., then another queue in the evening with others, who happened to screw up twice. And possibly the one thing they could've had time to queue for that evening. I.e., low playtime.

[JaydeDancer]

At first I thought this thread was made by an idiot who got themselves locked out of DF for a day by hitting "withdraw" three times in an attempt to make other people's lives miserable.

Then I actually read the first post and I agree with them. This does seem like a bit of an oversight with the programming. If one person in a party hits withdraw, for whatever reason, the whole party should not be locked out of DF for 30 minutes. That is simply not fair.

Also, I was under the impression, based on the patch notes, that the DF withdraw penalty only occurs after 3 withdrawals in one day and then you are banned from the DF for 24 hours. I thought that was fair and I looked forward to seeing that implemented, mostly because I wanted to laugh at the annoying people who withdraw from a duty just to make everyone else miserable.

This really needs to be changed, but I do not want to see a "Confirm Selection" box added. We don't need anymore boxes to click.

[NyarukoW]

...
Also, I was under the impression, ...

Your impression is not correct please see:

Since there appears to be a bit of confusion, I’d like to explain a little bit about how the Duty Finder penalty system works.

After the participants have been matched together, penalties will be counted in the event you press the “Withdraw” button or fail to press any button at all in the allotted time frame. As long as all of the party members have not been matched together, leaving the queue will not count towards the penalty.

Also, in the event that you queue up to the Duty Finder as a party, if one party member withdraws when matched, it will count as a penalty towards all of the party members. This excludes times when you queue as a complete pre-made party. Withdrawing in these instances will not count towards the penalty.

*When it comes to Crystal Tower, immunity for the withdrawal penalty only takes place when you queue as a full, pre-made 24-person alliance.

The DF penalty is 30 minutes. The strike count is reset once a day. If you can't hold your friends and other party member accountable and not abuse the withdraw, the collective penalty is good way provide social reinforcement of the correct behavior. The withdraw is NOT for the sake of the withdrawing player, but rather think of all the other players you are holding up. When you queue on the DF, you should take all necessary precautions to be ready queue when the queue pops. If should be common courtesy to not keep other players waiting.

[Cid_Grim]

I said it on page 16 and I'll say it again on page 43. Not only have I not received a penalty since this was implemented, I have not even received a single strike. I have even played with multiple partial parties.

The trick is to make sure everyone is ready before pressing the button.

[Fynlar]

You fail in dungeons so many times because of the fault of others...

And yet, none of those times are you given a restriction on when you can play/try again unless you personally made the decision to abandon your (full) group. Not really the same thing.

The game should not be imposing lockouts on you based on someone else's behavior. Period.

[polyphonica]

The game should not be imposing lockouts on you based on someone else's behavior. Period.

Well, then the real thing to rework is that one party member's withdrawal should not trump the whole rest of the group being ready, because right now that one person's behaviour does count exactly the same is if you yourself hit the withdraw button. Perhaps they should just make it so that the whole decision resides with the party leader. When the queue pops, the Party Leader decides whether to accept or not (up to them if they want to do a ready check or whatever), and if they accept, everyone else has the remaining time to either agree, or be booted from the party. This could result in more "gaps" to be filled by in-progress, but in that scenario it would make total sense for the lockout to only apply to the person who withdrew, because then rest of the party was allowed to commence anyway. It reduces queue failures in favour of more partial-parties.

[Niwashi]

Perhaps they should just make it so that the whole decision resides with the party leader. When the queue pops, the Party Leader decides whether to accept or not (up to them if they want to do a ready check or whatever), and if they accept, everyone else has the remaining time to either agree, or be booted from the party. This could result in more "gaps" to be filled by in-progress, but in that scenario it would make total sense for the lockout to only apply to the person who withdrew, because then rest of the party was allowed to commence anyway. It reduces queue failures in favour of more partial-parties.

Auto-withdraw from your party if you withdraw from a queue that the rest of your party accepts might not be a bad idea, but it seems like it would still be a queue failure. Someone withdrew and so you didn't have a full party formed. DF would keep trying to fill the open spot, the same as if they'd queued individually and withdrawn. The difference would be that the rest of the party isn't knocked out of the queue at the same time, (which is a problem regardless of whether there are additional penalties involved or not).

[Illya]

Greetings,

We implemented this new three-strike rule and its 30 minute penalty because we'd like players to be more mindful when pressing the withdraw button. As you know, when you queue up to the Duty Finder without a fully pre-made party, pressing the withdraw button after a match has been found will cause an inconvenience to other players.

We understand that this new penalty system can be frustrating for users who feel that they should not be punished for the actions of another party member. Therefore, in the future we will look into making adjustments so that only the party leader, or the player who pressed the withdraw button, will receive the penalty. With that said, we'd like to take time to look into this carefully as there may be methods that allow players to circumvent this.

The issue with doing this is you are now giving parties the ability to fish simply by having each member click "Withdraw" in turn, one after the other. So instead of 3 strikes and you're out, it's now 12 strikes. For a full party of 8, that's 24 strikes. This means we'll be going back to the days of waiting though 15 withdraws before you get into CT/ST.

[FruityTwotie]

Only the person missing / withdrawing should get the penalty --;