Keyboard / Mouse suggestions Build

Note: This will be a long one. I considered attaching it to other KB/M threads, but because it turned out to be quite long, it is better to start a new thread. Also, becasue it is a more general approach on how to get KB/M settings fixed for PC and Console gamers. I put it in Bug reporting, as for me there are too many issues to fix right now.

The Issues

Well, it looks like the ‘Keyboard and Mouse’ settings need some attention, as they’re not working properly at the moment. In fact, I think it makes playing the game a struggle on PC.

If users do not realise that these settings are bugged, they will probably exhibit unintentional behaviour, which will make things worse. This is particularly likely if the user then starts reassigning hotkeys. Not to mention the fact that Shift/Alt+Key combinations cannot be assigned to custom PC gamepads.

I struggled with the ‘dodge’ and ‘parry’ behaviour for quite some time, for example. I like setting ‘dodge’ to the middle mouse button. It’s quick and easy to click. I also like ‘parry’ on the right mouse button. That’s where the trouble started. Because ‘dodge’ wasn’t working, I started changing the ‘Keyboard & Mouse’ presets, which made things worse. I got the impression that the hotkeys sometimes worked and sometimes didn’t. Until today, I found that the game locks certain hotkeys in regardless.

While investigating the issue, I discovered that you can assign the right mouse button in the ‘Mouse and Keyboard Scheme’, even though the profile itself locks it in! Odd!

What’s more, you cannot toggle ‘dodge to mouse cursor direction’ on or off for PCs. The game forces you to perform a move dodge, which causes problems for gamers who use the WASD keys, as they can only dodge in four directions. Good luck if you’re fighting two enemies at the same time near a ledge!

While this is mostly not an issue for controller gamers, please could you add an option to ‘dodge always to mouse direction’ for PC gamers.

Darksiders Genesis is a great example of how to cater equally well for PC and console gamers. Almost every key and key combination, including “Shift+Fn” and “Alt+Ctrl+ESC”, can be assigned to any movement, action or UI keys. This solves many of the issues that the combat on PC NRFTW currently has. It also solves many issues for PC gamers using an additional gaming device, such as the Razer Tartarus. These players do not use the regular keyboard and therefore need to be able to reassign the ESC, TAB and Caps Lock keys, for example. Darksiders Genesis is probably the best example of perfect input settings for PC and console gamers alike. This includes gamers with disabilities and other devices.

Also, please do not lock the ESC key. If you do not use a standard keyboard, you cannot easily reach the ESC key. In my case, with the Razer Tartarus, every time the game forces me to press ESC, I have to move my left hand away from the gamepad to the keyboard and back again just to exit a screen, which is pretty inconvenient.

Additionally, link input settings/profiles to each character profile and copy the last used profile if the user creates a new character. This allows you to use one preset with your console and a different preset with another character for PC gaming, for example.

Suggestions

  1. Keep the keyboard profiles, but allow users to rename them.
  2. Don’t lock any mouse or key settings for those profiles and the game UI.
  3. Allow users to reassign the ESC key.
  4. Allow users to freely reassign all available keys and key combinations.
  5. Allow users to toggle between ‘Always dodge to mouse position’ and ‘Dodge while moving’.
  6. Add UI hotkeys to the keyboard settings. For example, enable reassigning the inventory and options hotkeys, such as Q, E, 1 and 3.
  7. Enable mouse clicking on all UI hotkey icons shown (e.g. [ESC] in dialogues).0
  8. Consider adding an ESDF preset next to WASD.
  9. Perhaps link the character input settings to each character profile.
  10. Like Darksiders Genesis, show all available character hotkeys to new players while playing (optionally).

Please consider implementing these changes and allowing gamers to customise them to their liking. This would not only ‘fix’ the awkward behaviour, but also free the game from presets that people don’t understand, while including gamers with disabilities.

While there are bugs and kb/m is overall a bit of a mess, some comments:

That’s not true, you can dodge towards mouse cursor just fine (at least when utilizing “Mouse and WASD” layout) as long as a directional key is not pressed.

I also have parry on RMB, works w/o issues. My run/dodge is on K in-between my movement block. Lots of keys are hardware-rebound to workaround some issues mentioned in the above thread (and that includes damn Esc key and some of the hardcoded inventory/menu keys).

My point is not that ‘dodge to mouse cursor direction’ is unavailable. It’s that you can’t just toggle it on or off as you like without searching for the best pre-defined profile that supports it.

The proposed approach is to not provide any KBM presets that have keys or actions locked in.

It is very frustrating for new players to have to search for the ‘best’ preset to support their play style. It is therefore suggested that all current predefined keys are removed, and three profiles are offered that users can use as freely as possible for as many actions and UI elements as needed.

Presets may make sense for console gamers, but not for PC gaming — especially if developers want to support gamers with disabilities too. This approach is also easier to implement, as developers do not need to determine which presets their customers require or desire.

Yea, nuances aside I fully agree there should be no hardcoded keys (whether hard or soft - like bugged V or R keys that always [try] do their default action). Regardless of the layout (to be fair, they should just allow unbinding keys normally and have 1 layout).

Hardcoded menu/inventory level keys are PITA as well. It’s crazy how rarely people responsible for implementing it never even consider case “what if someone moves out of wasd block”.