DF confirmation window cooldown

[Alukah]

Have you been in the situation of your DF being ready, but a party member keeps withdrawing over and over? (mainly tanks)

Yesterday after watching a tank withdraw around 10 times in a row, probably fishing runs in progress, I thought, what if they made people wait the whole 50 seconds (was it 50?) if they manually hit cancel? This could give the party some time to pull another tank and also would discourage this behavior. If people accidentally queued for the wrong content a 50s wait isn't unreasonable, IMO.

What do you think?

[Ruri]

Or have a cooldown of a minute or something after withdrawing from a DF.

[Luxx]

It's a damn hell hole if you're trying to que up for CT.

[Ruri]

Yea CT ques lol, I remember going through about 40 DF windows one time before entering. Hope the new CT isnt the same thing

[DieselPower]

Sometimes you can glitch on DF, and it'll fail you out of starting the dungeon, which is fairly likely to be what is going on. Ie, you're all set to go, and you click accept, but it fails with a message about not being able to start - I forget what the exact message was, but it was clear that it was a problem on my end. It's only ever once happened to me, and it needed a restart to fix :/

But humans being what we are, it's pretty much guaranteed to not always be that :/

[Yumi_umi]

There was also another bug where ppl could get instanced into a dungeon with 4 ppl already.
Had this happen in hakkuke hm a while back. A monk said he qued in prog but withdrawn but was too late as he got instanced in.
He didn't show up on the party list so our team comp was smn, whm, bard, tank but tank d/cd after.
It was kinda creepy seeing him there. Like he was somesort of anomaly. Only way to talk to him was to use /say .