Clone cancel is not safe. Also, hit confirming allows b2 and B33 to be fuzzy guarded because you confirm B33 based off of both hits not just the last hit. If the opponent fuzzy guards, B2 is blocked and only the second hit of B33 connects which makes the hit confirm impossible. the OS punishes fuzzy guard.Thanks for the videos, but exactly what is wrong with just hit confirming? Especially since that way I can make a choice whether to just Block and be safe or cancel into a Clone instead?
hit confirm will not work because the opponent can fuzzy guard which prevents the hit confirm.Thanks for the time, but I'd just prefer to hit-confirm or commit to my options.
Are you planning on being competitive? If so getting these down is extremely important.Thanks for the time, but I'd just prefer to hit-confirm or commit to my options.
If the opponent fuzzy guards the overhead/low mix up, the first hit of B33 is blocked and only the second hit of the string hits. This makes it impossible to hit confirm. So yes, that is what hit confirming is.. You just cannot do it if the opponent is fuzzy guarding.That's not what hit-confirming is though.
he means if the opponent blocks low, high and gets hit with the second low the OS will cancel into iceball, whereas if you try to hitconfirm you will see the 1st low blocked and not commit to iceballThat's not what hit-confirming is though.
No, it means this..Cancelling in to EX-Clone is pretty safe in general, and if they have no meter cancelling in to clone in general pretty safe too, and even if they do have meter its still ok to do every now and again I think. But regardless, are you saying the advantage of this over hitconfirming is if they block the first hit of B33, then drop block it OS's through? If thats the case then I think I'm cool with just hitconfirming I think, although I do appreciate the video
he means if the opponent blocks low, high and gets hit with the second low the OS will cancel into iceball, whereas if you try to hitconfirm you will see the 1st low blocked and not commit to iceball
How do you get a safe clone out of this? This uses ice blast or enhanced ice blast, and if it's block and that doesn't come out, the clone you pop out after is unsafe.I run into a very high percentage of people who fuzzy guard the b33 string. This OS gives me damage, a corner carry, and a safe clone when I would have otherwise only had 12+ hit adv.
I meant to imply that I could get the safe clone post combo in the event that the opponent does fuzzy guard and I hit with the OS.How do you get a safe clone out of this? This uses ice blast or enhanced ice blast, and if it's block and that doesn't come out, the clone you pop out after is unsafe.
B33 is -8 and unpunishable by 95% of the cast. No need for the risk on ex clone cancel.I meant to imply that I could get the safe clone post combo in the event that the opponent does fuzzy guard and I hit with the OS.
Having said that, I'll bet you could OS the b33 xx ice blast, cancelling with forward, and continue half circle back for the MB ice statue command. This way you either get a combo or a safe clone (assuming it doesn't bug out and give you normal clone).
Clone Cancels would be the obvious thing that you stand to lose doing it this way, instead of hitconfirming. I'm also a fan of cancelling into Ice Burst for 2% chip and only -10. This OS is just the easy way to do it, and there is no reason at all for a sensible opponent to drop lowblock against Sub once you've confirmed that his ONLY overhead isn't coming since it's the opener and 18 frames long. This is a good way to punish that mistake, but that seems like about itIf you're familiar with the trials from Street Fighter IV onwards, the notion to figure out when the link angel is too early or too late is fairly straightforward. If you use Sub Zero, you owe it to yourself to at least know how to do this.
It really isn't the most difficult thing in the world. Just do it, what do you have to lose besides matches?