Wait as Default on Controllers

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

[Tiggy]

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.

It's a different window.

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

It was just an example of a similar problem and how it happens often. The duty confirmation window until recently shared the same problem. I didn't think this was a leap see what I was getting at here.

If 'you' read this thread you'll notice that it's asking for an option to change the default. Not to change the default for everyone. So... why are you against it?

If you notice I said it to a quote where people just clearly don't get why it was added to begin with. Not against the option.

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

Boggles my mind that you can't see who what I quoted and responded to in terms of the broader argument. I never said a lack of options was bad. Did I? I explained why this was a good feature.

It's like people only read half of what I said.

[sarehptar]

Boggles my mind that you can't see who what I quoted and responded to in terms of the broader argument. I never said a lack of options was bad.

Was I even responding to you anymore? No.

My last point was a general comment that it seems bizarre to me that there even are "two sides" to this issue, given that what is being asked for here is an option, which makes any need for argument completely moot in the first place.

[Cutie_McSnuggles]

My last point was a general comment that it seems bizarre to me that there even are "two sides" to this issue, given that what is being asked for here is an option, which makes any need for argument completely moot in the first place.

LOL Also quoted for truth. And for making me laugh.

If you notice I said it to a quote where people just clearly don't get why it was added to begin with. Not against the option.

Also, sorry Tinggy. I'm just so used to being on the opposite side of discussions with you I automatically assume you don't agree with me. LOL

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

[Mutemutt]

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.

Well I was remembering some of the posts along the lines of "why did they change it" or "they shouldn't have changed it" or some feel similar to that. Looks like I just used the wrong word.

[sarehptar]

Well I was remembering some of the posts along the lines of "why did they change it" or "they shouldn't have changed it" or some feel similar to that. Looks like I just used the wrong word.

Then I'm sorry, I didn't realize you were talking about the people who just didn't like the new change in general; I thought you were actually saying that some people wanted to go to the yes/no with no protections option. Sorry if I seemed like I was personally attacking you or anything!