Thanks a lot for creating this game.
It's turned out bloody awesome and you deserve every bit that's coming your way.

Probably THE most fun fighter I've ever played, and even better than it had been in alpha.

It's been a long time, I'll drink to an even longer time together yet to come.
Cheers.

@Huggles said:
Start another attack (combo) after your miss and then parry.

I was not aware of that, thank you.
Tested it:
https://www.youtube.com/watch?v=Oyr5loBIHRs

And personally, I feel there's no reason at all that we can't "queue" a block (i.e. start one at the same time where we would start the queued strike in the combo). The superficial delay is just super annoying.

If you have that much time to bring your blade back up into position, you could just as well flip it back with force, resulting in a block, instead.

Been wondering for a while why it takes so darn long to get your sword back into position after a miss ...

I mean, let's say I have a greatsword against somebody with a sledgehammer.
We can both miss each other and he has all the time in the world to take another swing and hit me while I can't do anything but watch.
That can't be how these lockouts are supposed to work ...

Something minor completely unrelated that I am surprised survived so long ...

When you press "quit" after a match, mordhau doesn't care and puts you into the new game anyway.

Next bug:

I alt+tabbed out during the loading screen ... the entire screen turned black and STAYED black.
Tabbing back in didn't resolve anything, neither did tabbing back out.
Pressing the windows key did show me the task bar and the start menu, but the desktop remained completely black. win+L did lock the screen and did show me the lockscreen, but when I logged back in, black again.
Tabbing into mordhau and using Alt+F4 didn't do anything.
Started the taskmanager, screen remained black.
Eventually managed to close mordhau by using the arrow keys when tabbed into the task manager and using the alt-tab previews (which weren't blacked out) to determine whether I had selected the correct process to kill, then killing it with del.

Killing mordhau immediately resolved the blackness, so I can confirm that it's something to do with the game.

Using Win10 (64bit).

@Black Platypus said:
Update on the flickering problem: I fixed the issue by going to Nvidia Control Panel-Change Resolution-Then check the "Use Nvidia Color Settings" box and make sure it is set to 32 bit. I hope this helps others with the problem.

That did the trick, thank you.
Problem probably still should be addressed to work with standard colour settings, too. (Because imagine buying a game and the first thing you see is this flickering monstrosity.)

Have a similar problem to Foxy's, except in my case it's flickering purple.

The still doesn't portray how annoying the flickering is, and I cannot caputure it with my phone. Apparently, it's flickering at just the "right" rate for it not to be picked up while filming.

Also suspecting new NVIDIA driver.
Specs as reported by dxdiag:

CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00 GHz (8CPUs)
GPU: NVIDIA GeForce GTX 980, 4GB VRAM
Monitor: Generic PnP Monitor; mode: 1920x1080 (32bit) (60Hz)

Thanks to the both of you. Does seem to reset on exit.

step 1, press keys at random and hope one of them opens the console.

step2: ???

(why not simply make a setting out of it?)

Anybody also having a lot of trouble morphing rapier slashes into stabs? Just doesn't happen, for me.

Yeah, not very fond of the rollback on the 240 system. Prefer the click-and-flick, myself.
Why not add it as an option to the settings?

Mouse attack angling now angles after detecting movement after button press, or until button is released, same as it works in MnB/Wotr

I don't find the "or until button is released" option, so does this mean that after a keypress, it checks if the mouse moves and takes that angle or if no movement occurs. takes the angle before the click? Or am I overlooking something?

At any rate, it does feel a lot more consistent.

@kEsa1996 said:
[...]
it starts measuring the direction of your swing when you press down LMB
[...]
Make the attack windup start as soon as the client detects movement from your mouse (Up until here this is the exact same system used in M&B and WOTR). Unlike M&B and WOTR the client should then keep on proceeding to the release phase no matter whether LMB is still pressed down or not.

Personally I think the [...] option would be best. It's faster [...] yet extremely accurate in reading a player's input as proven by M&B and WOTR.

I'm in favour of that. Haven't played too much M&B and not even touched WOTR, so I can't really compare, but I like the idea.

Keybinds for choosing the items in the menu can also be set in options now.

WHERE?!
I've been scrolling through the bloody settings for God knows how long and I can't find these darn options.