Template:MoveData2/doc: Difference between revisions

Template page
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Note|This is an experimental template by [[User:Oldmanwang]] ([[Special:Contributions/Oldmanwang|c]]). It should not be used in the main namespace at this time.}}
{{Uses TemplateStyles|MoveData/style3.css}}
{{Uses TemplateStyles|MoveData/style3.css}}



Latest revision as of 06:17, 6 July 2021

This is an experimental template by User:Oldmanwang (c). It should not be used in the main namespace at this time.

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:MoveDataHeader2 before it.

Usage

Get familiar with the Movelist to know what appropriate values are.

{{MoveDataHeader2}} <!-- Include this at least once on every page using MoveData -->
{{MoveData2
|id=Lee-u/f+3
|input=u/f+3
|target=m
|damage=12
|range=3.09
|startup=i25~26
|crush=js12~
|recv=r27
|block=-9
|hit=+2
}}
{{MoveData2
|moveNo=72
|id=Lee-u/f+3,1
|name=Brilliant Rosé
|inputLead=u/f+3
|input=,1
|targetLead=m
|target=,m
|damageLead=12
|damage=,18
|range=4.27
|startupRoot=i25~26
|startup=,i21~22
|recv=r30 FC
|block=-12
|hit=+3
|ch=[[Lee combos#Staples|+26a]]
|combo=1.hit
|floor=F!
|notes=
}}

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
moveNo
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.
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.
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.
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).
range The range of the move, as per Movelist#Range.
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.
crush The frames where this move will crush, powercrush, or parry.
screw Initiates tailspin/screw.
wall Wall splats or bounds.
floor Initiates a floor break?
combo From what hit/ch does the string become guaranteed?
jail Jails from last hit.
leeway Number of frames by which input can be delayed.
delay Number of frames by which move can be delayed.
notes Anything that doesn't fit elsewhere.

If the name, startup (or startupRoot), or crush parameters have multiple values, use a comma. If the notes parameter has multiple lines, use a Plainlist.

|startup=i55,i68
|crush=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:

Basic entry:
{{MoveData2
|moveNo=
|id=
|name=
|inputLead=
|input=
|targetLead=
|target=
|damageLead=
|damage=
|startupRoot=
|startup=
|block=
|hit=
|ch=
|notes=
}}
Comprehensive entry:
{{MoveData2
|moveNo=
|id=
|name=
|inputLead=
|input=
|targetLead=
|target=
|damageLead=
|damage=
|startupRoot=
|startup=
|block=
|hit=
|ch=
|tracksLeft=
|tracksRight=
|range=
|recv=
|crush=
|screw=
|wall=
|floor=
|combo=
|jail=
|leeway=
|delay=
|notes=
}}

Note that the parameters don't have to be listed in sequence.

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

u/f+3
m  |  12
i25~26
-9
+2
3.09
r27
js12~
72
Brilliant Rosé
u/f+3,​1
m,​m  |  12,​18
i25~26,​i21~22
-12
+3
4.27
r30 FC
F!
1.hit