Duty Finder griefing, for Crystal Tower especially

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.

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.

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

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.

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?

Quote:

---

Originally Posted by 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.

---

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.

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.

Quote:

---

Originally Posted by 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.

---

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.

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.

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).

There should be a 5 minute wait time from withdrawing til you can register again.

Kind of like abandoning a duty.

I fully agree as yesterday for instance were fully qued up then someone dropped out,
happened 4 times in a row. Penalties should be implemented for people that withdraw.

I've actually made this very same suggestion to SE twice since CT was added and the q-fishing started and worsened. I'll even re-explain it here for everyone else to see and read it and maybe a dev will read it and not scoff it off as a single person's grievance.

For those people who queue up for a dungeon and repeatedly hit the withdraw option or just don't click commence or withdraw two or more times in the same 5 minute period should have a 15, 30 or 60 minute penalty enforced on them just as we all have to eat a 30 minute penalty for leaving a dungeon in-progress.

We've already seen what the update did where it prevented people from seeing where the group they are getting ready to join did nothing. It's quite obvious few people read the patch notes to realize they can't see if they're joining an in-progress run at the first, second or final boss, or even if the party is brand new to the dungeon.

(Continuation of previous post due to being too long...)

I had hoped as most other players I know did as well on my server, that this would have eventually solved itself with people realizing what the patch included, however that did not happen. The problem is only getting progressively worse and worse as time goes on.

Just the other day it took me 30 minutes to get into a Haukke Manor Hard Mode because someone or some people kept withdrawing from the queue over and over and over again. The problem will not resolve itself, something NEEDS to be done by the devs at some point in the near future to combat this before it gets any worse. I may not have a job outside of the game, but I'd like to do more with my day than fight the queue to get into a dungeon for either exp, drops or allagan tomes.

They should just do what I and many others said to do with this issue. Just put a 1 minute ban on re queuing if you miss or press the withdraw button. Reason i say for missing as well is if people are trying to grief then they will just queue and afk it out.

The majority of times it's DPS that withdraws, you can easily see it. Probably they got bored of waiting and logged off time before, but the message is like they had just withdrawn. (This is when it looks like someone withdraws at the same moment the party is full.) When it takes a long time to withdraw and it's a DPS or healer, probably they were doing other thing while they wait (I have had up to 30 min wait as a healer, most times over 15 min, DPS nearly always 30 min or more) and didn't have time to change classes and accept (crafting and not wanting to lose materials for example), or were just afk in that moment thinking the wait would be longer. I think it's hard to wait 30 min, get distracted a bit and lose the party, and not only have to wait another 30 min, but also some extra penalty. If he had already logged off time before, he couldn't care less about the penalty.

Simple solution, add a 3-5minute cooldown on Withdrawn. If u withdraw it means u are busy, can't do the dungeon yet, if course this also means is still towwithdraw 24x if everyone withdrew but if they know the penalty won't happen as much.

Quote:

---

Originally Posted by Squa

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.

---

I think this is about the only way to curb the delinquents but the punishment needs to be harsher, 10 minutes to these people is nothing thats just giving them time to go grab another bong hit or something. Now queing up and withdrawing is one thing but waiting until DF comes up then pulling out should be met with a 24 hour lockout from all dungeons, guildhests, leves, etc. I'm willing to bet very few people would abuse the system again.

Yes I know it sounds harsh and things happen in real life so in hindsight maybe a 3 strikes kind of rule before the penalty is incurred.