3rd strike command. is this bug or intend?

[kumito]

while practing i found out that moves list command does not have to be exact…
wodering if this is bug or intend…

for examples…

1. Hadoken cancel into SA3command supposed to be… QCF Punch, QCFx2 Kick
   but this works also… QCF Punch, QCF Kick

2. Shoryuken
   ↓:arrow_lower_left:↓:arrow_lower_right:↓:arrow_lower_left:↓:arrow_lower_right: Punch or…
   (charge)↓:arrow_lower_right:↓:arrow_lower_left:↓:arrow_lower_right: Punch

why!!! why???

p.s. im pretty sure this is nothing new to u guys… but is there a place where i can find all those alternative commands available? thx~

[SephirothDVR]

What you are mentioning in 1. is buffering: ie. the game engine remembers the first QCF for the Hado and only requires one more QCF to register QCF x2 for the SA3.

2. Sounds like input leniency. I don’t know how lenient the 3rd Strike engine is, SF4 is VERY lenient. This means that instead of →↓:arrow_lower_right: P for Shoryuken you can do ↓:arrow_lower_right: P (Not sure if 3rd Strike requires a clean → at the beginning but from what you described I take it, it doesn’t have to.) The reason it comes out while you are doing all the other weird motions, is that the engine picks up the needed ↓:arrow_lower_right: and ignores the rest. Also, that (charge) you mentioned is not needed at all.

here is someone who worded it a lot better than me in another thread:

What is buffering?

Buffering usually means taking advantage of the game’s input system by storing inputs in the game’s input buffer so that they can be used to execute a command at a later stage (usually only a few frames afterwards). Buffering makes certain moves easier to perform and is used to perform combos.

A few examples:
[list]
[*]To do a perform Zangief’s super without jumping, you can dash forward, then buffer the 720 command during the dash and then press punch when the dash ends.

[*]With Ryu (full super meter), if you do :qcf: + :p:, :qcf: + :p: you will get a fireball cancelled into his super. You get the super because the first :qcf: is still in the input buffer (ie. it’s “buffered”), so the motion the game “sees” is :qcf::qcf:.

[*]To perform fireball FADC, you only need to tap forward once after the fireball to get the dash cancel because the :qcf: of the fireball is buffered, so it uses the forward motion as the first input of the dash.
[/list]

"2MK36P236P"
The numbers refer to directions. Use the numeric keypad on your keypad as a reference. MK means medium kick and P means punch

This translates to:
:d::mk::df::r::p::qcf::p:

[Komatik]

All fighting games have a so-called input buffer. What it is is essentially the game remembering the last X frames of inputs that you’ve done. It’s what makes special moves possible. You press a button and the game checks what you pressed in the last few moments, ie. it sees you press forward+punch, and sees down, downforward and forward in the buffer => You get a fireball.

The super comes out because:
qcf+P [game checks, sees qcf in memory] => validates as fireball
qcf+K [game checks again, sees qcf, qcf in memory if you did it fast enough] => validates as SAIII, Ken is still doing fireball but it’s okay to cancel fireball into super => Ken stops the fireball recovery and does the super.

[JohnsoN_BCJ]

What you are mentioning in 1. is buffering: ie. the game engine remembers the first QCF for the Hado and only requires one more QCF to register QCF x2 for the SA3.

2. Sounds like input leniency. I don’t know how lenient the 3rd Strike engine is, SF4 is VERY lenient. This means that instead of →↓:arrow_lower_right: P for Shoryuken you can do ↓:arrow_lower_right: P (Not sure if 3rd Strike requires a clean → at the beginning but from what you described I take it, it doesn’t have to.) The reason it comes out while you are doing all the other weird motions, is that the engine picks up the needed ↓:arrow_lower_right: and ignores the rest. Also, that (charge) you mentioned is not needed at all.

here is someone who worded it a lot better than me in another thread:

What is buffering?

Buffering usually means taking advantage of the game’s input system by storing inputs in the game’s input buffer so that they can be used to execute a command at a later stage (usually only a few frames afterwards). Buffering makes certain moves easier to perform and is used to perform combos.

A few examples:
[list]
[*]To do a perform Zangief’s super without jumping, you can dash forward, then buffer the 720 command during the dash and then press punch when the dash ends.

[*]With Ryu (full super meter), if you do :qcf: + :p:, :qcf: + :p: you will get a fireball cancelled into his super. You get the super because the first :qcf: is still in the input buffer (ie. it’s “buffered”), so the motion the game “sees” is :qcf::qcf:.

[*]To perform fireball FADC, you only need to tap forward once after the fireball to get the dash cancel because the :qcf: of the fireball is buffered, so it uses the forward motion as the first input of the dash.
[/list]

"2MK36P236P"
The numbers refer to directions. Use the numeric keypad on your keypad as a reference. MK means medium kick and P means punch

This translates to:
:d::mk::df::r::p::qcf::p:

3S feels a bit more strict to me, but it’s not that bad…

[d3v]

2 is straight up input leniency, 3rd Strike actually has leniency on its DPs as well (which people tend to forget).