Paranormal_Oreo
[12] Conqueror
JF CE: 23236:bA+B+K. Can anyone do this consistently? I have only gotten it 5 out of about 60 tries. Also do is have any kind of advantage over the normal CE that isn't just blinding the opponent with awesomeness?
[ARCHIVE] JF CE
- Thread starter Paranormal_Oreo
- Start date
- Status
srsgamer87
[09] Warrior
Until there's video proof it doesn't exist, same as Hilde's "infinite".
Paranormal_Oreo
[12] Conqueror
Kane
oh riri
wow good find! ... I wonder if pyrrha has the same.
it would be awesome if the "jf" ce did the whole hit-throw animation even on airborne opponents
it doesn't appear to do any more damage than normal ... I guess it's just for "flash", no pun intended hah.
it would be awesome if the "jf" ce did the whole hit-throw animation even on airborne opponents
it doesn't appear to do any more damage than normal ... I guess it's just for "flash", no pun intended hah.
Supa
[10] Knight
Obvious glitch is obvious.
Even after the patch, there are a ton of those glitches all over every character including having Nightmare do a "BE CE" (236236bA+B+K).
Even after the patch, there are a ton of those glitches all over every character including having Nightmare do a "BE CE" (236236bA+B+K).
Age_of_Truth
[12] Conqueror
Try to find if it's possible using an A+B+K button bind, or if you have to use separate buttons.
If you have to use separate buttons, it's probably 236:B being 'kara-cancelled' into CE. The game will give you input leniency so that your CE comes out even if you press B before A and/or K, but of course the first frame(s) will still come out as 236:B.
If the green JF 'flash' is a separate animation from the 236:B animation, then the flash could still continue even after the move has changed into CE.
If you have to use separate buttons, it's probably 236:B being 'kara-cancelled' into CE. The game will give you input leniency so that your CE comes out even if you press B before A and/or K, but of course the first frame(s) will still come out as 236:B.
If the green JF 'flash' is a separate animation from the 236:B animation, then the flash could still continue even after the move has changed into CE.
Paranormal_Oreo
[12] Conqueror
It is possible to do with an A+B+K bind but you obviously have to do B and A+B+K separately. Also, it isn't 236:B that gives the flash. Its the 236236B. I mean it isn't the 236236B that gives it that but say you were to try the JF CE but you didn't press the A+B+K. Just the B, you would have to get DNS B. If you don't then you wouldn't have gotten the JF CE. Hope that made atleast a little bit of sense.
Supa
[10] Knight
I don't use an A+B+K bind and it happens all the time. I believe you can do it with just 236236A+B+K as long as you hit B first without pressing the JF bA+B+K.
What Age_Of_Truth describes is what happens in other games, but not SC. What it looks like is that the game reviews the input buffer even after an input is triggered. So rather than being kara-cancelled it appears to execute both the 236B and the CE with the CE taking priority. In contrast, other games would only execute one or clearly execute one before the other with moves taking certain priorities.
ie:
236B236A+B+K -> should do 236B, but you can get a CE from it and the JF CE. 236B starts but gets overridden.
6236P (in KoF13) will get you a dragon punch, but not a fireball animation with a dragonpunch at the end.
62369P (in KoF13) will get you a fireball. But not a dragon punch startup with a fireball at the end.
SCVs inputs are screwed up. Like seriously screwed up.
What Age_Of_Truth describes is what happens in other games, but not SC. What it looks like is that the game reviews the input buffer even after an input is triggered. So rather than being kara-cancelled it appears to execute both the 236B and the CE with the CE taking priority. In contrast, other games would only execute one or clearly execute one before the other with moves taking certain priorities.
ie:
236B236A+B+K -> should do 236B, but you can get a CE from it and the JF CE. 236B starts but gets overridden.
6236P (in KoF13) will get you a dragon punch, but not a fireball animation with a dragonpunch at the end.
62369P (in KoF13) will get you a fireball. But not a dragon punch startup with a fireball at the end.
SCVs inputs are screwed up. Like seriously screwed up.
Paranormal_Oreo
[12] Conqueror
Pyrrha has one too. Just tested . Looks flashy as fuck!
Kane
oh riri
^ I'm hella gonna try to use that in tournament 
Suirad
[10] Knight
So from what has been said, it's basically just a visual glitch caused by cancelling iNS B into CE and has no added difference in properties?
Supa
[10] Knight
Pretty sure 100% of these are just visual glitchery.
You can have fiery Yoshimitsu CEs that aren't unblockable, BE "flared" Nightmare CEs that do nothing (except sap your bar) and blinky Poe CEs.
Kane
oh riri
awesome glitch ... had to do the Pyrrha version :D
DrakeAldan
Follow the rules!
You flashy bastards.
CheeseOfTheDay
[10] Knight
great find
love that bling-bling stuff
love that bling-bling stuff
Echo01
[10] Knight
Would be awesome if it increased the already amazing range, or caught airborne opponents with the full animation.
Age_of_Truth
[12] Conqueror
Supa
[10] Knight
Yes.
If it didn't work the way I described then JFs wouldn't work at all. The whole purpose of a JF is that a move is triggered and then overridden by the next input. But SC does that on all inputs - not only JFs.
To put it another way, let's say the input buffer looked like:
[G]236B]G[236[.B]236A+K
What should happen is that the game ignores the first 236B (since it's in guard) which it does. But then it executes both the second 236B and the CE as long as the A+K is pushed within a few frames (3F?). That's not right..... For more weirdness that you won't find in the way other games review the input buffer, go check out Poe's BE fail (6B A+B+K turns into a BE colored normal) or the Nightmare bar sap I mentioned.
Other games explicitly mark moves that are cancellable for the game input logic. I have no idea, but I'm willing to bet that SC instead only marks moves that are NON-cancellable. Whitelisting versus Blacklisting.
If it didn't work the way I described then JFs wouldn't work at all. The whole purpose of a JF is that a move is triggered and then overridden by the next input. But SC does that on all inputs - not only JFs.
To put it another way, let's say the input buffer looked like:
[G]236B]G[236[.B]236A+K
What should happen is that the game ignores the first 236B (since it's in guard) which it does. But then it executes both the second 236B and the CE as long as the A+K is pushed within a few frames (3F?). That's not right..... For more weirdness that you won't find in the way other games review the input buffer, go check out Poe's BE fail (6B A+B+K turns into a BE colored normal) or the Nightmare bar sap I mentioned.
Other games explicitly mark moves that are cancellable for the game input logic. I have no idea, but I'm willing to bet that SC instead only marks moves that are NON-cancellable. Whitelisting versus Blacklisting.
Age_of_Truth
[12] Conqueror
Dude you can talk all you want. I already explained what's happening. It's clear from your comment "I don't use an A+B+K bind" that you don't undertsand what I said.
You want to carry on misleading other players with nonsensical waffling, go ahead. I haven't got the energy to waste time arguing with you.
You want to carry on misleading other players with nonsensical waffling, go ahead. I haven't got the energy to waste time arguing with you.
Supa
[10] Knight
Wow. So much angst.
I mentioned not using the A+B+K bind to SUPPORT what you were saying, nitwit. We already know what's causing the visual glitch and then you disagree with a more verbose version of exactly what you said. If you aren't here to speculate about it then don't quote my entire post.
To point out the painfully obvious: you do realize that we're saying generally the same thing, right? It's pretty clear you don't understand what you're saying, either.....
I mentioned not using the A+B+K bind to SUPPORT what you were saying, nitwit. We already know what's causing the visual glitch and then you disagree with a more verbose version of exactly what you said. If you aren't here to speculate about it then don't quote my entire post.
To point out the painfully obvious: you do realize that we're saying generally the same thing, right? It's pretty clear you don't understand what you're saying, either.....
- Status