Wait as Default on Controllers

[sarehptar]

I've odd my static members did this just last night even we we're to enter the fcob. Window to enter popped as he was moving through a menu and he cancelled the queue.

You just undermined your own argument though--if this happened just last night, that means it's still possible to misclick, even with "Wait" as the default. So what is the point of even having Wait? It literally does nothing.

[Niwashi]

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

This would have been a far better solution. What's more, it would be a solution to a number of different windows in addition to just the DF one. (Like accidentally cancelling a trade because you were typing in chat at the time the trade window popped up, or accidentally accepting a teleport because you were doing something else at the time, or accidentally accepting/declining FC/Party/Friend invites, etc.)

Pop-up windows should only appear and make their notification noise when their event is triggered. You should have to manually switch to that window before it gets controller or keyboard focus. That would fix all these problems more effectively than a "Wait" button.

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.

It's certainly not among the more commonly complained about issues, but I have seen complaints about various issues caused by pop-up windows (including the DF one, as well as the others I mentioned above) stealing focus and taking your next button press or keystroke as if it was a response to the pop-up instead of to whatever you'd been in the middle of doing at the time.

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.

Agreed. This is badly needed. We should be able to cancel conversations in the middle and have any related quests treat the conversation as not having been started. That way we could go back and do the conversation another time when we have time for the whole thing.

[Mutemutt]

I actually like having wait as the default. There's been plenty of times in the past where I've accidentally confirmed because I was about to target something and the duty window pops up. Or the times where I'm fiddling with gear and inventory, same story. It's relatively rare compared to how often I use the x button, but happened often enough to be fairly annoying.

You just undermined your own argument though--if this happened just last night, that means it's still possible to misclick, even with "Wait" as the default. So what is the point of even having Wait? It literally does nothing.

The fcob confirmation window doesn't have wait as a default option, well, not in the standard way. It basically gives you a "yes, enter" and a "no, cancel". No undermining here.

[sarehptar]

The fcob confirmation window doesn't have wait as a default option, well, not in the standard way. It basically gives you a "yes, enter" and a "no, cancel". No undermining here.

Then why is that person bringing that up as an example here? In that case, it's just totally irrelevant to the situation, which is defaulting to wait in places where defaulting to wait actually happens...

[Mutemutt]

Then why is that person bringing that up as an example here? In that case, it's just totally irrelevant to the situation, which is defaulting to wait in places where defaulting to wait actually happens...

Well, that's how the duty window used to be for all the dungeons. Essentially, it's the past system, and the flaw still shows up, even when the entire group has gathered up knowing that the window will pop soon, the system that some seem to argue that they had absolutely no problem with. It's exactly what some of the posters are asking for; seems relevant to me.

[sarehptar]

Well, that's how the duty window used to be for all the dungeons. Essentially, it's the past system, and the flaw still shows up, even when the entire group has gathered up knowing that the window will pop soon, the system that some seem to argue that they had absolutely no problem with. It's exactly what some of the posters are asking for; seems relevant to me.

As has been stated many times on this thread, it certainly doesn't seem to me that anyone is arguing for a total return to the old methods; clearly, people are asking for an option to select which button will be the default. Definitely no one has said "I want the FCOB of Yes/No" feature everywhere... -.- Furthermore, maybe there isn't a "confirm withdrawal?" option on FCOB, but there is a confirm withdrawal for standard dungeons now, which already protects against this kind of accidental misclicking, meaning that the Wait button is essentially useless for the issue she is describing (accidental withdraw)--on a standard dungeon, when the default was confirm, to accidentally withdraw yourself, you had to press right and then X. With wait defaulted, to accidentally withdraw yourself, you have to press... right and then X! It's exactly the same, so how does adding "Wait" as default in any way protect against accidentally withdrawing from a standard dungeon/trial? It doesn't. Only the added "confirm withdrawal" option does.

It still boggles the mind that anyone would be arguing against giving people more options in this game...

[Cutie_McSnuggles]

It still boggles the mind that anyone would be arguing against giving people more options in this game...

Quoted for truth.

[Mutemutt]

*snip*.

You said it wasn't relevant, I simply told you why it was. Nothing more, nothing less. You kind of just going off on me for pointing out you were mistaken.

And to be fair the wait option does stop you from accidently accepting or accidently dropping out of the queue.

[sarehptar]

You said it wasn't relevant, I simply told you why it was. Nothing more, nothing less. You kind of just going off on me for pointing out you were mistaken.

Your explanation of why it was relevant was fine by me; I got it when you explained it. What I was "going off on" was your comment of "It's exactly what some of the posters are asking for," because, like I said in my post, it seems (to me at least!) that is really not the case, no one is asking for FCOB yes/ no with no other misclick protection options, particularly as there are already other protections (hence why I brought up confirmation withdrawal) that no one is arguing against.

And to be fair the wait option does stop you from accidently accepting or accidently dropping out of the queue.

And part of my post was showing that it doesn't protect against accidentally dropping out in normal dungeons/trials because the number of buttons to accidentally drop out is the exact same as it was when "commence" was the default. It does protect against accidentally commencing before you want to, but a lot of the arguments from people on this thread claiming to have this happen to them (while gathering, while with a retainer, etc.) are actually impossible, so...

Make it an option to select which button you want to be the default, then everyone is happy. Tada. There should literally have been no debate about that at all, is all I'm saying.