DF Lockout needs to be adjusted/looked at/reviewed

[Giantbane]

Tested it - I didn't get punished..so...? Did you even read the announcement in the update? There's 3 strikes and it only happens in a partial party. So if the person who withdrew didn't have 3 strikes already, it's a bug which as said, report it in the appropriate section - If not, you already wasted most of your strikes and got punished as per the new system.

Also, do you know what the definition of complaining is? It was a statement, not a complaint - SE did this change because people wanted them to hinder those who waste our time with constant withdraws.

What you quoted about this not being kindergarten was talking about giving a strike to the partial party when one person withdraws.

You said:

Heh, next time tell your fellow players to stop fishing for inprogress queues and trolling the queue - SE wouldn't have listened to the pleas to fix that situation. So it was done for good reason.

groups cannot fish for in progress queues
groups don't have any easier time trolling the queue than an individual does

So my response was, that whatever you were "statementing" about does not happen in groups. Thus it's a terrible reason to use to give a strike to the whole group for what one person does.

[Lithera]

I would also obscure the progress by displaying only 0/1 like CT/ST does so people could not fish for 2/3 in progress. If they *really* want in progress, let them take their chances they'll end up with a 15 minute wait and a 0/3 run. However, the result is you'll never have a withdraw due to fishing ever again.

The CT/ST fishers didn't care one iota that they couldn't see the progress. They still kept fishing. They don't anymore. Problem solved. In Progress Only will just screw DPS even more.

[Volsung]

Prime example. Garuda bonus window is up.
Someone has a PF group up for Garuda.
Couple of us join but it's not a full party. Party leader closes PF and ques group up.
Party leader receives a tell, he invites the person into the group.

Party makeup has changed. Your registration is withdrawn.

Why am I locked out of DF for 30 minutes?
I thought it was 3 strikes withdrawing when the que had popped! That's 30 minutes of the bonus window GONE! Through no fault of my own! How was this a good idea?

This doesn't add up. I've added people to my party while in Que many times. I get that message
and am always able to put my DF back up.

[Giantbane]

The CT/ST fishers didn't care one iota that they couldn't see the progress. They still kept fishing. They don't anymore. Problem solved. In Progress Only will just screw DPS even more.

A few people determined enough to sit through lengthy queues just for a chance at a 2/3 that they won't know they got till they entered the dungeon will probably be balanced out with additional interest from people because they *can* join as in progress only. And you have to remember there's only so many in progress runs available. All of those runs are currently taken by people who click "in progress optional". With "in progress only" available, more "in progress optional" people will be pushed into fresh dungeons. You'll also get some DPS who will switch over to "in progress only" because they're as crazy as the people as you described. The net effect is likely very little impact on the queue times of DPS.

In other words, I don't agree.

Besides, you have to recognize CT/ST isn't just people fishing. Part of it is needing 24 people to all hit "ready" at roughly the same time. That's a lot of chances to fail, I'm sure many of the withdraws are people AFK or whatever. It's the reason CT/ST can still get hit with multiple withdraws even after this change.

[Lazearus]

They aren't wasting anyone's time more than an individual withdrawing from the queue. In fact they're actually wasting fewer people's time as a group than an individual does. Think about it. If a group of 7 joins a queue for 8 person content, and the group of 7 withdraws, they are only wasting 1 other person's time. If an individual joins a queue for 8 person content and then withdraws, they are wasting 7 people's time. Sounds worse to me when the individual does it.

So what's the reason to punish the whole group for one person's actions again?

And that is why SE's method is good. 7 people who wasted the time of 1 person's will receive the same punishment as the single person who wasted the time of the 7 others. Do you really want SE to punish the single person who withdrew from an ST queue with a 23X30min penalty?

Anyway, in a party, each member must be proactive in ensuring everyone else is ready and prepared before entering the instance. This is precisely why every member will get the penalty because they are partly responsible.

Once again, I am okay with changing the system to punish only those responsible, but this current system is already good enough for me.

[Giantbane]

And that is why SE's method is good. 7 people who wasted the time of 1 person's will receive the same punishment as the single person who wasted the time of the 7 others. Do you really want SE to punish the single person who withdrew from an ST queue with a 23X30min penalty?

Anyway, in a party, each member must be proactive in ensuring everyone else is ready and prepared before entering the instance. This is precisely why every member will get the penalty because they are partly responsible.

How on earth could you possibly read what I wrote and think I wanted to punish the single person with 23x the penalty.

In both cases the person who withdrew is the one wasting everyone's time. He's even wasting his own groups time. 1 person clicked withdraw or was AFK, 1 person is solely responsible. This just actively discourages players from grouping with random people because they *might* give you strikes. Do you honestly think the game needs more of that?

How this system handles partial groups sucks.

[IfritReborn]

Let me put it more clearly since some ppl in this thread are incredibly vindictive and horrible human beings.

Party leader closed PF and qued us. He received a tell, he sent an invite to the person who I will refer to as person A who sent him the tell. Person A DID NOT accept the invite right away. The que had popped and it was only then that Person A accepted the invitation, forcing us to withdraw not of our own will and locking us out!

I deserve to be punished? Not only did I not know that the party leader received the tell and invited Person A, I had no idea Person A would accept the invitation so late, nor did I have any idea that the party leader may have already had strikes against him! Why must I even be worrying about this IN THE FIRST PLACE!

But lo and behold! I deserve to be punished for something out of my control.

[HeroSamson]

It's a terrible idea and there's pretty much no good reason to do it this way.

I am glad they did it.

I sit down in the rising sun sometimes to take a break, I noticed a Lala on the fire place just flagging up, flagging down non-stop, not first time I have seen this happen, people hide under places or just out in open constantly flagging up and down trolling the queque and some of these people are all max 50 and have nothing better to do.

People were complaining about this for a while and so SE decided to mess with it.

If you wanna blame anyone for SE changing stuff like this blame those who trolled the DF not others or SE.

[Ashkendor]

All of this was done because of people fishing in progress runs. And by people, I mean tanks. Take away their ability to fish the runs and the issues go away. Add a penalty instead, and thread after thread will crop up from the innocents caught in the crossfire.

Funny, I see more withdrawals from DPS than any other role, whether it be from timing out or just bailing.

In any case, roulette isn't truly random. It was designed to help new players through the dungeons they need to complete the dungeons required for main story progression. It's working, though. I see far less in-progress fishing now.

[Lithera]

That clarification helps. The fix here would be for the devs to change it so that the DF queue is broken as soon as the leader sends the invite rather than when the invitee hits Accept. You can't invite once the Commence window pops so there would be no risk of accidentally giving anyone a strike. The other option would be to disallow party invites PERIOD during queue. Force the party leader to break the queue to invite. Also it shouldn't have mattered that the party leader had 2 strikes already. THe lockout should only have applied if you previously had the 2 strikes. If you're certain you did not have any strikes (keep in mind the reset time), then submit a bug report.