RE: DRE: CTS community mail

  • From: lindsey kiviets <lindseyak@xxxxxxxxxxx>
  • To: "cpt-fgc@xxxxxxxxxxxxx" <cpt-fgc@xxxxxxxxxxxxx>
  • Date: Wed, 22 Apr 2015 04:35:11 +0000

https://www.youtube.com/watch?v=Mp2oM5Ap3Go

lol like dis?

Date: Wed, 22 Apr 2015 00:23:44 +0200
Subject: Re: DRE: CTS community mail
From: marongdin@xxxxxxxxx
To: cpt-fgc@xxxxxxxxxxxxx

Ok i just understood how that works...
basically it's sort of hit confirming?
normal string into special xx on block? input the rest of the string xx on hit?
let the combo begin.
right? that's pretty odd. Does it have to be a command from the string or i can
just mash any button during the string into special into _______.
On Wed, Apr 22, 2015 at 12:12 AM, Di Lhong <marongdin@xxxxxxxxx> wrote:
usually unsafe normals into special are either interrupt-able or can be
backdashed.
especially if the special is slow. fast specials are usually unsafe.
On Tue, Apr 21, 2015 at 11:25 PM, Ilitirit Sama <ilitirit@xxxxxxxxx> wrote:
Oh man, how could the developers not see this one coming...

So in MKX, impact freeze on block is different than on hit. Now that's bad.
But the bigger problem is that on block, impact freeze is longer. THIS IS
STUPID. What this means is that you can use buffer Option Selects. If you
buffer a normal into a special, usually what happens is the normal will cancel
into special on hit. But, you can cancel the special by inputting more
commands after you inputted the special move. Basically, it clears the input
buffer if you input input another move before the special comes out. What does
this enable you to do?

normal xx (unsafe) special xx (any safe input)

On hit, you get the normal into special. On block, the longer impact freeze
gives you more time to cancel the special, so the special move will not come
out.

Silly NRS.




Other related posts: