Locked out of the Duty Finder.

[polyphonica]

There is no complexity to the priorities of players in the queue. It's just a queue. The individual leaves and the individual reenters at the back of the line. The group leaves, the group reenters at the back of the line. There's no difference.

All the people who didn't withdraw or timeout are then added back to the beginning of the line and it tries to regroup them with others at or near the front of the line. Same result. The only time it's really effected is if there are just not enough people of a particular class in the queue. And it will act the same if the group has the needed class as an individual being the single class, ie: they'll get back in easily because of the needed class.

There's a huge difference. If one player goes to the back of the line, that's one less player. If a party goes back to the end of the line, that "times x" less players. The impacting queue wait for the party failure is on a different order of magnitude. If you're in a party of 8, it's no different from 8 withdrawals from the queue system's point of view. The system needs to find 8 replacements to accommodate the 16 ready players (and so on at smaller scales).

The result is a minimal behavior in queue behavior. A person will be discouraged from withdrawing because they don't want the strike. In the same way, within a group, each individual member will be discouraged from withdrawing because they *also* don't want a strike. So no, applying the punishment to everyone is not going to be very helpful in this situation and is only going to encourage more animosity between players when somebody makes a mistake that hurts everyone else. The game does not need more of that.

But this cannot work. What's going to happen when an individual in the group gets their three strikes? It will still inevitably impact the entire party because they are queueing as a group. As long as one person is locked out, you're all locked out. So you can kick that person. Okay, but you could already kick that person after the first strike to avoid the risk of a recurrence. Again, in all this time, every queue failure is multiplied by the amount of players in your group who are not able to enter the instance because of that one person's withdrawal. So the impact from the game's point of view is the same. The issue here is not the party members, who can at least control the party they're in, but the other players in the duty finder whose entry is delayed exponentially by the one person's failure to be ready.