Wait as Default on Controllers

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

[valho]

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.

Because it's a behavior that we never wanted. We are fine with the commence button as it is, but we understand that some players do like the wait button, so we are just suggesting SE to add a toggle where we can choose which button it default to.

Or better yet fix the commence button itself, if the player is ready and in the right class then just bring us into the instance when we click commence. If the player is not ready either they are crafting, not in the right class, gathering, etc or any other things that make it not possible for them to go into the instance, simply make it so when they click commence it automatically becomes wait instead. This would be a better user interface than the current one, which makes it annoying for some people.

[kidvideo]

That is greatly incorrect ...

First of all - once the DF menu pops up in in the foregraound / active and it WILL take X or O as action for DF window. Plus - if you gather you don't have crossbat up most of the time. .

Not incorrect. I'm not referring to gathering. I'm referring to open world content. On a controller you need to hold the cross bar button to have access to your abilities. If the duty window pops, that window is not active unless you are NOT holding the cross bar button.

Also, if you're crafting or gathering you can't accept a duty... so that's not the reason this "wait as default" was added.

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

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

[Cutie_McSnuggles]

I hope this gets fixed soon. I'm keep hitting wait and then timing out because I thought I hit commence.

[Logo]

Prior to 2.5, hitting Circle accomplished the same thing that 'Wait' does now. You just had to pop open the duty finder queue window to be able to bring it back up.



If you are fighting something, you probably are holding one of the trigger buttons down.. which makes hitting X activate the crossbar ability, even if the duty finder is up.

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.

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