Thank you!
Honestly, I'm still quite conflicted on how far the dash should travel, since it used to be about 1.5x-2x as long when I first implemented it. I think the current iteration strikes a decent balance between recovery time, distance, and iframe duration that I quite like, but I've also heard comments on the invulnerability being too short or the dodge feeling unresponsive, so it's definitely something I want to experiment with in future.
Camera is another big aspect I need to really dig into, but these are some good suggestions. The current camera code does a little bit of angling downwards, but it's not very strong and doesn't work well at further distances. Dynamic zoom isn't something I've tried yet, so I'll look into that too.
Getting knocked down probably shouldn't feel good since it's a form of punishment for messing up. There's 2 types of knockdown you could be referring to here: getting knocked down by a specific strong attack, or getting stance broken when your meter fills up. There's a dodge recovery input for the first almost immediately once you hit the ground, but there's a bigger delay before you can do it on the second since you have to wait until you recover from being stance broken. Perhaps the animation poses aren't clear enough here? As for the input buffer, I believe it's still set at 0.2s buffer time, so I'll have to investigate the case of attack buffering during stance break and see if it needs to be reduced.