Recent content by Saykrd

I disagree actually. Frames are a more useful unit of measurement than milliseconds because more visual and also more coherently tied to the game itself rather than your personal interpretation of how long something will take. We may use time everyday, but can you actually picture in your head...

https://twitter.com/saykrd/status/710114094884495360?s=09 Yeah, FSmash is still jank guys.

Nah I tested that specifically. I can assure you that is still a thing sadly.

Alright re-confirming this. Just updated my 3ds to 1.1.5. Unless they changed the blastzones of 3ds battlefield this is most likely confirmed. Ftilt kills 30%+ earlier So far these are my findings at least: Jab1: Possible angle/knockback change to make it link into jab 2 better. Jab2...

Ah I see, that might be placebo then.

[Probably placebo, pls test on one system to confirm] Ftilt might have also gotten some KBG changes as well. It kills at least 30% earlier. (167% > 135% on Mario from the edge of battlefield)

I know right? Seriously. What's worse is Samus' whole leg hurtbox is just poking out unprotected.

Is it really 4 frames? It seems more lenient than that to me. It's definitely easier to land at low %, and it helps if you b-reverse WT so that they start behind you and get knocked into the second one. It seems to stop working at like 70%+ on midweights tho, or maybe I'm just bad. ...But...

The second WT should be double jump canceled, so after the whole combo finishes you should still have your double jump

It should be doable in training mode just fine. Make sure you ABK right after WT ends as opposed to interrupting it.

I do, I was just lazy :P. Here you go: https://www.youtube.com/watch?v=_D2lIlT_Qk4

There's also another variant of this combo that goes Dtilt-WT-ABK-WT-ABK-UAir that's slightly more reliable since ABK-UAir is harder to DI out of than ABK-ABK-Uair. I'd post a video but I don't have recording tools :/

Yeah, that's just Donkey Kong's UpB windbox that moved him. Edit: Got ninja'd

I thought so too, yet every time I try a forward input that isn't close to an upthrow input it doesn't end up canceling the dash throw. It's probably some inconsistency in the logic that checks whether you're trying to perform an upthrow and the actual logic to perform an upthrow. Oh its also...

If I'm facing right, It's pretty much: :GCR: Dash -> :GCA: (hold) Dash Throw -> :GCB: + :GCUR:(but about a tenth of the distance between the NE and E groove lower) For the backthrow input, practically it would be: :GCR: Dash -> :GCN: + :GCA: (hold) Dash Throw -> :GCB: + :GCUL:(but about a...