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

[Naberrie]

you assume that its not intended it very well could be that this is working as it should be. But it may not be as well. but untill SE says hey dont do this no one has the right to say people should be "banned " for it thats absurd.

Well, you're right. I am assuming. I believe they added the Join In Progress feature because they thought it would be a way for people to help other players. I believe that was their intent. That is my assumption.

Also, I'm not saying I think people should be banned, nor that I thought SE would take any such action. Nowhere in my post is the word "ban". I merely suggested that, if this continues, SE will likely take some sort of action; but I don't believe it will be bans. More likely they will add a penalty that will prevent people from entering an instance. Probably an hour. And I think it would only be triggered by withdrawing too many times within a window, like 3 times within an hour.

Also, I would like to reiterate a point. Yoshi said that the reason they don't allow Server Only in Duty Finder as an option is because if too many tanks or healers used that option, Duty Finder would essentially ceased to function if no one from those classes on your server was looking. The same would apply to Join In Progress only. If too many tanks were using Join In Progress Only, it would make it virtually impossible to form an initial party.

[Vanidin]

Really? We're solely blaming the Tanks?
I'm a tank myself (never ran my other classes in Dungeons or Guildheists) and my experience is with DPS repeatedly withdrawing from the queue, its maddening.

I dont think they should be a punishment though, just after 3 withdraws their locked into doing the instance - no "Commence" or "Withdrawn" option just dumped into it.

This. I can't remember a single time a tank didn't accept, it's almost always a dps. I typically queue as a healer, though sometimes as tank or dps.

[Lafiele]

They really need to start banning them. I main a PLD and it sickens me when this crap happens if I'm on another job. It's incredibly rude and needs to be punished.

Over reaction man. You don't need a ban for this, you just need a withdraw penalty timer.. like maybe 5-10 minutes and problem will be solved.

[mythicrose]

This. I can't remember a single time a tank didn't accept, it's almost always a dps. I typically queue as a healer, though sometimes as tank or dps.

I queue as a tank or dps. The offenders are generally tanks/healers. Those classes are the only ones that get instant queues. It's not that dps classes wouldn't be doing this if they could. Unfortunately in most cases, if they drop the queue they must wait for some time to try again.

[CrystalRainbow]

It's not just tanks.

my wife and I get this too. And she is a warrior.

[Tano]

it's mostly dps who get bored of queue and go afk forgetting it.

[Welsper59]

I have a better idea: How about they make "Join in Progress" actually work as intended? Make it so it is ONLY set to search for dungeons that are in need of another player. If Tanks need to wait 30 minutes for another Tank to drop in a in progress dungeon so they can join, so be it.

Once you select that button, you should only be searching for an In Progress dungeon, not one that's beginning.

Am I just too good of a person to understand that "Join in Progress" simply means you're okay with potentially being setup into a party that is in-progress? It just baffles me that people actually believe that the option was intended to be exclusive rather than inclusive. In other words, re-queuing for only in-progress dungeon/raid is an abuse of the current system. "Abuse" being a very strong word mind you, but still applicable. Of course, it's not like they'll ban people for it, as it's impossible to prove grief potential/intentions.

[Tano]

This has to be fixed by SE however.

1) add an option to queue ONLY for party in progress.
2) limit the number of times you can use it daily.
3) if a forming party is interrupted by a players who rejects or is afk, just find a replacement for that player, without starting the queue over again.
Like "1 player didn't accept the duty, finding another one, stand by", than it's found and who has already accepted doesn't have to do it again.

players are not using this feature in the wrong way. Is the feature itself that is poorly made.

[Kazamoto]

it's mostly dps who get bored of queue and go afk forgetting it.

This does not apply to the complaint we are having.

A single DF timer counting all the way down, and then re-queuing is understandable.

We are talking about when the DF ready window is only up for 2 seconds because someone is ACTIVELY clicking withdraw, then requeing, then clicking withdraw again, and again if it is not what they want.

[Wolf_Gang]

Adding a 1-2 min cooldown after withdrawing would be quick bandaid fix.