Duty Finder griefing, for Crystal Tower especially

[Fancyfeast]

Ok this has been happening a LOT since the last patch, where I get the notification that CT or Castrum/Praetorium is ready to go, and I click ok and then within a couple seconds inevitably someone withdraws. If this happened just a couple times it would be OK, but this morning it literally happened 23 times in a row! So it added another 15 minutes just to get the dungeon actually started.

Apparently some people think it's funny to continually spam withdraw from duty?

This has happened several times during the past week, where someone withdraws about 10 times before it's ready, but it seems to be getting worse....

SE needs to implement some countermeasure, like some kind of timer to disallow signing up for a duty if you withdraw multiple times within a certain amount of time.

[dspguy]

I agree. Or they should get rid of the notice that you are joining a party in progress. Let them join, but don't inform them whether it is a party just starting the instance or one that is on the boss.

[SkyHighDN]

for CT it may be a good idea to break it down to 8 members..... confirm the commence of alliance "A".... and once the full party of 8 is confirmed, then confirm the alliance.... if you have the spamming in your group, the other 2 alliances aren't penalized for the withdrawal troll..... and the next queued alliance will take your place....

Now will this suck to be a party of the alliance that is frequently getting withdrawn.... yea... but at least the other 16 people can get started with a fresh complete 8 group.... especially since there is basically only a set amount of servers to run this instance, and it is over run on monday tues and weds....

this should stop the 50 min queues for a dps using df

[Nash20]

Not a bad idea Robin.

I think we all can agree, CT a majority of the time is more of a hassle than it is fun anymore. From high queues, to PF people claiming items before entering, griefing, trolling, Vote Abandon, crap drop rate and bullying.

Sad part is, the first week or two I loved CT...was fun and people were patient.

[Fancyfeast]

This is still happening - I was hoping this week's patch would have fixed this obvious problem.

Doesn't SE have a team of people that just play the game to experience usability issues that need fixing like this?

[SummonerSenah]

I agree. Or they should get rid of the notice that you are joining a party in progress. Let them join, but don't inform them whether it is a party just starting the instance or one that is on the boss.

The problem that you would get with that is that once everyone joined and saw what the progress of the run was, they'd just leave if it wasn't in progress to where they want, and you'd be stuck in there waiting for a replacement anyway.

[ProxyTooMuch]

It may have happened 23 times in a row, but it's very likely 23 different people. Whenever I see it happen, it's rarely the same combat role withdrawing.

[Squa]

It may have happened 23 times in a row, but it's very likely 23 different people. Whenever I see it happen, it's rarely the same combat role withdrawing.

I think 2 things

1) they should increase the time to 'accept' from 45 seconds to 1 minute. Lets say you get a drink or step away for a second

2) not accepting or 'withdrawing' will enact a 10 minute temporary lockout from queuing again.

[buritoslicer]

I just ran into this issue today with queue time because people kept withdrawing in hope to find a party in progress. There should be a countermeasures against this with upcoming hotfix patches.

[Vhailor]

I agree with OP, and generally favour any and all suggestions to curb the behaviour.

At the very least, countermeasures should include removing the progress indicator entirely, and putting penalties on those with multiple withdrawals in a relatively short period of time (say, multiple within 10-15 minutes).