Instant while running

Instant while running (iWR) is a technique to do running moves at close range.

Timing

Despite the name, iWR has nothing to do with being fast.

	Standing
	Dashing
	Running

Fastest possible iWR, minimal input

Frame

Input

State

1

f

2

n

3

f

4

n

5

f

6

2

Slowest possible iWR, minimal input

Frame

Input

State

1

f

2

n

⋯

n

20

n

21

f

22

n

⋯

n

30

n

31

f

32

2

The key to iWR is that the attack button must be pressed exactly one frame after the third f input.

Button too early, gets f,F+2 instead

Frame

Input

State

1

f

2

f

3

f

4

n

5

n

6

n

7

f

8

f

9

f

10

n

11

n

12

n

13

f2

Succesful iWR

Frame

Input

State

1

f

2

f

3

f

4

n

5

n

6

n

7

f

8

f

9

f

10

n

11

n

12

n

13

f

14

f2

Button too late, gets f+2 instead

Frame

Input

State

1

f

2

f

3

f

4

n

5

n

6

n

7

f

8

f

9

f

10

n

11

n

12

n

13

f

14

f

15

f2

The technique makes use of how the game goes about stopping you from running when the opponent is close. Rather than stopping you from doing a run at all, it simply stops a run immediately after it starts, so there's still one frame where you're in the running stance.

Purpose

Running moves are the most powerful moves for many characters. For example, Kazumi's wr2 deals 25 damage with knockdown and wall splats. The only other safe mid she has with better payoff is f,F+4, which is slower, shorter range, easier to step, and worse on block. She also has wr1 which is +7 on block and deals even more damage.

Even when input quickly, running moves are slow—the input still adds 5 frames minimum to the startup, and more realistically 10+ frames.

Rather than making running moves fast, the purpose of iWR is to make them consistent. They're at their best at around range 2, but it's possible when you go for one that your opponent does a dash (e.g. a dash block) at the same time. If this happens and you don't do iWR, you don't get your running move.

That being said, iWR does make running moves slightly faster, since you'll always be pressing the attack button at the first frame of your run, rather than 2 or 3 frames into it as one might do naturally.

Overusing iWR at close range without a read on your opponent's timing is good way to eat a counter hit, but having the option to use running moves in this situation is still useful, especially when at the wall.

Buffered

Example of buffer into iWR.2. The purple square in the overlay shows the first frame after recovery. Note how early the first f is buffered.

You can buffer the first f of an iWR. This makes it a lot faster and thus more of a threat when combined with a big frame advantage. Doing this is a bit harder as now the second f input must also be timed well—exactly as you recover. If you press it too early you'll get the wrong move, and later will be slower.