Instant while running: Difference between revisions

From Wavu Wiki, the 🌊 wavy Tekken wiki
VisualWikitext
(Created page with "f, n, f, n, [exactly 1 frame of f], f+2. Here is what it looks like when done perfectly: File:iwr2History.png The duration of the first and second forward, as well as the...")
 
No edit summary
 
(25 intermediate revisions by 5 users not shown)
Line 1: Line 1:
f, n, f, n, [exactly 1 frame of f], f+2. Here is what it looks like when done perfectly:
'''Instant while running''' ('''iWR''' or '''iwr''') is a technique to do [[run]]ning moves at close range(closer than range at which your character starts running by just pressing f,n,f).  
[[File:iwr2History.png]]


The duration of the first and second forward, as well as the duration of the neutral frames can vary in order to still perform the iWR2, however, pressing 2 exactly one frame after the third forward is mandatory.
== Tekken 8 Changes==


For the purposes of this guide, I will just say iWR2, but, of course, this can be used for any moves that need to be executed from a while running state, with a few exceptions.
[[File:Tekken8PointBlankRun.mp4|250px|thumb|right|Extra frames of running are granted on a f,f,F input, even if you are at point blank range.]]
Tekken 8 introduces far more lenient timing for inputting WR moves at point blank, granting additional time in the running state once you hit the opponent. This greatly lowers the execution barrier for including while running moves as part of a core gameplan.
[[File:Tekken8PointBlankRunIntoDelayWR2.mp4|250px|thumb|right|Dragunov's wr2 does not require precise timing at point blank, and can be delayed slightly.]]
While running moves can be input at any point during this running state, allowing for far more lenient timing than that in Tekken 7. Some while running attacks may still reward precise timing with extra damage, such as the blue spark version of [[Dragunov]]'s wr2.


While running moves can be done at range 0 consistently and without that much effort. You don't need to mash forward so fast your life depends on it. The only thing that matters for iWR2 at range 0 is that you press 2 exactly 1 frame after the third f press. If you press them at the same frame, you will get f2. If you have greater than 1 frame delay, you will get f2.
== Timing ==
This is shown here https://gfycat.com/OldfashionedHotAmmonite.


Most of the time, when you are trying to do iWR2, you are doing it after another move, such as a wr2 on block. This can make things easier. The trick here is to buffer the first forward, and then on the first frame when you can act, you press f, n, [exactly one frame of f], f+2. This makes it quite a bit easier, given that you have a very large window to buffer the first f. All you need to focus on is timing of your second f with your first actionable frame, and pressing 2 exactly 1 frame after your third f.  A common way this is messed up is when the second f is pressed before the first actionable frame. When this happens you get ff2. This is shown here:
Despite the name, iWR has nothing to do with being fast.
https://gfycat.com/SarcasticHandmadeCoelacanth


In this frame-by-frame overlay, the frame colored purple, denotes the first frame I can input an action. Take note of how the first f is buffered very early.
{{Legend|float=right
|blue=Standing
|orange=Dashing
|green=Running}}{{FrameTable|caption=Fastest possible iWR, minimal input|
{{Frame|1|f}}
{{Frame|2|n}}
{{Frame|3|f}}
{{Frame|4|n|orange}}
{{Frame|5|f|orange}}
{{Frame|6|2|green}}
}}
{{FrameTable|caption=Slowest possible iWR, minimal input|
{{Frame|1|f}}
{{Frame|2|n}}
{{Frame||n}}
{{Frame|20|n}}
{{Frame|21|f}}
{{Frame|22|n|orange}}
{{Frame||n|orange}}
{{Frame|30|n|orange}}
{{Frame|31|f|orange}}
{{Frame|32|2|green}}
}}<div style="display: flex; flex-flow: row wrap; gap: 0 1em"></div>
 
The key to consistently do iWR moves at point-blank range is to press the attack button one frame after the third f input.
 
<div class="frame-table-group">
{{FrameTable|caption=Attack button pressed too early, gets f,F+2 instead|
{{Frame|1|f}}
{{Frame|2|f}}
{{Frame|3|f}}
{{Frame|4|n}}
{{Frame|5|n}}
{{Frame|6|n}}
{{Frame|7|f}}
{{Frame|8|f|orange}}
{{Frame|9|f|orange}}
{{Frame|10|n|orange}}
{{Frame|11|n|orange}}
{{Frame|12|n|orange}}
{{Frame|13|f2|orange}}
}}
{{FrameTable|caption=Succesful iWR|
{{Frame|1|f}}
{{Frame|2|f}}
{{Frame|3|f}}
{{Frame|4|n}}
{{Frame|5|n}}
{{Frame|6|n}}
{{Frame|7|f}}
{{Frame|8|f|orange}}
{{Frame|9|f|orange}}
{{Frame|10|n|orange}}
{{Frame|11|n|orange}}
{{Frame|12|n|orange}}
{{Frame|13|f|orange}}
{{Frame|14|f2|green}}
}}
{{FrameTable|caption=Button too late, gets f+2 instead(applies only to point-blank range)|
{{Frame|1|f}}
{{Frame|2|f}}
{{Frame|3|f}}
{{Frame|4|n}}
{{Frame|5|n}}
{{Frame|6|n}}
{{Frame|7|f}}
{{Frame|8|f|orange}}
{{Frame|9|f|orange}}
{{Frame|10|n|orange}}
{{Frame|11|n|orange}}
{{Frame|12|n|orange}}
{{Frame|13|f|orange}}
{{Frame|14|f|green}}
{{Frame|15|f2|blue}}
}}
 
The attack button one frame after the third f input only required at point-blank range. At any range besides point-blank range there is no need to input the attack button one frame after the third f input as shown in the video:[[File:Iwr2.mp4|none|thumb]]
</div>
 
The input overlay was modified to show inputs on per-frame basis. As you can see on one of the frames of the video:[[File:Tekken 7 Dragunov iwr2 frame.png|thumb|alt=|none]]
 
Dragunov did iwr2 at very close range but I did not enter the '''''2''''' input one frame after the third '''''f'''''. I only entered '''''2''''' two frames after the third '''''f'''''.
 
The iWR technique makes use of how the game goes about moving you to a running state and stopping you from running when you hit the opponent with your dash. Rather than stopping you from doing a run at all, the game always switches to a running state after you press third '''''f''''', and only switches your character back to a standing state after it hits the opponent with its model, so there's always at least one frame where you're in the running state.
== Purpose ==
 
Running moves are powerful. 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.
 
Rather than making running moves ''fast'', the purpose of iWR is to make them possible at range that is less than range at which your character starts running on its own after entering '''''f,n,F'''''. 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.
 
Even when input quickly, running moves are slow—the input still adds 5 frames minimum to the startup, and more realistically 10+ frames.
 
iWR does make running moves ''slightly'' faster when you press the attack button at the first frame of your run compared to 2 or 3 frames into it as one might do often.
 
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 also useful, especially when at the wall.
 
== Buffered ==
 
[[File:Ff2InsteadOfWR2Example.mp4|250px|thumb|right|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 [[input buffer|buffer]] '''''f,n''''' inputs of iWR. This makes it 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 should only be entered after your character recovers. If you press second '''''f''''' too early(before your character recovers) you'll get the wrong move, and later will be slower.
 
<div style="clear: both"></div>
 
{{Navbox system}}

Latest revision as of 10:14, 1 March 2024

Instant while running (iWR or iwr) is a technique to do running moves at close range(closer than range at which your character starts running by just pressing f,n,f).

Tekken 8 Changes

Extra frames of running are granted on a f,f,F input, even if you are at point blank range.

Tekken 8 introduces far more lenient timing for inputting WR moves at point blank, granting additional time in the running state once you hit the opponent. This greatly lowers the execution barrier for including while running moves as part of a core gameplan.

Dragunov's wr2 does not require precise timing at point blank, and can be delayed slightly.

While running moves can be input at any point during this running state, allowing for far more lenient timing than that in Tekken 7. Some while running attacks may still reward precise timing with extra damage, such as the blue spark version of Dragunov's wr2.

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 consistently do iWR moves at point-blank range is to press the attack button one frame after the third f input.

Attack button pressed 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(applies only to point-blank range)
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 attack button one frame after the third f input only required at point-blank range. At any range besides point-blank range there is no need to input the attack button one frame after the third f input as shown in the video:

The input overlay was modified to show inputs on per-frame basis. As you can see on one of the frames of the video:

Dragunov did iwr2 at very close range but I did not enter the 2 input one frame after the third f. I only entered 2 two frames after the third f.

The iWR technique makes use of how the game goes about moving you to a running state and stopping you from running when you hit the opponent with your dash. Rather than stopping you from doing a run at all, the game always switches to a running state after you press third f, and only switches your character back to a standing state after it hits the opponent with its model, so there's always at least one frame where you're in the running state.

Purpose

Running moves are powerful. 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.

Rather than making running moves fast, the purpose of iWR is to make them possible at range that is less than range at which your character starts running on its own after entering f,n,F. 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.

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

iWR does make running moves slightly faster when you press the attack button at the first frame of your run compared to 2 or 3 frames into it as one might do often.

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 also 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 f,n inputs of iWR. This makes it 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 should only be entered after your character recovers. If you press second f too early(before your character recovers) you'll get the wrong move, and later will be slower.

Mechanics
Concepts
Techniques
Strategy
Miscellaneous
Retrieved from "https://wavu.wiki/w/index.php?title=Instant_while_running&oldid=23647"
Last modified
This page was last edited on 1 March 2024, at 10:14.
Copyright
All game content, materials, and recordings are copyright and owned by Bandai Namco Entertainment Inc. TEKKEN® is a registered trademark by Bandai Namco Entertainment Inc.. All rights reserved. All other content is available under Creative Commons Zero (Public Domain) unless otherwise noted.