Template:MoveData/doc: Difference between revisions

Template page
No edit summary
(add deprecation note)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Uses TemplateStyles|MoveData/style.css}}
{{Note|Deprecated. Use {{tl|Move7}} instead.}}
{{Uses TemplateStyles|MoveData/style2.css}}


This template is used to show detailed information for a single move. It's mainly used in movelists.
This template is used to show detailed information for a single move. It's mainly used in movelists.
Line 12: Line 13:
{{MoveDataHeader}} <!-- Include this at least once on every page using MoveData -->
{{MoveDataHeader}} <!-- Include this at least once on every page using MoveData -->
{{MoveData
{{MoveData
|id=u/f+3
|id=Lee-uf+3
|input=u/f+3
|input=uf+3
|target=m
|target=m
|damage=12
|damage=12
Line 22: Line 23:
|crush=js12~
|crush=js12~
|recv=r27
|recv=r27
|tot=53
|block=-9
|block=-9
|hit=+2
|hit=+2
}}
}}
{{MoveData
{{MoveData
|id=u/f+3,1
|id=Lee-uf+3,1
|name=Brilliant Rosé
|name=Brilliant Rosé
|inputLead=u/f+3
|inputLead=uf+3
|input=,1
|input=,1
|targetLead=m
|targetLead=m
Line 38: Line 40:
|startup=,i21~22
|startup=,i21~22
|recv=r30 FC
|recv=r30 FC
|tot=78
|block=-12
|block=-12
|hit=+3
|hit=+3
Line 50: Line 53:


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


== Parameters ==
== Parameters ==
Line 60: Line 63:
|-
|-
| <code>id</code>
| <code>id</code>
| A unique id for the move. Usually equal to <code><nowiki>{{{inputLead|}}}{{{input}}}</nowiki></code>.
| A unique id for the move. Usually equal to <code><nowiki>{{{fighterName}}}-{{{inputLead|}}}{{{input}}}</nowiki></code>.
|-
|-
| <code>name</code>
| <code>name</code>
Line 69: Line 72:
|-
|-
| <code>input</code>
| <code>input</code>
| The input of the move, not including previous moves in the string. 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. -->
| The input of the move, not including previous moves in the string. 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.
|-
|-
| <code>targetLead</code>
| <code>targetLead</code>
Line 100: Line 103:
| <code>crush</code>
| <code>crush</code>
| The frames where this move will crush, powercrush, or parry.
| The frames where this move will crush, powercrush, or parry.
|-
| <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>recv</code>
| <code>recv</code>
Line 114: Line 120:
|-
|-
| <code>notes</code>
| <code>notes</code>
| Anything that doesn't fit elsewhere.
| Anything that doesn't fit elsewhere. See also {{tl|MoveDataIcon}}.
|}
|}


If the <code>name</code>, <code>startup</code> (or <code>startupRoot</code>), <code>crush</code>, or <code>notes</code> parameters have multiple values, use a 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.
If the <code>name</code>, <code>startup</code> (or <code>startupRoot</code>), <code>crush</code>, or <code>notes</code> parameters have multiple values, use a 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.
Leaving fields blank is fine, especially ones that take a while or are difficult to measure such as <code>range</code>, <code>tracksLeft</code>, and <code>tracksRight</code>.


<syntaxhighlight lang="html">
<syntaxhighlight lang="html">
Line 130: Line 134:
* Tailspin}}
* Tailspin}}
</syntaxhighlight>
</syntaxhighlight>
== Data entry ==
The simplest way to enter the data is to copy this and fill in the blanks:
<syntaxhighlight lang="html">{{MoveData
|id=
|name=
|inputLead=
|input=
|targetLead=
|target=
|damageLead=
|damage=
|range=
|tracksLeft=
|tracksRight=
|startupRoot=
|startup=
|crush=
|recv=
|block=
|hit=
|ch=
|notes=
}}
</syntaxhighlight>
However, you might prefer using a spreadsheet. In that case, you can use [https://docs.google.com/spreadsheets/d/1TsKSmzZSekxkxobL1RpfD4PUS-se2JsMq8ajIylDuvM/edit this spreadsheet] to convert to wikitext automatically. This is not recommended, but it's there if you must.


== Example ==
== Example ==
Line 135: Line 168:
{{MoveDataHeader}}
{{MoveDataHeader}}
{{MoveData
{{MoveData
|id=u/f+3
|id=Lee-uf+3
|input=u/f+3
|input=uf+3
|target=m
|target=m
|damage=12
|damage=12
Line 145: Line 178:
|crush=js12~
|crush=js12~
|recv=r27
|recv=r27
|tot=53
|block=-9
|block=-9
|hit=+2
|hit=+2
}}
}}
{{MoveData
{{MoveData
|id=u/f+3,1
|id=Lee-uf+3,1
|name=Brilliant Rosé
|name=Brilliant Rosé
|inputLead=u/f+3
|inputLead=uf+3
|input=,1
|input=,1
|targetLead=m
|targetLead=m
Line 161: Line 195:
|startup=,i21~22
|startup=,i21~22
|recv=r30 FC
|recv=r30 FC
|tot=78
|block=-12
|block=-12
|hit=+3
|hit=+3

Latest revision as of 17:50, 19 September 2023

Deprecated. Use {{Move7}} instead.

This template is used to show detailed information for a single move. It's mainly used in movelists.

The first use of this on any page should include Template:MoveDataHeader before it.

Usage

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

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

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 id and input.

Parameter Description
id A unique id for the move. Usually equal to {{{fighterName}}}-{{{inputLead|}}}{{{input}}}.
name The name of the move, if any.
inputLead The input of the previous moves in the string, if any.
input The input of the move, not including previous moves in the string. Start with a comma if there were previous moves. Start with a : or ~ instead if that's what the notation calls for, but write the colon as &#58; or it'll break things.
targetLead The hit level of the previous moves in the string, if any.
target The hit level of the move, not including previous moves in the string. Start with a comma if there were previous moves.
damageLead The damage of the previous moves in the string, if any.
damage The damage of the move, not including previous moves in the string. Start with a comma if there were previous moves.
range The range of the move, as per Movelist#Range.
tracksLeft The tracking score, as per Tracking#Measurement, to the attacker's left (i.e. opponent steps right).
tracksRight The tracking score, as per Tracking#Measurement, to the attacker's right (i.e. opponent steps left).
startupRoot The startup of the first move in the string, if this isn't the first move.
startup 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.
crush The frames where this move will crush, powercrush, or parry.
tot The total number of frames for the whole move. For strings, this count is from the start of the string with no delays.
recv 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.
block The frame advantage on block.
hit The frame advantage on hit.
ch The frame advantage on counter-hit. Leave blank if the same as on hit.
notes Anything that doesn't fit elsewhere. See also {{MoveDataIcon}}.

If the name, startup (or startupRoot), crush, or notes parameters have multiple values, use a Plainlist. Exception is if the startup is two short values and it would look better with a space instead of a line break.

|startup=i55 i68
|crush={{Plainlist|
* cs25~45
* js45~}}
|notes={{Plainlist|
* Homing
* Tailspin}}

Data entry

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

{{MoveData
|id=
|name=
|inputLead=
|input=
|targetLead=
|target=
|damageLead=
|damage=
|range=
|tracksLeft=
|tracksRight=
|startupRoot=
|startup=
|crush=
|recv=
|block=
|hit=
|ch=
|notes=
}}

However, you might prefer using a spreadsheet. In that case, you can use this spreadsheet to convert to wikitext automatically. This is not recommended, but it's there if you must.

Example

Name
Alt

Input

Hit level
Damage
Range
Left Tracking
Right Tracking
Block
Hit
CH
Startup
States
Recovery
Notes

uf+3

m
12
3.09
18
9
-9
+2
i25~26
js12~
t53 r27
Brilliant Rosé

uf+3,1

m,​m
12,​18
4.27
-12
+3
i25~26
,i21~22
t78 r30 FC
  • Floor break
  • Combo from 1st hit