Wait as Default on Controllers

[HONK]

As stated in other posts, when you are out of the room, and most likely have your controller in ONE hand and DF pops you could just press X to confirm or O to wait, but not anymore

I'm actually still hitting X only to realized I've just hit wait...

Are you saying that it's too hard for you to adjust to a new automatic behavior? You just have to do it consciously a few times, after that it's just like before.

[Katsaria]

They really should add the wait command to the FCOB initiation menu for both KB/M and Controller.

[seida]

It's irritating for me, I have to say. After always immediately pressing circle to confirm for over a year, yes, it is instinctive now.

It pops and half the time I now automatically press wait.

Is it a terrible tragedy? No, but it IS annoying and the opposite of a QoL improvement as far as I'm concerned.

[valho]

A toggle please, less click is always better than more, now I have to click twice just to commence where I use to only need to click once.

And also a toggle to set all confirmation window to Yes instead of No, that really really annoy me actually that it's defaulted to No.

[Kogasan]

What I was hoping this wait button would do is not what it does I really wish se would put in a function that would make the duty finder actually wait like when I zone into mordhona and it takes forever. For me to zone it would actually wait so I don't loose my dungoen que for something I cannot control. That is what they really need to implement not some stupid wait function that doesn't actually work.

[Seif]

I'm one of those people who ALWAYS accidentally canceled. These instances were NEVER DURING GATHERING so the current system is super duper awesome and I haven't messed up the registration since 2.5.
Big thanks and PLEASE leave it as it is.

[LineageRazor]

I'm not going to argue whether or not the addition of the Wait function was the right way to go - but something DID need to be done. The fact that players could unintentionally Commence was a pretty clear design flaw. It's not just Gathering jobs that make use of the X button; you use it to target mobs, for instance, and engage auto-attack. Needless to say, targeting and attacking an enemy is not a rare occurrence in this game - particularly if you're farming FATEs with lots of targets.

Or how about the rarer, but extremely unfun case where you're about to talk to the Repair NPC because all of your gear is broken? Only - nope, you're in a dungeon now, and you might as well be naked...

The fact that the Commence window appeared and immediately became active means that players have a good chance of inadvertently entering an instance before they were ready. While this change may inconvenince folks who would like to select commence while afk, it really was the case that something needed to change.

Now, perhaps a better alternative would have been instead to add a one-second or so delay after the Commence window appears before the Commence and Withdraw options become selectable, while still keeping Commence as the default option. That way, folks sitting on the porcelain throne could still mash accept without going into "wait" mode, and players mashing buttons to select mobs or NPCs will have a moment's grace before they're sucked unwillingly into an instance.

[Neira]

Hoping a representative reads this, in case the suggestion hasn't already been made, but is it possible that this wait button that has been added(to essentially bump the duty window off screen temporarily) could be given a new functionality? When I saw it, I had hoped that it was giving an option to deny the duty queue, but instead of cancelling it out entirely, merely pushing yourself back in the queue, buying you a few extra minutes to finish whatever activity you may be in the middle of.

Along with the other comments expressed here, such as an option to set your cursor's default to wait or commence, is it possible for a function such as I described to be looked into? It would be a nice addition to the recent changes to the duty queue, and I'm sure something that most players would use at least once.

[Roris]

I don't really understand, the chances of hitting withdraw are still exactly the same, it's still an accidental right direction and accept button press. It's the very same button combination to accidentally withdraw, so nothing really changes, all it does however is make it so accept is now 2 button presses away. Having the reassign venture option default to cancel is annoying too, I understand exactly why it's like that but it's still annoying if you just send stuff on one type of venture.

[odie]

Why not just default to Commence? If they are busy, the game would prevent Commence from working in the first place. It's pretty hard to accidentally end up in a duty.