That definition of option select in the link is very wrong as well. It has nothing to do with the CPU 'choosing the right outcome'. And it's also not exclusively ambiguous either. A safe jump or negative edge command throw in ST is not ambiguous, it's very deliberate. ETTEG protects against high escaped throws, linear attacks, and half circular attacks, all at the same time, the CPU doesn't choose which one is best in that situation, everything is covered already.

Whenever the SRK Wiki gets restored I'll be putting up my massive ST writeup on option selects in the Wiki so look for it.

As far as I know its the correct one. ETTEG isnt an option select and afaik negative edge isnt either. Dunno what safe jump refers to.

ARE in VF4 was an option select...Im pretty sure there were others in older VFs but I cant recall them.

ETEG is an option select....

I think the link described option selects correctly, but did a bit of a poor job describing it in a comprehensive way.

And Manji, evade throw escapes is a textbook example of an option select. You input an evade and a throw escape, what you will actually get depends on what the opponent does. If he throws you will throw escape, if he attacks you will instead get a successful evade. So you only one thing, but got two completely different outcomes depending on what the opponent did (this is what that text meant by the computer choosing the "right" outcome).

For people still confused, here's an example of something that is NOT an option select: A sabaki. Even though it beats both attacks and throws, it can not be considered an option select since no matter what it beats, you will have always gotten out the same thing (the sabaki attack).

So an option select is not so much about covering a lot of options (which the name might imply) as it is a technical term for what I described above, you input one thing but can get two (or more) different things come out depending on what the opponent did.

Hopefully I didn't just further confuse anyone with this poorly written text, it's hard to describe it in writing compared to showing it in the game.

k.

I agree with Jeneric, and I was wrong about ETTEG. I guess I wasnt thinking rationally.

Safe jump is when you knock down the opponent and by inputting 7p on the 1 player side in the right time frame it will enable an option select of:

-Pouncing if opppnent lays there
-Jumping backwards if 2nd player tech rolls

Both work together, but as far as I know the timming is still a mystery to me. If anyone is proficent at this please post up as I have been dying to know.

Thanks

I've never been able to get it to work in VF5, it was simple to do in 4 too so either it's not in VF5 or i'm just n00b.

EDIT: In VF4 you had to input the exact moment your opponent hit the floor otherwise it didn't work, like I said though doesn't seem to work in VF5.

"Safe jump" refers to a technique in 2D fighters.

Thats what I know, Im not exactly sure what it is about. Doing a jump and inputting an attack with b at the end at the correct distance and timing right before landing so that when you land, you block if they do a wakeup DP etc, or hit them if they try something else? Did I get it right?

As for Kaminari_Oyajis version of 'safe pounce', I didnt think it needs any timing at all, just input it as soon as you've recovered from the attack you knocked them down with.. Im not sure because I don't use this, generally I only do pounces when they are guaranteed.

EDIT: To return to Empnovas post,
Thats exactly what it is about, although you are right and the wiki is wrong in that the player input is not ambiguous (Im not sure of semantics here) but rather very deliberate specific input.

ps. That wiki in Leonards link could do with some rewriting.

The word "ambiguous" actually fits the bill quite well since you're doing the one input to get different results. They don't mean that the player didn't mean to do it or that it isn't a deliberate thing to do, they're meaning the technical nature of the input.

Think about it, when you do an ETE you don't know what the outcome will be, hence the ETE is an ambiguous input and the CPU is actually deciding the outcome depending on what the opponent does.