Template:WhiffPunisherTable/doc

	This template uses Cargo:
	Special:CargoTables/Move

	This template uses Lua:
	Module:Move Module:Move/functions Module:Move/game

This page is for Tekken 8. For Tekken 7, see Template:WhiffPunisherTable7.

Displays characters' whiff punishers in a table.

Related templates

{{Move}} - show detailed information for a move and store it in a cargo table.
{{MoveQuery}} - show detailed information for an already defined move.
{{MoveGet}} - get one field of an already defined move.
{{MoveInherit}} - create a new move based on an already defined move. Primary usage - inherit properties of a generic move.
{{PunisherTable}} - show information for character punishers and store them in a cargo table. Depends on the data defined by {{Move}}.
{{PunishmentChart}} - display a chart of punishment damage for a character. Depends on the data defined by {{PunisherTable}}.
{{WhiffPunisherTable}} - show information for character whiff punishers. Depends on the data defined by {{Move}}.

Usage

{{WhiffPunisherTable
|{{o| moveId = Bryan-1,4 }}
|{{o| moveId = Bryan-4,3
    | riskNote = <ref>4,3 is unsafe but can threaten extensions.</ref> }}
|{{o| moveId = Bryan-df+2,1
    | riskNote = <ref>2nd hit is a duckable high at -22.</ref> }}
|{{o| moveId = Bryan-ws3 | speed = i12(~14) }}
|{{o| moveId = Bryan-f,F+2 | speed = i13(~16) }}
|{{o| moveId = Bryan-ws1 | speed = i15(~17) | staple = 77 }}
|{{o| moveId = Bryan-b+4 | mini = 50 | wall = 80 }}
|{{o| moveId = Bryan-f,n,b+2 | speed = i14(~16) | staple = 77 }}
|{{o| moveId = Bryan-Sway.2,4 | speed = i15(~17) | mini = 59
    | riskNote = <ref>qcb+2 on its own is safe at -9 and hard to challenge given the extension CH launches, and qcb+2,4 is delayable enough to [[hit confirm]] off of random whiffs, but not the hit itself.</ref><ref>2nd hit is a duckable high at -32.</ref> }}
|{{o| moveId = Bryan-f+4,1 | staple = 72 }}
|{{o| moveId = Bryan-f,F+4 | staple = 82
    | speed = i17(~20) | speedNote = <ref>f,F+4 more often connects on its second active frame (i17) when used at range.</ref> }}
|{{o| moveId = Bryan-ss1 | speed = i17(~26) | staple = 75 }}
}}

Parameters

Template takes 1 or more unnamed parameters - punishers.

Each punisher is an {{o}} with following parameters:

Parameter	Required	Description
`moveId`	✔︎	Unique id of the move.
`mini`		Max damage of a mini combo, if any. See Template:PunisherTable7#Parameters.
`staple`		Max damage of a staple combo, if any. See Template:PunisherTable7#Parameters.
`wall`		Max damage of a wall combo, if any. See Template:PunisherTable7#Parameters.
`rage`		Max damage of a rage combo, if any. See Template:PunisherTable7#Parameters.
`${column}`		Overrides value of any column: `move` - Overrides move input. See Template:PunisherTable7#Parameters. `speed` - Overrides startup of the move which by default is the 1st active frame. Useful when move is done using motion input or has multiple active frames. Example: Bryan's f,F+4 is i16~19. At range range often connects on 2nd active frame, which makes it i17 at the fastest, and if you count motion input it becomes i17(~20). `range` - Overrides move range. `damage` - Overrides move damage. See Template:PunisherTable7#Parameters. `risk` - Overrides move risk. Example: moves with stance transitions have different advantage with and without a transition. `hitbox` - Overrides move hitbox.
`${column}Note`		Add a note to any of the columns. Notes should be in `ref` tag.

Example

Move	Speed	Range	Damage	Risk	Hitbox
Whiff punishers
1,4	i10	2.30	21	-7	High
4,3	i12	2.24	27	-10^[1]	High
df+2,1	i13	2.23	23	-4^[2]	Mid
ws3	i12(~14)	2.32	18	-10	Mid
f,F+2	i13(~16)	~3.05	32	-9	High
ws1	i15(~17)	2.24	20 (77)	-16	Mid
b+4	i16	2.18	18 (50/79)	-10	Mid
f,n,b+2	i14(~16)	2.43	20 (77)	-7	High
qcb+2,4	i15(~17)	2.72	41 (59)	-9^[3]^[4]	Mid
f+4,1	i18	2.71	20 (72)	-13c	Mid
f,F+4	i17(~20)^[5]	~2.9	32 (50)	-9c	High
ss1	i17(~26)	~3.1	23 (75)	-5	High

↑ 4,3 is unsafe but can threaten extensions.
↑ 2nd hit is a duckable high at -22.
↑ qcb+2 on its own is safe at -9 and hard to challenge given the extension CH launches, and qcb+2,4 is delayable enough to hit confirm off of random whiffs (but not the hit itself).
↑ 2nd hit is a duckable high at -32.
↑ f,F+4 more often connects on its second active frame when used at range.

[1] 4,3 is unsafe but can threaten extensions.

[2] 2nd hit is a duckable high at -22.

[3] qcb+2 on its own is safe at -9 and hard to challenge given the extension CH launches, and qcb+2,4 is delayable enough to hit confirm off of random whiffs (but not the hit itself).

[4] 2nd hit is a duckable high at -32.

[5] ,F+4 more often connects on its second active frame when used at range.

[1]

[2]

[3]

[4]

[5]