The input buffer allows the player to send inputs when they can't actâsuch as during recovery or blockstunâand have the input act is if it were sent exactly as they can to act. This is what enables frame advantages to play out in a consistent way, since both players are almost guaranteed to get frame perfect timing on their follow ups. For example, it allows -10 moves to be punished by i10 attacks without frame perfect inputs.
Timing
The input buffer is 8 frames long. This gives an effective 9 frame window to input a frame perfect link.
For example, the following inputs both do a generic 1 jab twice in a row as quickly as possible:
| Active frame | |
| Recovery | |
| Input buffer |
Motion inputs
Non-stance motion inputs can be buffered. For these, the 8 frame window is only concerned with the last input in the sequence, with the timing window of the motion input itself independent of the input buffer.
For example, Kazumi's b,n,f+2 can at most be input in 15 frames:
So the b can be âbufferedâ for up to 22 frames:
Unbufferable moves
As a general rule, moves that aren't bufferable are those which come out of a stance. If you aren't in that stance while recovering, you can't buffer the moves for that stance. In addition, for most stances entered by motion inputs, entering the stance also can't be buffered.
For the generic dash stance entered by f,f, the first f can be buffered, but the second cannot. This obeys the rules for motion inputs as above, so it can be âbufferedâ for up to 20 frames, as that's the biggest gap between the two f's that is normally permitted.
A move not being bufferable means that it can't be easily used as a punisher, follow up, counter-attack, or in combos, since getting the move out may require near frame perfect timing.