-The Dream Cancel Wiki has successfully upgraded it's wiki software and editing has returned. Tables for data have returned.

Template:FrameDataCargo-KOF02UM: Difference between revisions

From Dream Cancel Wiki
Jump to navigation Jump to search
Franck Frost (talk | contribs)
No edit summary
Franck Frost (talk | contribs)
No edit summary
Line 1: Line 1:
<includeonly>{| class="wikitable" style="text-align: center; border-collapse: collapse; margin: 0em;" width="96%"
<includeonly>{| class="wikitable" style="text-align: center; border-collapse: collapse; margin: 0em;" width="96%"
! width = "180px" style="vertical-align:top;"| <big>{{#cargo_query:tables=MoveData_KOF02UM| fields = name| where = moveId='{{#invoke:Parser|parseMoves|{{{moveId|}}}|2}}'}}</big><br/><small>{{#cargo_query:tables=MoveData_KOF02UM| fields = input| where = moveId='{{#invoke:Parser|parseMoves|{{{moveId|}}}|2}}'}}</small>
! width = "180px" style="vertical-align:top;"| <big>{{#cargo_query:tables=MoveData_KOF02UM| fields = name| where = moveId='{{#invoke:Parser|parseMoves|{{{moveId|}}}|1}}'}}</big><br/><small>{{#cargo_query:tables=MoveData_KOF02UM| fields = input| where = moveId='{{#invoke:Parser|parseMoves|{{{moveId|}}}|1}}'}}</small>
<tabber>
<tabber>
Images=
Images=
Line 10: Line 10:
| style="text-align: {{#if:{{{textonly|}}}|left|center}}; vertical-align:top; padding: {{#if:{{{textonly|}}}|0.2em;|0px;}}" height="100%"|
| style="text-align: {{#if:{{{textonly|}}}|left|center}}; vertical-align:top; padding: {{#if:{{{textonly|}}}|0.2em;|0px;}}" height="100%"|
{| class="wikitable" style="text-align: center; border-collapse: collapse; border-style: hidden; margin: 0em;" width="100%"
{| class="wikitable" style="text-align: center; border-collapse: collapse; border-style: hidden; margin: 0em;" width="100%"
{{FrameData-KOF02UM/Query|{{#invoke:Parser|parseMoves|{{{moveId|}}}|2}}}}
{{FrameData-KOF02UM/Query|{{#invoke:Parser|parseMoves|{{{moveId|}}}|1}}}}
{{#if:{{{description|}}}|
{{#if:{{{description|}}}|
{{!}} {{#if:{{{version|}}}|colspan="12"|colspan="11"}} style="text-align: left; vertical-align:top; font-size: 110%;" {{!}}  
{{!}} {{#if:{{{version|}}}|colspan="12"|colspan="11"}} style="text-align: left; vertical-align:top; font-size: 110%;" {{!}}  
Line 17: Line 17:
</div>
</div>
{{!}}-}}
{{!}}-}}
{{#if:{{#invoke:Parser|parseMoves|{{{moveId|}}}|3}}|
{{#if:{{#invoke:Parser|parseMoves|{{{moveId|}}}|2}}|
{{FrameData-KOF02UM/Query|{{#invoke:Parser|parseMoves|{{{moveId|}}}|3}}}}
{{FrameData-KOF02UM/Query|{{#invoke:Parser|parseMoves|{{{moveId|}}}|2}}}}
{{#if:{{{description2|}}}|
{{#if:{{{description2|}}}|
{{!}} {{#if:{{{version|}}}|colspan="12"|colspan="11"}} style="text-align: left; vertical-align:top; font-size: 110%;" {{!}}  
{{!}} {{#if:{{{version|}}}|colspan="12"|colspan="11"}} style="text-align: left; vertical-align:top; font-size: 110%;" {{!}}  
Line 26: Line 26:
{{!}}-}}
{{!}}-}}
}}
}}
{{#if:{{#invoke:Parser|parseMoves|{{{moveId|}}}|4}}|
{{#if:{{#invoke:Parser|parseMoves|{{{moveId|}}}|3}}|
{{FrameData-KOF02UM/Query|{{#invoke:Parser|parseMoves|{{{moveId|}}}|3}}}}
{{FrameData-KOF02UM/Query|{{#invoke:Parser|parseMoves|{{{moveId|}}}|3}}}}
{{#if:{{{description3|}}}|
{{#if:{{{description3|}}}|
Line 32: Line 32:
<div>
<div>
{{#if:{{{phases3|}}}|<tabber>Description= {{{description3|}}} |-| Phases= {{{phases3|}}}</tabber>|{{{description3|}}}}}
{{#if:{{{phases3|}}}|<tabber>Description= {{{description3|}}} |-| Phases= {{{phases3|}}}</tabber>|{{{description3|}}}}}
</div>
{{!}}-}}
}}
{{#if:{{#invoke:Parser|parseMoves|{{{moveId|}}}|4}}|
{{FrameData-KOF02UM/Query|{{#invoke:Parser|parseMoves|{{{moveId|}}}|4}}}}
{{#if:{{{description4|}}}|
{{!}} {{#if:{{{version|}}}|colspan="12"|colspan="11"}} style="text-align: left; vertical-align:top; font-size: 110%;" {{!}}
<div>
{{#if:{{{phases4|}}}|<tabber>Description= {{{description4|}}} |-| Phases= {{{phases4|}}}</tabber>|{{{description4|}}}}}
</div>
</div>
{{!}}-}}
{{!}}-}}
Line 37: Line 46:
{{#if:{{#invoke:Parser|parseMoves|{{{moveId|}}}|5}}|
{{#if:{{#invoke:Parser|parseMoves|{{{moveId|}}}|5}}|
{{FrameData-KOF02UM/Query|{{#invoke:Parser|parseMoves|{{{moveId|}}}|5}}}}
{{FrameData-KOF02UM/Query|{{#invoke:Parser|parseMoves|{{{moveId|}}}|5}}}}
{{#if:{{{description3|}}}|
{{#if:{{{description5|}}}|
{{!}} {{#if:{{{version|}}}|colspan="12"|colspan="11"}} style="text-align: left; vertical-align:top; font-size: 110%;" {{!}}  
{{!}} {{#if:{{{version|}}}|colspan="12"|colspan="11"}} style="text-align: left; vertical-align:top; font-size: 110%;" {{!}}  
<div>
<div>
{{#if:{{{phases4|}}}|<tabber>Description= {{{description4|}}} |-| Phases= {{{phases4|}}}</tabber>|{{{description4|}}}}}
{{#if:{{{phases5|}}}|<tabber>Description= {{{description5|}}} |-| Phases= {{{phases5|}}}</tabber>|{{{description5|}}}}}
</div>
</div>
{{!}}-}}
{{!}}-}}

Revision as of 19:27, 29 December 2021

Usage

No results
No results

Lua error: bad argument #1 to 'query' (string expected, got nil).

Lua error: bad argument #1 to 'query' (string expected, got nil).

No resultsNo results

Kyo swings both his legs on the ground to trip his opponent, nothing too special but it compliments his moveset really well. No, it still isn't cancelable but it works well after a cl.C or cr.B, cr.A to give him a limited but easy and mostly safe conversion that boosts for his high/low mix-up game.
Both hits' pushback and recovery keep it very safe on block but if the opponent is willing to spend the bar to GCRoll the first kick, they'll get a free punish on the recovering Kyo. Going for it more or less thus depends on situation and opponent.

df+D is extremely fast and has decent low profile so you'd expect to use it as such but it's not great for the job. The range is fairly limited, especially on the second hit that has the unsettling tendency to whiff when spaced a bit making df+D very whiff punishable at close range. If willing to spend the meter with hardly a confirm, canceling to the 1st hit into a max run and another df+D to start a combo is a better alternative for using df+D raw.

  • Combo Advice: Whether after cl.C or cr.B, cr.A; a df+D max bypass or a df+D(1) max cancel into a run is the basis of most of Kyo's max mode potential so it's best to get used to the move and at least just using a max bypass off it.

No results
No results

Lua error: bad argument #1 to 'query' (string expected, got nil).

Lua error: bad argument #1 to 'query' (string expected, got nil).

No results


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.