The weird multi-button combo for KB/M jump attacks is weird. Are you sure all those presses are required? I know that, on controller, it's "tap forward + attack", but the timing is very finicky and slightly offset, to the point where performing it in combat is unreliable at best. It would make sense that the same inputs are required in the KB/M variant, just with the same obnoxious staggering controllers suffer from.
It's actually even worse than that. The 'g' key in that combo is the 'left attack' button. So why can't you just use the mouse for that combo?
By default, the strong attack for both right and left are bound to 'double mouse right' and 'double mouse left.' "But wait," you might be thinking, "what does that have to do with a combo?"
Well here's the part where we put our pants on our heads and start tasting paste. They determine whether the mouse was pressed once or pressed twice by introducing a delay in mouse click input, to wait for the mouse to be potentially pressed again before acting upon it. Which means any attack combo involving any mouse buttons will time out and fail before the input is registered as a single mouse press. And thus the only way to pull off any combo is to ensure every button in the combo is pressed on the keyboard only. You can unbind the strong attack from the double clicks so they are set to nothing;
but they still wait the time it takes to determine if the mouse was pressed twice. And if it was pressed twice while unbound, it doesn't do the single press action,
it does nothing.Every single combo that involves anything bound to the mouse. Completely broken unless you use solely the keyboard. The guard break combo (or whatever it is, I've never actually seen it) is similarly broken; though I believe it uses the 'h' key instead of 'g.'
The only real fix I've seen online is variations on these instructions to install autohotkey and macro scripts to 'rebind' the keys. When the only way to effectively rebind your controls to something useful involves installing 3rd party macro scripts, your shit is broke. We wrote better input handling code in less than a week during our spare time as university students.
The saddest 2 lines in that script are these:
~LButton::H
~RButton::G
This is literally saying "When the default mouse attack bindings are pressed, intercept the button press, and emulate a press of the default keyboard attack bindings." just to get rid of the artificial input latency.