Wait as Default on Controllers

before the update I've accidentally hit withdraw while desynthing more times than i'd like to admit >_>; heck. one time i forgot i was queued...tried to summon my choco (got the warning and stopped) then accidentally hit Wait instantly when i queued.

you don't have to be spamming the button for the queue to appear right as you're pressing the X button. (another example of how this mistake has happened, is pressing the X button to target the nearest monster/NPC, i do it all the time. so that too has messed me up before lol)

I may not do this all the time, for the the times it does happen (usually when queuing for something that takes awhile to get, as a dps) i'm glad that it's there.

I'm not aginst adding a method to change the default though~ so long as the default starts on wait

i honestly don't see the logic here. the default selection for the Commence window was "Commence". the ONLY way, without using virtual mouse, you could/currently can accidentally click "Withdraw" is the to push right on our d-pad then confirm. which can occur in the middle of some other activity/action. but i just don't understand how this "Wait" option makes this any less likely to occur.

Quote:

---

Originally Posted by 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.

---

Why didn't they go with making the pop-up window not steal focus?

If you're interacting with a NPC, or retainer, or marketboard, or gathering node, etc when it pops you are unable to confirm until you disengage, but your clicks now go to the pop-up window instead.

Good god, this is actually an issue with people, LOL :D

Quote:

---

Originally Posted by VanilleFang

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.

Quote:

---

Originally Posted by LineageRazor

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 [changes] this, most thoroughly, though arguably not in the best way.

---

Frankly this is a change to the system that as far as I can tell no one was asking for. Until this thread was created I'd never heard of anyone complaining about accidental commences. If that is a problem for someone then fine, give them the 'OPTION' to default to wait. Don't make EVERYONE do it.

First off, to all of you talking about commencing duty while still on a gathering/crafting job: Trust me, you won't get taken into a dungeon by accident while you're still a botanist or leatherworker. /facepalm

I play this game on PS3/PS4 since (re-)launch, and by now the DF "ding" activates some kind of muscle-memory "Am i ready? >> press X / Am i not? >> press O".

After over a year i can't think of more than 2 occasions where i hit commence but wasn't ready, and those were due to almost broken gear, wich, in turn, was 1. due to my own stupidity and 2. is a thing of the past anyways, since i can repair inside a dungeon now.

So, to get into a dungeon by accident, i would have to already be on the right class/job, wich can only be a battle-class. During fights, when holding R2/L2 (to use actions), it kinda negates the ability to hit "commence". For enemy-targeting i mostly use L2+R1 or R2+L1 (feel free to try it, it works really well). And if it really pops the very second i was trying to talk to an NPC... so what? I will stll be right in front of that NPC when i'm done with the dungeon.

But what does happen to me is: I'm queued for duty while i tidy up a room, are in the kitchen or bathroom and hear that all familiar "ding". Now fast, finish this, wash my hands, run back to my room, jump over my couch, hit X on the controller, yay, made it in time to... oh crap! i just hit hold, now to fumble that window back up, go to "commence" and... too late...

It's all about personal preference. And i would personally prefer the cursor to be on "commence" rather than "hold" by default.


But while on the subject of DF, if they do want to improve something, make it so we can hit commence during a NPC-conversation/cutscene or cancel them. As it is now, we can only completely skip the cutscene/conversation or time out the DF. Sure, most cutscenes we can re-watch, but some we can't, and about all normal NPC-conversations (wich often contain valuable info of the story and can be quite long as well) are lost forever if you skip them.

Oh my love.....

Lemme ask where you want the default at, Withdraw? Accept?

If they defaulted on Withdraw then players will accidentally hit with draw and be forced to make the decision to confirm or not.
If they defaulted on Accept then players would be locked into going into a run forcing them to make a decision to stay or get penalized.

"Don't queue for something if you can do the run?"
"Don't organize items in inventories while queued to prevent accidental accept/withdraw?"
"Make sure you're holding Cross Hotbar triggers to prevent accidental accept/withdraw?"
"Don't craft/gather while queued to prevent accidental accept/withdraw?"

You're asking players the above to cater to this nonsense thread request?

This thread was made from ignorance, Yoshi's team does a lot of dumb stuff in this game that is inconsistent with good game design,
but opting to not lock a player into an unexpected window pop is a good choice and the wait option was duly needed.

My tone in this reply simply comes my shock to see this being an issue at all, and I feel that the question of recent generation gamer's lack discipline.
Feel free to express your feedback as is your right, but the consequence of thoughtless requests deliver responses.... like mine?

Quote:

---

Originally Posted by StouterTaru

Why didn't they go with making the pop-up window not steal focus?

If you're interacting with a NPC, or retainer, or marketboard, or gathering node, etc when it pops you are unable to confirm until you disengage, but your clicks now go to the pop-up window instead.

---

This could also be modified to help assist accidental accept/withdraw, whether to place the window as a backdrop and not a focus, or making it just a notice until selected.

Quote:

---

Originally Posted by MyKotoShi

This thread was made from ignorance.

---

If it's ignorant to ask for a QOL change that will give us the option to choose where the default is, then ignorance is bliss. ^^

Quote:

---

Originally Posted by MyKotoShi

"Don't queue for something if you can do the run?"

---

Which is something people do, pre-Wait button.

Quote:

---

Originally Posted by MyKotoShi

"Don't organize items in inventories while queued to prevent accidental accept/withdraw?"

---

Go for it, but half the time if you're organizing inventories, you're doing it from a retainer window that doesn't accept Duty prompts anyway. So moot.

Quote:

---

Originally Posted by MyKotoShi

"Don't craft/gather while queued to prevent accidental accept/withdraw?"

---

As people said, this issue isn't even real since you can't accept even while in the wrong class. As for withdraw, that would've happened anyway.

Quote:

---

Originally Posted by MyKotoShi

This thread was made from ignorance.

---

That would imply that we didn't know any better. Ignorance is not the word you're looking for here. It's better to say laziness, which still isn't a good enough reason for you to post here in an attempt to call us names.

Your post really was made because you wanted to listen to yourself put down a QoL some people want. Just like the Wait button was put in for some people, some other people want the default button to be different. As I stated before, not all of us need training wheels for our duty prompts. We just want the old way back or a means to default it back to something similar to the previous, one button click commence or withdraw.