View source for Template:Move/doc

{{Uses Cargo|Special:CargoTables/Move}}
{{Lua|Module:Move|Module:Move/functions|Module:Move/game}}
{{Hatnote|This page is for ''Tekken 8''. For ''Tekken 7'', see [[Template:Move7]].}}

This template is used to show detailed information for a single move and store that information in a [https://www.mediawiki.org/wiki/Extension:Cargo Cargo] table. It should only be used in movelists.

The first use of this on any page should include {{tl|MoveDataHeader}} before it.

{{Move/doc/related}}

== Usage ==

Be sure to be familiar with [[Movelist]] to know what appropriate values are.

<syntaxhighlight lang="html">
{{MoveDataHeader}} <!-- Include this at least once on every page using MoveData -->
{{Move
|id=Lee-uf+3
|parent=
|input=uf+3
|target=m
|damage=12
|startup=i25~26
|block=-9
|hit=+2
|crush=js12~
|recv=r27
|tot=53
|range=3.09
|tracksLeft=18
|tracksRight=9
}}
{{Move
|id=Lee-uf+3,1
|parent=Lee-uf+3
|input=,1
|name=Brilliant Rosé
|target=,m
|damage=,18
|startup=,i21~22
|block=-12
|hit=+3
|ch=[[Lee combos#Staples|+26a]]
|recv=r30 FC
|tot=78
|range=4.27
|notes={{Plainlist|
* Floor break
* Combo from 1st hit}}
}}
</syntaxhighlight>

For frame advantages:

* Link to the combo page if it leads to a combo (even if the page doesn't exist yet).
* Always write +0. Do NOT use -0 or 0 without an operator.

== Parameters ==

All parameters are blank by default and can be left blank without issue. However, every move should at least have an <code>id</code> and <code>input</code>.

{| class="wikitable"
! Parameter !! Required !! Description !! Example
|-
| <code>id</code>
| {{Ya}}
| A unique id for the move. Usually equal to <code>${fighterName}-${fullInput}</code>.
|
* <code>Jin-1,2,3</code>
* <code>King-df+1</code>
|-
| <code>parent</code>
|
| The parent of the move, if any. Usually this is previous move in the string. Parent move itself must be defined before its child.
| <code>Jin-1,2</code> is a parent of <code>Jin-1,2,3</code>.
|-
| <code>input</code>
| {{Ya}}
| The primary canonical input of the move, not including previous moves in the string. This should not include any aliases or alternates, which are indicated by <code>alias</code> and <code>alt</code> respectively.

Start with a comma if there were previous moves. Start with a <code>:</code> or <code>~</code> instead if that's what the notation calls for, but write the colon as <code>&amp;#58;</code> or it'll break things.
| rowspan="3" |
* <code>Jin-1,2,3</code> has <code>input=,3</code>
* <code>Jin-b+1+3</code> has <code>input=b+1+3</code> and <code>alt=b+2+4</code>
* <code>Jin-b,n,f+2</code> has <code>input=b,n,f+2</code> and <code>alias=b,f+2</code>
* <code>Jin-b,n,f+2,3</code> has <code>input=,3</code> and <code>alias=b,f+2,3</code>
* <code>Lee-d+4,d+4</code> has <code>input=,d+4</code> and <code>alias=D+4,4</code>
|-
| <code>alias</code>
|
| '''NOT YET IMPLEMENTED'''

Any non-canonical ways of notating the move's input. For strings, this is written in full. If there is more than one alias, use a {{tl|Dotlist}}.

Most common case is non-standard stance abbreviations and short forms for motion inputs.

This is used by frame data bots and other search tools to find the move. It also shows in the movelist notes as "Sometimes written [...]".
|-
| <code>alt</code>
|
| '''NOT YET IMPLEMENTED'''

Any alternate inputs that also perform the same move. For strings, this is written in full. If there is more than one alternate input, use a {{tl|Dotlist}}.

Most common case is jumping and crouching moves where f or b don't affect the move, and for parries where 1+3 and 2+4 both work.

When the alternate input would place the move somewhere else in the movelist, or when it's not clear which is the primary input, such as with {{fl|Claudio}}'s FC.df+2 and f,F+2, it's usually better to copy it with {{tl|MoveInherit}}, with both entries listing the others as alternates.

This shows in the movelist notes as "Alternate input [...]".
|-
| <code>name</code>
|
|
The name of the move, if any.

This can come from the in-game movelist, but if there is a more commonly used name that may be used instead.

For strings, if the in-game movelist has multiple parts of the string named, this should be split as appropriate (see examples).

If there is no name, leave this blank. Do not generate one from the whole string's name, such as by calling {{fl|Lidia}}'s f+1+2,3,2 "Political Storm (3)". However, making a name up is acceptable.
|
* In-game movelist calls 1,2,4 "Left Right > Mid Kick", so
** <code>Lee-1,2</code> has <code>name=Left Right</code>
** <code>Lee-1,2,4</code> has <code>name=Mid Kick</code>
* <code>Lee-1,3:3</code> has <code>name=</code> (blank)
* <code>Lee-1,3:3:3</code> has <code><nowiki>name=[[Acid Rain]]</nowiki></code>
|-
| <code>target</code>
|
| The hit level of the move, not including previous moves in the string. Start with a comma if there were previous moves.
|-
| <code>damage</code>
|
| The damage of the move, not including previous moves in the string. Start with a comma if there were previous moves.
|-
| <code>startup</code>
|
| The startup of the move, not including previous moves in the string. Start with a comma if there were previous moves. Leave blank if you don't want to measure it. 
|-
| <code>block</code>
|
| The frame advantage on block.
|-
| <code>hit</code>
|
| The frame advantage on hit.
|-
| <code>ch</code>
|
| The frame advantage on counter-hit. Leave blank if the same as on hit.
|-
| <code>crush</code>
|
| The frames where this move will crush, powercrush, or parry.
|-
| <code>recv</code>
|
| The number of frames the move takes to recover, starting with an r. Indicate the state after recovery if the move doesn't recover standing.
|-
| <code>tot</code>
|
| The total number of frames for the whole move. For strings, this count is from the start of the string with no delays.
|-
| <code>range</code>
|
| The range of the move, as per [[Movelist#Range]].
|-
| <code>tracksLeft</code>
|
| The tracking score, as per [[Tracking#Measurement]], to the attacker's left (i.e. opponent steps right).
|-
| <code>tracksRight</code>
|
| The tracking score, as per [[Tracking#Measurement]], to the attacker's right (i.e. opponent steps left). 
|-
| <code>notes</code>
|
| Anything that doesn't fit elsewhere. See also {{tl|MoveDataIcon}}.
|}

If the <code>name</code>, <code>startup</code>, <code>crush</code>, or <code>notes</code> parameters have multiple values, use a {{tl|Plainlist}}. Exception is if the <code>startup</code> is two short values and it would look better with a space instead of a line break.

<syntaxhighlight lang="html">
|startup=i55 i68
|crush={{Plainlist|
* cs25~45
* js45~}}
|notes={{Plainlist|
* Homing
* Tailspin}}
</syntaxhighlight>

== Data entry ==

The simplest way to enter the data is to copy this and fill in the blanks:

<syntaxhighlight lang="html">{{Move
|id=
|parent=
|input=
|name=
|target=
|damage=
|startup=
|block=
|hit=
|ch=
|crush=
|recv=
|tot=
|range=
|tracksLeft=
|tracksRight=
|notes=
}}
</syntaxhighlight>

== Example ==

<!-- MoveDisplay is used instead of Move to render the example without storing any data -->
{{MoveDataHeader}}
{{MoveDisplay
|id=Lee-uf+3
|input=uf+3
|target=m
|damage=12
|startup=i25~26
|block=-9
|hit=+2
|crush=js12~
|recv=r27
|tot=53
|range=3.09
|tracksLeft=18
|tracksRight=9
}}
{{MoveDisplay
|id=Lee-uf+3,1
|inputLead=uf+3
|input=,1
|parent=Lee-uf+3
|name=Brilliant Rosé
|target=,m
|damage=,18
|startup=,i21~22
|block=-12
|hit=+3
|ch=[[Lee combos#Staples|+26a]]
|recv=r30 FC
|tot=78
|range=4.27
|notes={{Plainlist|
* Floor break
* Combo from 1st hit}}
|targetLead=m
|damageLead=12
|startupRoot=i25~26
}}