Tanks Who Constantly Queue and Then Withdraw Trying to Get in Progress Instances

[Mishayangg]

The problem is that there are players that ONLY want to join "in progress" even if they have to wait 30 minutes to get into a group like that.

The logic is flawed today since the queue puts together "in progress" and "new" in the same pot for faster pops.

They should separate the queues. If you want to join "in progress" you will never get a pop for "new dungeon".

[KiraJ]

3 days ban for checking the "Join in progress" box, and wanting to actually join a group in progress?
Are you for real?

Yes and he's right. I guess you are one of those ranting when the said thing happens all the time.

[Aegis]

Either seperating the queues or not showing in progress status.

TBH, I'd be in favour of either.

Seperating the queues won't cause the fresh queues to be longer because it's a natural balancing act: Fewer fresh runs because tanks are in 'In Progress' queue = fewer runs for people to join in progress = In progress queues take longer = Tanks less willing to rage quit because In progress queues take a long time.

If the 'In progress queue isn't as attractive to tanks because the queue is so long, more will join fresh parties.

And as for not showing the 'In progress' status of a queue... I don't really see any possible downsides.

[synaesthetic]

And as for not showing the 'In progress' status of a queue... I don't really see any possible downsides.

There are no downsides. Every game I've ever played with an instance matching system did this. You could flag yourself as "able to join an in-progress dungeon," but it would never tell you if it was new or half-completed. You wouldn't find that out until you got in.

Splitting the queues apart completely? No. That just encourages toxic, greed-driven behavior. These people aren't queue fishing to help people finish runs. They just want an easy 50 myth tomes or to snipe that last boss's drop.

[zakalw3]

"Sickens me"

Really?

This forum would be a much more productive place if we could reign in the emotional hyperbole.

[KraggyKor]

That just encourages toxic, greed-driven behavior.

Seems to me this doesn't need any more encouragement, SE already did that with asinine gear acquisition requirements and dungeon entry mechanics.

In this case it's the back-loading of rewards on the last boss that's crass, they obviously should be spread over the entire dungeon .. except doing that kills pretty much any incentive to join 'in progress' groups, which is presumably why SE end-loaded on the last boss .. which causes the toxic behaviour we have now.

It's an un-squareable circle, fix one thing, break another. Ultimately it's due to SE making gear acquisition such a painfully, drawn-out and tedious process that it encourages people to find the path of least resistance and be jerks to everyone else in the process.

[Sadana]

And as for not showing the 'In progress' status of a queue... I don't really see any possible downsides.

But wouldn't they just beg for a vote kick (or hold the party hostage by sitting) once they got in and saw they weren't at a point they wanted? That's awful too... and something we know many people would do.

[Zakalwe]

But wouldn't they just beg for a vote kick (or hold the party hostage by sitting) once they got in and saw they weren't at a point they wanted? That's awful too... and something we know many people would do.

Ah, but that's harassment and subject to reporting and possible disciplinary action.

[Sadana]

Ah, but that's harassment and subject to reporting and possible disciplinary action.

True... but HAS anyone been hit with the banhammer after being reported for this?

[Aegis]

But wouldn't they just beg for a vote kick (or hold the party hostage by sitting) once they got in and saw they weren't at a point they wanted? That's awful too... and something we know many people would do.

Report for harassment. Wait them out. They don't get what they want and a they will get a GM visit and/or reprimand.

Even if you do kick them, they flag backup for an in progress run: they get you. There's no way for them to avoid a full run.