Locked out of the Duty Finder.

[Mugiawara]

It makes sense actually, since it's your party constantly queuing and withdrawing - You're still trying to queue up with other people, it's a system basically to deter wasting people's time with that. Since you're in a party together it makes sense you all get the penalty since it was the party that withdrew.

This feature needs to stay, if anything it needs to be a bit more strict than it already is. It's done much more good than it has harm.

Constantly? Is it constant withdrawals or just one?
This has to be a bug lmao. The "3 strikes your out thing" is good enough.
Penalizing the ENTIRE party because someone else withdrawls is not fair.

[Crankysorc]

It'd be real easy to troll right now by offering free queues as a healer or tank for those leveling up and just giving them strikes instead.
I feel like this alone should make it not count for the entire party.

If a heal/tank were planning to party up to troll and it gives the penalty to the entire party, they're just going to choose to alternate solo queue withdrawing instead.

[Granyala]

Then what is a party supposed to do when someone drops mid duty? GG, abandon?

I said HIDE the status so the participant doesn't know whether its a fresh run or an in progress run until he is IN the dungeon. Not remove the option to queue in progress.

This BS system was implemented because people (probably tanks with their instant invits) fished for in progress runs, trolling everyone that was queued by constantly getting pops that end up aborted.

[LaylaTsarra]

Feel free to try it out yourself, join a party, have the party leader sign up for a Duty, have someone withdraw, enjoy your lockout.

You might want to reevaluate who you queue with if they aren't reliable. This has to happen 3 times in a day for it to apply. Also ST is now bearable as are some other duties without all the continuous random withdrawals. I like the new rules although I'll admit if the entire group is being penalized perhaps that should be looked at.

[MilesSaintboroguh]

I said HIDE the status so the participant doesn't know whether its a fresh run or an in progress run until he is IN the dungeon. Not remove the option to queue in progress.

This BS system was implemented because people (probably tanks with their instant invits) fished for in progress runs, trolling everyone that was queued by constantly getting pops that end up aborted.

So you're telling me that every time I join a duty, I have no control over whether or not it's fresh or in progress? What kind of BS is that? No, I am not an in progress fisher, but maybe some people actually like starting at the beginning, not the middle.

[VesperValveto]

So you're telling me that every time I join a duty, I have no control over whether or not it's fresh or in progress? What kind of BS is that? No, I am not an in progress fisher, but maybe some people actually like starting at the beginning, not the middle.

That's not what they are saying at all. They said to HIDE the status of the dungeon. if you want to do a dungeon from the beginning, simply don't click on the "join party in progress" (or whatever it's called). If you want to try to get in a group already started then click on the button and take your chances of getting in mid dungeon like it was intended.

[Shadray]

So you're telling me that every time I join a duty, I have no control over whether or not it's fresh or in progress? What kind of BS is that? No, I am not an in progress fisher, but maybe some people actually like starting at the beginning, not the middle.

If you want to start at the beginning don't select join in progress option.

[Darkoon]

You might want to reevaluate who you queue with if they aren't reliable. This has to happen 3 times in a day for it to apply. Also ST is now bearable as are some other duties without all the continuous random withdrawals. I like the new rules although I'll admit if the entire group is being penalized perhaps that should be looked at.

In order to create a better community, we must avoid the community. GENIUS!

[Daragust]

Sadly, I'm pretty sure this is working as designed. That being said, it is definitely a bad design and needs to be fixed. Only reason I think this isn't a bug, but a flawed design, is that at least once during development a QA person would have had to see this behavior. It isn't exactly a hard thing to reproduce. If you have doubts, go do it yourself and see what happens rather than attacking the player who is reporting the issue. No one deserves to be locked out of doing dungeons for actions outside of their control. Currently, this makes using PF at all a very dangerous thing and we don't need yet another abuseable system for people to take advantage of.

[Daragust]

You might want to reevaluate who you queue with if they aren't reliable. This has to happen 3 times in a day for it to apply.

Actually this isn't true. Yes, you will get totally locked out of dungeons for the day at 3 occurrences, but prior to that you are still getting withdrawal penalties that stop you from queuing for a while which is what I believe the OP is showing.