Wait as Default on Controllers

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

[kidvideo]

engaged in other activities, such as gathering or crafting.

I never ran into this issue with a controller... The L1 & R1 buttons make the Cross Hotbar the active window selections, not the Duty pop screen. When the L1 & R1 buttons are not held, the duty window would become active... the X button was to Confirm & the O button was to Wait.

[Ophie-Mio]

We had figured out why the Wait button was implemented... Why there wasn't a default you could set is what we're figuring out now.

Also, you have to be doing some mad button pressing to accidentally Withdraw. On controller and my keyboard, I basically had to spaz out with both to accidentally Withdraw. The situation that Tiggy and Izsha is more common, accidental Commencing.

[Keoeson]

Personally I love the new wait option. It happened to me few times during gardening, where you just select a crop and bash X to fertilize, if duty pops you could only hope others take their time so you can finish fertilizing the remaining crops.

[HEC-]

The L1 & R1 buttons make the Cross Hotbar the active window selections, not the Duty pop screen. When the L1 & R1 buttons are not held, the duty window would become active... the X button was to Confirm & the O button was to Wait.

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. Finally - many players use toggle / mixed crossbar mode where you don't hold L2 / R2 to have the bar up and in such case any othe window poping up (including DF) will close / inactivate the crossbar and you'll hit button in the DF instead if you're engaged in battle or any other activity. Either way - adding of the confirmation is well welcomed and I personally have no issues with it to default to wait although I appreciate that some player would like to be able to change the default selectin in settings ...

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

[kidvideo]

That is greatly incorrect ...

Actually I miss-typed the buttons... It's R2 & L2, sorry for the confusion. R2 & L2 take precedence over the duty pop window.

[Tiggy]

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.

This exact situation has happened to me dozens of times. I was coming here to say exactly this but Grek beat me to it. This was especially aggravating after the punishment was added for queue canceling.

[EZ5902]

Greetings,

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.

I thought the confirmation of withdrawal was to combat that no?

Also agreeing with OP on this topic.

[sarehptar]

I thought the confirmation of withdrawal was to combat that no?

This exactly. In the end, I think this was a bit short-sighted of the devs--misclicks are presumably not happening constantly, consistently, or to everyone, so why does everyone have to be treated as if they need this triple layer of protection?

Pleaseeee give us the option to default to commence instead. Pleaseeee.