Locked out of the Duty Finder.

[HEC-]

I cannot control if another party members withdraws or not.
I should not be penalized for the actions taken by a different party member!

Well - but you can (and should) control who do you party with! I'm pretty sure this is working as intended (despite unclear description of the feature in - at least English - patch notes) otherwise the groups will "trade-off" withdraws within the party to still try to fish for a specific duty or one in progress. Imagine group of 7 players - each can withdraw twice before incurring any penalty so in total they can spam DF 14 times! Either way - if the "group" (although it's usually only one member) withdraws it affects other players who were paired with that group and such group should share penalty as whole, simple as that.

[Cerat]

I'm actually curious about this, as yesterday in a Shiva EX party I was in we had the same person withdraw 3 times and none of us incurred the lockout penalty. Was your party premade, partially formed or pure DF?

[Camate]

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.

[IzumiYuki]

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.

Is there any reason why the entire party has to be affected by the doings of a single player?

[Archadius]

Is there any reason why the entire party has to be affected by the doings of a single player?

If you're entering something as a partial pre-made party, be it with friends or via the PF, etc... You should either know these people, or be performing ready checks before you press that button to reserve an instance. Failure to do so is at the fault of the party leader. This system is working as intended. If you queue solo, there is no way that people can screw you over with this system. If you queue as a full pre-made party (or alliance in the case of CT/ST), there is no way that people can screw you over with this system.

I hope that helps clarify what Camate is telling you.

[Kimikryo]

Is there any reason why the entire party has to be affected by the doings of a single player?

This please.

While I welcome this penalty system for those "in progress fishers" I don't like to be the one getting a penalty if people in my party decide to withdraw for whatever reason (like the party leader forgetting he still has something else logged in).

There has to be a way, that only the one withdrawing gets a penalty (at least in 4 man dungeons) and not everyone.


And I had rather an official clear up what he is saying, and not somebody else who thinks he understands better than others.

[Ladon]

Is there any reason why the entire party has to be affected by the doings of a single player?

Because without it, if you get a party of three and queue up, you effectively get 9 cancels with some coordination to fish for what you might be looking for. They are trying to avoid this.

[kidvideo]

Is there any reason why the entire party has to be affected by the doings of a single player?

Looks like this is intended from the perspective of a single Duty Finder player... but this unfortunately can cause penalties against some who shouldn't be penalized for the actions of another.

[NyarukoW]

Is there any reason why the entire party has to be affected by the doings of a single player?

Because your party is not a single player. And had too many fishing troll parties withdrawing on things like ST, CT, etc, over and over. People shouldn't have to click commence 15 times in 15 minutes just to get started on CT or ST. There were groups of trolls doing this already thinking it was funny to mess with people.

I really like it now, when you click commence it is a go. No withdrawals whatsoever. But the DF fishers out of business. That is good thing.

[Eidolon]

otherwise the groups will "trade-off" withraws within the party to still try to fish for duty in progress. Imagine group of 7 players - each can withraw twice before incurring any penalty so in total they can spam DF 14 times! Either way - if the "group" (although it's usually only one member) withdraws it affects other players who were paired with that group and such group should share penalty as whole, simple as that.

You can not que as a party for In Progress. When que'ing as a party, you can ONLY que for a fresh/new dungoun. You are only capable of que'ing for In Progress when solo.

It baffles me that people think that there is que fishing going on in small/light parties. It is literally impossible and shows a complete lack of understanding to the system.