Wait as Default on Controllers

[kidvideo]

One thousand times, yes. I was amazed there was no thread about this already. The "wait" is the dumbest thing ever. If you're doing something else and don't want to confirm immediately... just hit circle. We already had a completely viable way to "wait"--now we're stuck defaulting to an option that often isn't even needed--I confirm immediately way more often than I need to wait.

/agreed

I dislike this new "feature" as well. When using a controller Wait already existed as the circle button, Confirm was the X button. Now we essentially have a menu choice. If anyone wanted this update it should be a toggle setting somewhere rather than default.

[Cutie_McSnuggles]

I concur. I would LOVE an option to return the default to commence instead of wait.

[Gokuhan]

The Wait button is there so if you are going to "click" on something else and the DF window pops you aren't unintentionally confirmed. It's a fine addition, as long as hitting 2 buttons isn't overly taxing.

[sarehptar]

The Wait button is there so if you are going to "click" on something else and the DF window pops you aren't unintentionally confirmed. It's a fine addition, as long as hitting 2 buttons isn't overly taxing.

But, presuming that you are not button mashing, the circumstances under which this would happen would be so rare as to be negligible. Once or twice in a while? Maybe. Often enough to justify "wait" being the default for everyone? No way. Sorry, but two buttons every single time is overly taxing to me if the only reason it's required is that some people are clumsy about clicking. A few mistaken clicks now and then can be bothersome, but nowhere near as bothersome as being permanently locked into an option that I didn't need and will never use.

[AsahinaMyLove]

This annoying me too!! D:<

Now you cant press "Cancel" by accident because the systems will ask like "Really cancel?" - wich makes "wait" button even more useless.

[TheGrimace]

The Wait button is there so if you are going to "click" on something else and the DF window pops you aren't unintentionally confirmed. It's a fine addition, as long as hitting 2 buttons isn't overly taxing.

It actually is overly taxing.

[writeraeria]

Either I'll get used to it or they'll program something in that lets us pick whether it defaults on confirm or wait, but it's annoying the hell out of me at the moment. I keep hitting X by instinct thinking I'm confirming but really I'm that jerk who waits until the end to confirm.

[WHS]

I am having sorta same problem. Only I am not afk I am looking at the screen and am so used to just hitting the enter button on controller I hit wait. I would like an option to change the default to commence myself. If I needed to wait I would hit cancel on my controller and the popup goes away. Then when I am ready to hit commence I can do so. I have never had an issue with windows being in my way or any of that. I understand some might like or want this option and that is truly ok. Just give those of us that don't an option in the ui to change the default to commence. Ty.

[Amelia_Pond_Behemoth]

I found this to be a pointless change. If I was ready, I'd hit the X button and be ready to go. If I needed a couple more seconds, I'd hit the circle button and I could bring the window back up from the duty list when I was ready.

[Grekumah]

Greetings,

We appreciate your feedback on the addition of the “Wait” button, I will be sure to forward it onto the devs. For now though, I would like to explain why this feature was added.

There were instances when players were waiting for a queue to pop and during the wait they were engaged in other activities, such as gathering or crafting. If these players were in the middle of an action and the queue popped, there was a chance that there may be an accidental withdrawal from the queue. To alleviate this issue where players may have cancelled their queue progress after waiting, we added the “Wait” button and chose to make it the default selection.