View source for Template:FrameDataCargo-KOF94/Documentation

<pre>{{FrameDataCargo-KOF94
| moveId = 
| description = 
| phases = 
}}</pre>

==Usage==
This template provides a direct and simple way to display the data stored in the [[Special:CargoTables/MoveData_KOF94|MoveData_KOF94]] cargo table via [[Template:MoveData-KOF94]]. It uses [[Template:FrameData-KOF94]] for moves, [[Template:CharData-KOF94]] for a char's basic action, with data gotten via [[Template:FrameData-KOF94/Query]] and is based on the [[Template:MoveData]] format.

===Main Parameters===

* The move(s)' Id(s), <u>'''moveId'''</u> from which the template will extract the data needed for the table. Up to 10 move Ids are supported.
: Multiple ids should be separated by commas, the template will gather and display images, hitboxes and data for all moves in their given "orderId"s as they were stored in the cargo table.
: ''Note that image/hitbox files of the same name will only be displayed once, at their first iteration.''

* A <u>'''description'''</u> to write in the table under the first move's data.
: Use extra parameters description2 up to description10 for descriptions under the 2nd up to 10th move's data.

* Filling <u>'''phases'''</u> will create an extra tab of that name next to description. It should be used to display and occasionally describe interesting changes in the first move's hitboxes.
: Use extra parameters phases2 up to phases10 to make a phases tab next to the 2nd up to 10th move's description.


===Secondary Parameters===
Secondary parameters are mainly used to change default options depending on the situation's needs.

* The table will use the first move's name and input(s) which may not be what you want. In that case, you can use the <u>'''name'''</u>, <u>'''input'''</u> and/or <u>'''input2'''</u> parameters for the table to use instead.

* Images and hitboxes will be automatically displayed under "Images" and "Hitboxes" tabbers respectively. Use <u>'''tab1'''</u> and <u>'''tab2'''</u> to provide different names for said tabbers.
:* Tabbers disable the auto-resize function of the image block, thus introducing bothersome sliders for bigger images, instead of stretching the block. Use <u>'''size'''</u> to forcibly change the size of the image block. Size preferably written in % (like 20%) or em but px values are accepted.

* All images and hitboxes are displayed in '''175x250px and centered''' (<nowiki>[[File:x.png|175x250px|center]]</nowiki>). You can change that by writing your preferred options separated by commas on the <u>'''display'''</u> parameter. The default display parameter would be {{DocParam|display |175x250px,center}}.
:* To add captions to images and hitboxes use the <u>'''captions'''</u> parameter to write one or multiple captions separated by commas. The first caption will go under the first image/hitbox, the 2nd caption under the 2nd image/hitbox and so on.

* All images and hitboxes are gathered directly from the [[Special:CargoTables/MoveData_KOF94|MoveData_KOF94]] Cargo storage table but the user can enter them manually if preferred using an <u>'''image'''</u> and/or <u>'''hitbox'''</u> parameter. You can also add image2/hitbox2 up to image10/hitbox10 parameters.
:* Doing this disables the display parameter. However you can then change an image/hitbox's display size with <u>'''imageSize'''</u> and/or <u>'''hitboxSize'''</u> keeping the same additional imageSize2 and/or hitboxSize2 up to the 10th parameter for each image/hitbox.
:* Doing this disables the caption parameter. However you can then add a caption to an image/hitbox with <u>'''caption'''</u> keeping the same additional caption2 up to caption10 for each image/hitbox.


==Examples==
Examples made with the 02UM cargo but the 94 version has identical features. All the data necessary here had been declared first in Kyo's [[The_King_of_Fighters_2002_UM/Kyo_Kusanagi/Data|data subpage]].

* Case 1: Simple table with one move and no secondary parameters.
{{FrameDataCargo-KOF02UM
|moveId=kyo_sta
|description=
<br>
A cancelable standing jab with poor priority but decent range and speed. Can be used to stuff hops early but a well timed st.B is generally preferred.<br>
<br>
* Cancelable on hit/whiff.
* Chains into every lights but cl.A/B.
|phases=
<gallery mode=packed-hover heights=150px>
File:02UM_Kyo_st.A_1.png|'''Startup'''
File:02UM_Kyo_st.A_2.png|'''Active'''
</gallery>
}}
<div class="toccolours mw-collapsible mw-collapsed" style="width:500px">
<div style="font-weight:bold;line-height:1.6;">Source</div>
<pre class="mw-collapsible-content">
{{FrameDataCargo-KOF02UM
|moveId=kyo_sta
|description=
<br>
A cancelable standing jab with poor priority but decent range and speed. Can be used to stuff hops early but a well timed st.B is generally preferred.<br>
<br>
* Cancelable on hit/whiff.
* Chains into every lights but cl.A/B.
|phases=
<gallery mode=packed-hover heights=150px>
File:02UM_Kyo_st.A_1.png|'''Startup'''
File:02UM_Kyo_st.A_2.png|'''Active'''
</gallery>
}}</pre></div>
<br>
* Case 2: Simple table with one move and a caption.
{{FrameDataCargo-KOF02UM
|moveId=kyo_stc
|captions=''This is not okay.''
|description=
<br>
Very lackluster range for such a slow button with a severe lack of active frames, an unsettling tendency to be whiff punished and no conversion whatsoever. To put it bluntly this move could do double the damage with double the speed and it would still be pretty bad but it doesn't even have that. Mostly appears when messing up cl.C's spacing, frustration usually ensues.
|phases=
<gallery mode=packed-hover heights=160px>
File:02UM_Kyo_st.C_1.png|Frames '''4~9'''
File:02UM_Kyo_st.C_2.png|Frames '''10~12'''
File:02UM_Kyo_st.C_3.png|'''Active'''
File:02UM_Kyo_st.C_4.png|'''Early Recovery'''
</gallery>
}}
<div class="toccolours mw-collapsible mw-collapsed" style="width:500px">
<div style="font-weight:bold;line-height:1.6;">Source</div>
<pre class="mw-collapsible-content">
{{FrameDataCargo-KOF02UM
|moveId=kyo_stc
|captions=''This is not okay.''
|description=
<br>
Very lackluster range for such a slow button with a severe lack of active frames, an unsettling tendency to be whiff punished and no conversion whatsoever. To put it bluntly this move could do double the damage with double the speed and it would still be pretty bad but it doesn't even have that. Mostly appears when messing up cl.C's spacing, frustration usually ensues.
|phases=
<gallery mode=packed-hover heights=160px>
File:02UM_Kyo_st.C_1.png|Frames '''4~9'''
File:02UM_Kyo_st.C_2.png|Frames '''10~12'''
File:02UM_Kyo_st.C_3.png|'''Active'''
File:02UM_Kyo_st.C_4.png|'''Early Recovery'''
</gallery>
}}</pre></div>
<br>
* Case 3: Simple table with one move and I pick what image and hitbox to show.
{{FrameDataCargo-KOF02UM
|moveId=kyo_clc
|image=02UM_Kyo_cl.C_2_ima.png
|hitbox=02UM_Kyo_cl.C_2.png
|description=
<br>
A very fast and cancelable uppercut with deceptively good range that serves as Kyo's main combo starter and then extends higher for a good secundary grounded anti-air against hops. Can be 1f linked off cr.B for a good frametrap on block but a somewhat limited conversion on hit without max mode.<br>
<br>
* Only the first part is cancelable so a whiff cancel needs to be done very fast.
|phases=
<gallery mode=packed-hover heights=200px>
File:02UM_Kyo_cl.C_1.png|'''Startup'''
File:02UM_Kyo_cl.C_2.png|Frames '''3~4'''
File:02UM_Kyo_cl.C_3.png|Frames '''5~12'''
</gallery>
}}
<div class="toccolours mw-collapsible mw-collapsed" style="width:500px">
<div style="font-weight:bold;line-height:1.6;">Source</div>
<pre class="mw-collapsible-content">
{{FrameDataCargo-KOF02UM
|moveId=kyo_clc
|image=02UM_Kyo_cl.C_2_ima.png
|hitbox=02UM_Kyo_cl.C_2.png
|description=
<br>
A very fast and cancelable uppercut with deceptively good range that serves as Kyo's main combo starter and then extends higher for a good secundary grounded anti-air against hops. Can be 1f linked off cr.B for a good frametrap on block but a somewhat limited conversion on hit without max mode.<br>
<br>
* Only the first part is cancelable so a whiff cancel needs to be done very fast.
|phases=
<gallery mode=packed-hover heights=200px>
File:02UM_Kyo_cl.C_1.png|'''Startup'''
File:02UM_Kyo_cl.C_2.png|Frames '''3~4'''
File:02UM_Kyo_cl.C_3.png|Frames '''5~12'''
</gallery>
}}</pre></div>
<br>
* Case 4: Table of 3 moves with no phases, a description only after the 3rd move's data, a caption only on the 3rd hitbox, and I want to pick the name and input on display.
{{FrameDataCargo-KOF02UM
|moveId=kyo_ha,kyo_ja,kyo_nja
|name=jump A
|input=j.A
|captions=,,whack
|description3=
<br>
The only good thing to note is hop A has a good chunk of active frames for a hop, though it isn't deep enough to hit crouching(Bao, Chin, Choi) unlike j.A or neutral j.A. Mediocre and outshone by other jump-ins.
}}
<div class="toccolours mw-collapsible mw-collapsed" style="width:500px">
<div style="font-weight:bold;line-height:1.6;">Source</div>
<pre class="mw-collapsible-content">
{{FrameDataCargo-KOF02UM
|moveId=kyo_ha,kyo_ja,kyo_nja
|name=jump A
|input=j.A
|captions=,,whack
|description3=
<br>
The only good thing to note is hop A has a good chunk of active frames for a hop, though it isn't deep enough to hit crouching(Bao, Chin, Choi) unlike j.A or neutral j.A. Mediocre and outshone by other jump-ins.
}}</pre></div>
<br>
* Case 5: Table of 2 moves both with descriptions and phases, and I want to decide what images and hitboxes to show.
{{FrameDataCargo-KOF02UM
|moveId=kyo_rawf+B,kyo_cancelf+B
|image=02UM_Kyo_raw_f+B_2_ima.png
|image2=02UM_Kyo_can_f+B_3_ima.png
|hitbox=02UM_Kyo_raw_f+B_2.png
|hitbox2=02UM_Kyo_can_f+B_3.png
|description=
Kyo lifts his leg then does a quick heel drop, very simple overhead but doesn't have much use, especially without meter. On paper the average speed and short active period feels lacking but a better look shows that the small active period is great since the hurtbox shrinks in quickly making it much less likely to be whiff punished. Furthermore, its good pushback also keeps it safe on block making this a fairly good mix-up option if it doesn't get stuffed first.<br>
<br>
* [[The_King_of_Fighters_2002_UM/Offense#Standing_Overheads|Standing Overhead]].
* '''Mix-up Advice''': After cr.B/A, cr.A you can delay cancel into f+B to get the raw f+B out faster than linking it for an overhead option versus canceling into df+D for a low.
* '''Combo Advice''': You can do '''BC run, cl.C''' to combo off a very close f+B. Off the previous mix-up, you can max bypass f+B into '''qcf+BC, [(C)qcf+A, (C)qcf+C]x1~2 (SC) qcfx2+A''' or '''qcf+BC, [(C)qcf+A, (C)qcf+C]x2 (SC) qcb,hcf+P(Charge)''' to spend 2 bars on a 36~41% conversion.
|phases=
<gallery mode=packed-hover heights=200px>
File:02UM_Kyo_raw_f+B_1.png|'''Startup'''
File:02UM_Kyo_raw_f+B_2.png|'''Active'''
File:02UM_Kyo_raw_f+B_3.png|'''Early Recovery'''
</gallery>
|description2=
Like most standing overheads, canceling f+B out of a normal on hit/block makes it faster and cancelable although they usually don't change animation like Kyo's f+B that then looks like his 98 Goufu You instead for some reason. It is faster but the first hit's range is tiny, whiffing on almost every non-backturned character for only the second hit to connect, although it only combos off cl.C/D on hit.<br>
It is mostly safe if it gets blocked but falls short of being a true blockstring in the first place, it's still a good frametrap but shouldn't be too relied on since the opponent can OS it with a fast invincible reversal.<br>
<br>
Both hits properly combo on the front only on Chang, standing(Shermie) and crouching(Chin, Choi, Xiangfei). Special note that against crouching Choi '''cl.C, f+B, qcf+C > hcb+P > f+P > dp+P''' is a true and good combo.
<br>
<br>
* '''Combo Advice''': The go-to meterless option on hit is '''cl.C, f+B, qcf+A''', it's mostly very safe on block but qcf+A can whiff on block so using qcf+C instead is a bit less safe but more consistent. The same max bypass as with raw f+B is still possible.
|phases2=
<gallery mode=packed-hover heights=200px>
File:02UM_Kyo_can_f+B_1.png|'''1st hit'''
File:02UM_Kyo_can_f+B_2.png|'''Gap'''
File:02UM_Kyo_can_f+B_3.png|'''2nd hit'''
</gallery>
}}
<div class="toccolours mw-collapsible mw-collapsed" style="width:500px">
<div style="font-weight:bold;line-height:1.6;">Source</div>
<pre class="mw-collapsible-content">
{{FrameDataCargo-KOF02UM
|moveId=kyo_rawf+B,kyo_cancelf+B
|image=02UM_Kyo_raw_f+B_2_ima.png
|image2=02UM_Kyo_can_f+B_3_ima.png
|hitbox=02UM_Kyo_raw_f+B_2.png
|hitbox2=02UM_Kyo_can_f+B_3.png
|description=
Kyo lifts his leg then does a quick heel drop, very simple overhead but doesn't have much use, especially without meter. On paper the average speed and short active period feels lacking but a better look shows that the small active period is great since the hurtbox shrinks in quickly making it much less likely to be whiff punished. Furthermore, its good pushback also keeps it safe on block making this a fairly good mix-up option if it doesn't get stuffed first.<br>
<br>
* [[The_King_of_Fighters_2002_UM/Offense#Standing_Overheads|Standing Overhead]].
* '''Mix-up Advice''': After cr.B/A, cr.A you can delay cancel into f+B to get the raw f+B out faster than linking it for an overhead option versus canceling into df+D for a low.
* '''Combo Advice''': You can do '''BC run, cl.C''' to combo off a very close f+B. Off the previous mix-up, you can max bypass f+B into '''qcf+BC, [(C)qcf+A, (C)qcf+C]x1~2 (SC) qcfx2+A''' or '''qcf+BC, [(C)qcf+A, (C)qcf+C]x2 (SC) qcb,hcf+P(Charge)''' to spend 2 bars on a 36~41% conversion.
|phases=
<gallery mode=packed-hover heights=200px>
File:02UM_Kyo_raw_f+B_1.png|'''Startup'''
File:02UM_Kyo_raw_f+B_2.png|'''Active'''
File:02UM_Kyo_raw_f+B_3.png|'''Early Recovery'''
</gallery>
|description2=
Like most standing overheads, canceling f+B out of a normal on hit/block makes it faster and cancelable although they usually don't change animation like Kyo's f+B that then looks like his 98 Goufu You instead for some reason. It is faster but the first hit's range is tiny, whiffing on almost every non-backturned character for only the second hit to connect, although it only combos off cl.C/D on hit.<br>
It is mostly safe if it gets blocked but falls short of being a true blockstring in the first place, it's still a good frametrap but shouldn't be too relied on since the opponent can OS it with a fast invincible reversal.<br>
<br>
Both hits properly combo on the front only on Chang, standing(Shermie) and crouching(Chin, Choi, Xiangfei). Special note that against crouching Choi '''cl.C, f+B, qcf+C > hcb+P > f+P > dp+P''' is a true and good combo.
<br>
<br>
* '''Combo Advice''': The go-to meterless option on hit is '''cl.C, f+B, qcf+A''', it's mostly very safe on block but qcf+A can whiff on block so using qcf+C instead is a bit less safe but more consistent. The same max bypass as with raw f+B is still possible.
|phases2=
<gallery mode=packed-hover heights=200px>
File:02UM_Kyo_can_f+B_1.png|'''1st hit'''
File:02UM_Kyo_can_f+B_2.png|'''Gap'''
File:02UM_Kyo_can_f+B_3.png|'''2nd hit'''
</gallery>
}}</pre></div>
<br>
* Case 6: Table of 2 basic actions with personalized images, their size and tabbers but without adjusting the image block size. (Sliders result)
{{FrameDataCargo-KOF02UM
|moveId=kyo_hop,kyo_jump
|name=Jump
|tab1=Hop
|tab2=Jump
|image=02UM_Kyo_hop.gif
|imageSize=x250px
|hitbox=02UM_Kyo_jump.gif
|hitboxSize=x250px
|description2= 
<br>
Jump arcs with good height and speed. Hyper hop able to go over middle height standing characters which helps for cross-ups. Note that if j.d+C is used, the jump's native 1f recovery is replaced by j.d+C's own 5f landing recovery, rending it particularly weak to low profiles.<br>
<br>
* Unthrowable by grounded throws for the entire duration. 
* When buffered, hyper hop and super jump are frame 1 airborne. Will avoid low meaties on wake-up.
}}
<div class="toccolours mw-collapsible mw-collapsed" style="width:500px">
<div style="font-weight:bold;line-height:1.6;">Source</div>
<pre class="mw-collapsible-content">
{{FrameDataCargo-KOF02UM
|moveId=kyo_hop,kyo_jump
|name=Jump
|tab1=Hop
|tab2=Jump
|image=02UM_Kyo_hop.gif
|imageSize=x250px
|hitbox=02UM_Kyo_jump.gif
|hitboxSize=x250px
|description2= 
<br>
Jump arcs with good height and speed. Hyper hop able to go over middle height standing characters which helps for cross-ups. Note that if j.d+C is used, the jump's native 1f recovery is replaced by j.d+C's own 5f landing recovery, rending it particularly weak to low profiles.<br>
<br>
* Unthrowable by grounded throws for the entire duration. 
* When buffered, hyper hop and super jump are frame 1 airborne. Will avoid low meaties on wake-up.
}}</pre></div>
<br>
* Case 7: Previous table and adjusting the block size. (No sliders)
{{FrameDataCargo-KOF02UM
|moveId=kyo_hop,kyo_jump
|name=Jump
|tab1=Hop
|tab2=Jump
|size=38%
|image=02UM_Kyo_hop.gif
|imageSize=x250px
|hitbox=02UM_Kyo_jump.gif
|hitboxSize=x250px
|description2= 
<br>
Jump arcs with good height and speed. Hyper hop able to go over middle height standing characters which helps for cross-ups. Note that if j.d+C is used, the jump's native 1f recovery is replaced by j.d+C's own 5f landing recovery, rending it particularly weak to low profiles.<br>
<br>
* Unthrowable by grounded throws for the entire duration. 
* When buffered, hyper hop and super jump are frame 1 airborne. Will avoid low meaties on wake-up.
}}
<div class="toccolours mw-collapsible mw-collapsed" style="width:500px">
<div style="font-weight:bold;line-height:1.6;">Source</div>
<pre class="mw-collapsible-content">
{{FrameDataCargo-KOF02UM
|moveId=kyo_hop,kyo_jump
|name=Jump
|tab1=Hop
|tab2=Jump
|size=38%
|image=02UM_Kyo_hop.gif
|imageSize=x250px
|hitbox=02UM_Kyo_jump.gif
|hitboxSize=x250px
|description2= 
<br>
Jump arcs with good height and speed. Hyper hop able to go over middle height standing characters which helps for cross-ups. Note that if j.d+C is used, the jump's native 1f recovery is replaced by j.d+C's own 5f landing recovery, rending it particularly weak to low profiles.<br>
<br>
* Unthrowable by grounded throws for the entire duration. 
* When buffered, hyper hop and super jump are frame 1 airborne. Will avoid low meaties on wake-up.
}}</pre></div>