Party member withdrawal spam needs to stop

[Souljacker]

The only thing that will stop it is not showing the "in-progress" anymore. Take the option out and filter people into dungeons as spots are opened like every other game on the planet does. This is precisely the reason Blizzard took it back out when they thought it would be a good idea - people fishing to in-progress runs (and by people, I mean tanks) and withdrawing from fresh ones. Wanting to punish people for using a system is the wrong approach. Fixing the system is the correct approach.

[Kaisha]

The only thing that will stop it is not showing the "in-progress" anymore.

Or make in-progress tick check for in-progress runs only, so they can enjoy sitting there for 30min in queue with nothing popping up since 50 others on the server will be doing the same.

[Riviere]

Or make in-progress tick check for in-progress runs only, so they can enjoy sitting there for 30min in queue with nothing popping up since 50 others on the server will be doing the same.

This is exactly what I think. Why not just make it separate?

[Souljacker]

This is exactly what I think. Why not just make it separate?

It will cause more issues than it will solve. Once people realize that queue is no longer "insta" they will go right back to the main queue, leaving parties who need replacements out in the cold. No, this has been discussed to death years ago elsewhere and the solution was going back to filtering everyone into the randoms, randomly. The whole idea of "I want a random, but it has to match these conditions" defeats the entire purpose of a random queue.

It's going to take another year or so for SE to learn this valuable lesson, but mark my words, they WILL learn it eventually. The best solution is usually the one where neither side walks away entirely happy. I lose my in-progress fishing, you lose your "random but fresh" random queue.

[Riviere]

It will cause more issues than it will solve. Once people realize that queue is no longer "insta" they will go right back to the main queue, leaving parties who need replacements out in the cold. No, this has been discussed to death years ago elsewhere and the solution was going back to filtering everyone into the randoms, randomly. The whole idea of "I want a random, but it has to match these conditions" defeats the entire purpose of a random queue.

It's going to take another year or so for SE to learn this valuable lesson, but mark my words, they WILL learn it eventually. The best solution is usually the one where neither side walks away entirely happy. I lose my in-progress fishing, you lose your "random but fresh" random queue.

How will this cause more issues? If people can queue for in-progress only, they don't have to ruin new groups with their withdrawal spam.

[Darki]

The only thing that will stop it is not showing the "in-progress" anymore. Take the option out and filter people into dungeons as spots are opened like every other game on the planet does. This is precisely the reason Blizzard took it back out when they thought it would be a good idea - people fishing to in-progress runs (and by people, I mean tanks) and withdrawing from fresh ones. Wanting to punish people for using a system is the wrong approach. Fixing the system is the correct approach.

This right here. There is actually a famous quote that goes with this to:

“You never change things by fighting the existing reality.
To change something, build a new model that makes the existing model obsolete.”
― R. Buckminster Fuller