Wait as Default on Controllers

[VanilleFang]

if your using toggle as an option, this is not the case.
it will pop and withdraw you while fighting.
it should default to wait , but changeable in settings.

everyone saying "wait" is ridiculous
should understand not everyone plays the way they do.

:

I literally have no idea what you are talking about.

Toggle as an option? Instantly withdrawing you while fighting? (You mean circle would do this?)

What ever way this is I don't know any one who plays like this. Circle, by default, lets you "wait" the DF so you can finish what you are doing.

Not to be overly rude but its really on you as a player if you accidentally commenced a duty. It dings and pops. If that wasn't enough "warning" that's really your fault. I have never accidentally commenced a duty or accidentally withdrew. I don't even know how that's possible honestly. You were either in a different Job/Class and couldn't except the Duty, in a cutscene, shop window etc and can't commence the duty, or you were doing something like gardening or fighting and could easily hit circle (unless you play like Logo I guess?) to put it away until you were ready. No one who is pro-wait option has even really explained HOW they accidentally commence/withdraw. Except for saying they are "mashing X", which is again their fault not the systems (they set up the DF and know what to expect) which only explains accidental commences not accidental withdraws.

This "wait" option is unneeded for many of us, and I would just like the option to make it so I don't hit Wait when I never screw up. I don't care if its there, I just don't want to have to deal with it.

[LineageRazor]

Not to be overly rude but its really on you as a player if you accidentally commenced a duty. It dings and pops. If that wasn't enough "warning" that's really your fault. I have never accidentally commenced a duty or accidentally withdrew. I don't even know how that's possible honestly. You were either in a different Job/Class and couldn't except the Duty, in a cutscene, shop window etc and can't commence the duty, or you were doing something like gardening or fighting and could easily hit circle (unless you play like Logo I guess?) to put it away until you were ready. No one who is pro-wait option has even really explained HOW they accidentally commence/withdraw. Except for saying they are "mashing X", which is again their fault not the systems (they set up the DF and know what to expect) which only explains accidental commences not accidental withdraws.

Under the old system, when your duty window pops the "Commence" button is defaulted and is immediately selectable. If you're in the process of pressing X and you don't notice this in time (and while people's recognition time varies from individual to individual, I think we can agree that NO ONE's recognition time is faster than a computer's) you will press X and enter the instance, even if you did not intend to. The fact that this has never happened to you, personally, is simply a matter of your personal good fortune, POSSIBLY coupled with a higher-than-average recognition time - not an indication that that the system was a good one. There's also the delay between your brain telling your thumb to press the button, and your muscles actually getting the job done. This, too, is not an instant process. I realize we're talking about fractions of a second, here, but the computer is STILL faster, by many orders of magnitude. There's PLENTY of space in there for a window to pop up.

And, has been noted, X-mashing is not necessary for this to happen. You just have to tap X once, and if you have the misfortune of having the window pop at just that moment, BAM! you're in, ready or not. The new system fixes this, most thoroughly, though arguably not in the best way.

[sarehptar]

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. With the default being confirm for so long, since the patch, I have found myself automatically hitting X the moment the DF pops, only to realize I've just hit wait on accident and now have to bring up the window again, move over, and then click confirm. It's an unnecessary hindrance and I seriously hope they reconsider the default or the very least give us the option to change it ourselves.

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

[FireHero]

if it pops while your not there then your not realy ready finish your toilet buisness and get back to it!
Having it default wait makes it easyer for most players you know cause when you go to the toilet your not ment to take your pad with you.

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

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

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