The Consequences of Floaty Combat in Kingdom Hearts
Video Statistics and Information
Channel: Bl00dyBizkitz
Views: 314,475
Rating: undefined out of 5
Keywords: Kingdom Hearts, Kingdom Hearts 2, Kingdom Hearts 2 Final Mix, Kingdom Hearts Birth by Sleep, Kingdom Hearts 0.2, Kingdom Hearts Birth by Sleep 0.2, Combat, Gameplay, Action Game, Action RPG, Bl00dyBizkitz, BB, Analysis, Video Essay, Floaty Combat, Floaty Gameplay, Floaty, Animation, Clunky, Tight, Game Feel, Controls, Gameplay Analysis
Id: lqWh1faBaAA
Channel Id: undefined
Length: 13min 7sec (787 seconds)
Published: Wed Jan 02 2019
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.
I agree with him, to be honest. It's the ability to be flexible with your combos and also not being animation locked too heavily when you perform basic combos on the ground or in the air. Those are the things that makes KH2's combat punchy and satisfying. I'm not saying KH3 has to adhere to this design philiosophy, but if it did, I'm sure both casual players and the players who want a little something more from the game will be happy.
Iβve never been a speed runner or anything, but Iβve always noticed a big difference in the combat systems between kh2 (my favorite game EVER) and every game after. Didnβt realize it was the βfloatinessβ until recently with all this talk, and itβs making me super nervous about the game. Iβve been a fan of the series since kh1 but the combat system is super important to me and Iβm PRAYING they can do something about it.
If I see one more combat finisher where the character does an upper cut into the air and sits there for 1.5 seconds before falling, Iβm gonna lose it
Everything said in the video has been 100% fair. Just because there are some people who don't care about the things mentioned about the combat doesn't make his concern(as well as many others) for the game any less valid and something that shouldn't be talked about. If a game like KH2 was designed in such a way which had satisfied both hardcore and casual side of the fanbase, I don't think it's unreasonable for those that do care to hope that the dev team are again able to find that middle ground of design that can please both sides.
Floaty combat at its finest.
https://imgur.com/a/yPVy2wB
After this I had to take unwind by attempting the data fights in kh2
He's 1000% right. Literally just so right. I hope kh3 turns out right
I think KH3 will be floaty but not as bad as BBS and DDD. Will it be as tight as KH2? No but it will be the closest thing to it, which isnβt too awful!
I completely agree with every point Bloody is making and I truly do hope that KH3 feels completely like KH2, but new and more fresh of course. Though while he doesn't seem reassured, it seems others have been reassured as Square has been taking feedback about it and there is always patching in the future too if it comes down to that.
I want KH3 to be the absolute best it can be. Story, gameplay, and feel. And I damn well hope it'll be because I'm sure Osaka team needs that boost for future games to come in the franchise.
Can't wait for people to throw BB under the bus for being a speedrunner, when they probably didn't even give the video a chance and probably formulated their opinion on nothing. Meanwhile, BB actually shows footage, and articulates his opinions. The video brings up a lot of awesome points and I really enjoy the lack of understanding of complex gameplay mechanics between a casual crowd and the hardcore crowd. Im usually really competitive in a lot of games and find myself more towards the hardcore crowd and understand that little things like this make or break a persons experience. I am definitely a casual guy when it came to kingdom hearts but his speedruns and his analysis really make me understand the concerns of the hardcore crowd.
Yeah...I've heard ever since it was announced at E3 that people have been super worried about the combat being "floatly" like in all the other games, with the exception of 2. And it's honestly a very valid concern. Hopefully being un UE fixes this issue.