The occupied thing on duty finder is ridiculous

So I was queuing for Syrcus Tower, and in the meantime I was checking my retainers.
When suddenly it appeared to be ready so I wanted to accept it, but it said 'It's not possible while occupied' so I went back and closed everything with the retainers, but when I went back to the window my cursor was automatically at 'abandon'. I accidentally pressed abandon and got a 30 Min. penalty, very very fair. :mad::mad::mad:
Why doesn't it just let you confirm and close al the other window automatically? :confused::mad:

i see 2 people gave this post a like. so someone must understand what the hell this person is talking about. :/

Quote:

---

Originally Posted by BLaCKnBLu3B3RRY

i see 2 people gave this post a like. so someone must understand what the hell this person is talking about. :/

---

It's a gamepad thing. He was interacting with his retainers when his DF queue popped, which meant he couldn't hit "Commence" immediately. He had to exit retainers first, so he started spamming the cancel button, then the confirm button (because you have to shut your retainer up before they'll leave you alone, and that's confirm, not cancel), trying to get to the queue quickly. When he got back to the queue window, he just hit the confirm button on the gamepad (likely still spamming confirm from shutting up the retainer), which is, for some crazy reason, defaulted to "Withdraw" instead of "Commence" on the queue window.

Which would not be a problem if NPCs like retainers would just bugger off automatically when you hit "Commence."

i play on the PS4 and still fail to understand. like i understand you can't commence while accessing the bell for your retainers and some other work. however, the cursor is never defaulted to Withdraw. even if you hide the commencement window and bring it back up, the cursor still defaults to Commence. i have never once had my cursor defaulted to Withdraw. even under the same exact situation as his. and i also fail to understand how he got the 30minute abandon penalty. you can't abandon a duty you haven't commenced.


i am not sure what the issue is, but it sounds like he should make a bug report.

Completely ignoring the withdraw/accept positioning, I absolutely agree that we should be able to accept a queue no matter whether or not we're currently talking to a retainer, and we should also be able to accept a queue if we're not currently on the class we signed up on, it should just put us in duty as the class we signed up with.

Fair enough. Could've sworn other people said the default was Withdraw. It's been so long since I used a gamepad I don't remember myself.

Regardless, though, I agree that we should be able to commence even while interacting with NPCs or whatever. That's a pain no matter what input method you've got.

Quote:

---

Originally Posted by BLaCKnBLu3B3RRY

and i also fail to understand how he got the 30minute abandon penalty. you can't abandon a duty you haven't commenced.

---

Third strike. He'd withdrawn (or had group members withdraw) after the queue popped 2 times already that day.

Quote:

---

Originally Posted by Bixby

Fair enough. Could've sworn other people said the default was Withdraw. It's been so long since I used a gamepad I don't remember myself.

Regardless, though, I agree that we should be able to commence even while interacting with NPCs or whatever. That's a pain no matter what input method you've got.



Third strike. He'd withdrawn (or had group members withdraw) after the queue popped 2 times already that day.

---

hm. well i don't know. he says "abandon". and that Withdraw penalty gives you a 24hour lockout or something. not just 30minutes. i don't know. but all-in-all, at least to me, the OP makes zero sense. i am not saying it's impossible, but i have personally never clicked Withdraw by accident. i've actually clicked Commence by accident several times, though.

maybe the OP will clarify for us.

Quote:

---

Originally Posted by BLaCKnBLu3B3RRY

and that Withdraw penalty gives you a 24hour lockout or something. not just 30minutes.

---

It's 30 minutes, and it resets once a day. On your third strike, you're locked out for 30 minutes. Every time you withdraw (once the queue has popped; withdraws before the DF finds you a party don't affect anything) after that, you're locked out for 30 minutes, until the next morning's reset time (11 EST or whatever it is now; midnight Japan time).

Quote:

---

Originally Posted by Riepah

... and we should also be able to accept a queue if we're not currently on the class we signed up on, it should just put us in duty as the class we signed up with.

---

It likely wouldn't be able to find all the gear suitable to that class. If it switches you automatically, you'd show up naked with only a weapon equipped (assuming it would just take the first weapon of the correct type it finds in your Armoury Chest and would fail if there isn't one there). Of course, you could still put on your proper gear once you get there, but that's provided you realize it immediately and not at a "whoops" moment once mobs are aggroed.

Quote:

---

Originally Posted by Niwashi

It likely wouldn't be able to find all the gear suitable to that class. If it switches you automatically, you'd show up naked with only a weapon equipped (assuming it would just take the first weapon of the correct type it finds in your Armoury Chest and would fail if there isn't one there). Of course, you could still put on your proper gear once you get there, but that's provided you realize it immediately and not at a "whoops" moment once mobs are aggroed.

---

It could put you in the dungeon with exactly what you were wearing while you signed up as that class, minus any pieces it cannot locate in your armory chest / inventory anymore. They could also make it so that any items you were wearing during signup cannot be removed from the armory chest without automatically cancelling your DF search.
But yes, even only having your weapon equipped and having to manually put your armor on would be better than being unable to accept a queue pop when you're, for example, in the middle of a FATE and finding yourself unable to get away from aggroing mobs within the time limit, or at first attempted to finish the FATE quickly, realizing too late there's not enough time left.

Quote:

---

Originally Posted by Bixby

It's 30 minutes, and it resets once a day. On your third strike, you're locked out for 30 minutes. Every time you withdraw (once the queue has popped; withdraws before the DF finds you a party don't affect anything) after that, you're locked out for 30 minutes, until the next morning's reset time (11 EST or whatever it is now; midnight Japan time).

---

oh i see. well that's not so bad. the patch notes don't actually state a lock-out time frame. just when the with withdraw count resets.

but something doesn't make sense. if the lockout is only for 30minutes, why do we need a reset time for the withdraw counts? wouldn't they just auto reset after the 30minute lockout? or is every withdraw after your third strike initiate a 30 minute lock out?

Quote:

---

Originally Posted by BLaCKnBLu3B3RRY

but something doesn't make sense. if the lockout is only for 30minutes, why do we need a reset time for the withdraw counts? wouldn't they just auto reset after the 30minute lockout? or is every withdraw after your third strike initiate a 30 minute lock out?

---

The latter. Every withdrawal from 3 onward gives a 30-minute penalty.

Quote:

---

Originally Posted by Bixby

The latter. Every withdrawal from 3 onward gives a 30-minute penalty.

---

ohhh. okay. well that is pretty cool. i was always under the impression we would be locked out until that reset time. and sure as heck wasn't going to find out! lol. no more being scared of the DF wew. :/