[Combined] Mouse & Keyboard keybinds resetting every session + other hardcoded functions

Wicked Bug Reporting
,
1

Tag: Settings/Controls

Playing with mouse and & keyboard, I have rebinded a few keys, specifically:

  • Quick item to: m3 (scrollclick)
  • Run to: Shift
  • Offhand use to: RMB (right mouse button)
  • Parry to: Q

This is within the Mouse and WASD control scheme under Keyboard & Mouse

What happens after exiting and booting up your game for a new session is:
– Shift will reset to Offhand use, this is easily noticable because you cannot run anymore (it is my suspicion that it retains both the new and old function of particular key)
– Q will still let you parry, but holding it lets you select consumables (as if it is the consumable keybind). Selecting the new key (m3) will function as consumables as well, my suspicion again confirmed.

This issue is like a splinter in your toe. It is so small compared to the body, yet it’s range of annoyance and pain is great.

I will go as far to say that if Thomas Mahler had this issue, it would be patched at the end of the week.

I have found a myriad of reports on this, and I share them below:
Rebinding Q button (july 17th)
[Linked] Unable to sprint/run with when holding a shield with keyboard and mouse (May 17th)
Keybindings not saving (May 15th)
M&K option 3 not keeping keybinds (May 9th)
https://forum.norestforthewicked.com/t/key-binds-not-registering-after-restating-the-game/16196 (May 6th)
[Linked] Game refuses to obey to the custom keybind (PC keyboard controls) (May 3th)

Old but still valid I think:
[Linked] Keybinding Conflict (an old multi-thread from 2024)
Key binding bug (June 2024)

So there you have it. I would love to have this patched, it sours the overall experience to much.

To better let you understand what it means in reality, here is a short video:

It looks small, it seems small, it feels huge.

Should there be a need for any transfer of sacred files by pigeon courier, let me know!

1 Like
Rebinding Q button
Rebinding Q button
2

Thank you for this summary.

Would love to get rid of this unnecessary login routine

2 Likes
3

Have You tried Making your ‘AccountSettings_LOCAL.dat’ file ‘Read Only’ ?

I’m not sure if the fact it’s a .dat file will cause any issues with being set to RO, I doubt it, seeing as how it’s static.

  • %USERPROFILE%\AppData\LocalLow\Moon Studios\NoRestForTheWicked\DataStore*.dat

I’m aware this doesn’t really fix quite a few of the issues, and the sutff mentioned, but I was just thinking for covering the “daily routine” aspect of manually re entering at the very least.

4

I have just tried it after seeing your reply, sadly no permanent result! I tried 2 ways:

  • I set the file to read-only after having it changed in-game, like the routine
  • I set it to read-only before booting up, than making changes, exit and restart the game; no changes.

If you have more ideas I would love to try them out.

Edit: oh, and the game seems to make a new AccountSettings_LOCAL.dat if the file is set to read-only, in both manners

image

In the screen snipped the LOCAL.old was the file set to read-only while it was called the top file name.

5

So are you saying you observed that .dat file go from default > read only (and changed keybinds+saw file reflect the new bindings) > relaunch and the file reflects the default config again?

EDIT: ahh ok that answers everything haha. Interesting, I did indeed wonder if the fact it was a .Dat file would change any functionality.

1 Like
6

How do I check if the file saw the keybind changes made?

edit: yeah that is to bad. There’s also none of the individual controls in the file, that’s probably worth noting.

Thanks for your attempt to help me!

7

image
image296×195 5.98 KB

When you have the game running, in any other circumstance, you could open the file after making your changes to see if any of the keywords in respect to the changed keybindings show up/are changed. However, the fact it’s just bypassing the read only by making a new file is unlucky. Actually, come to think of it, there should be no practical difference in the formats whatsoever in Windows, whether it be .dat or.txt, so it must just be set up that way, or has multiple Hard links/directories.

1 Like
8

I’m having basically the same keybinds and issues as you. Hope they look at your post and prioritize it asap.

Also for off-topic, but still keybind related; please add the possibility to rebind “Tab” and “½” (left of 1). The more freedom to rebind keys the better.

1 Like
9

I am a keyboard player. After I re-bind the keys and restart the game, the keys of using left-hand equipment and food will be restored to the default keys. In addition, I have a problem that when I hold down the run key, the character will move towards the mouse position. Obviously, you have set up a key to achieve this function. Why do you have to do this? I mainly use the keyboard to control the movement. Whenever I release the wasd key, the character will move uncontrollably. It makes my playing experience very bad.

1 Like
CTRL on the KB&M is always toggling runes
10

i moved this here to one of the existing topics.

and as far as movement goes i think thats just how it works, if you do not press WASD you character automatically moves towards your mouser position when sprinting. But i do not play KB&M so someone else might have to confirm.

1 Like
11

Zerone, as Chemile0n states it is correct that the keys resetting is a bug.

The sprint towards your mouse cursor however is not. You need to hold any wasd if you want your character to go a static direction, otherwise your sprint key will serve the same function as “walk to mouse cursor”.

I hope you can adjust to this, give it a little time!

12

This is another one.

13

Yes, your character will sprint towards the mouse position but it will slow down and even walk slowly if your mouse cursor is close to your character, which is super cool and deserves a medal. I use WASD outside combat scarcely.

1 Like
14

It makes playing experience super cool. You do not need WASD outside combat at all. Believe me, it’s much easier to navigate your character with your mouse. It’s faster and twice easier traversing very narrow places. Try to learn it, it’s not difficult, but I’d recommend to bind sprint to a mouse button.

Lumber stack in The Burrow's
15

20250916185351_1
20250916185351_11920×1200 415 KB

20250916185259_1
20250916185259_11920×1200 460 KB

What do we have here: My current keybinds is what you can see in the second screenshot. What you see in the first screenshot is absolute nonsense which happens after launch. When I move with the character keybinds ‘reset’ to what you see in the second screenshot. And again mouse button 4-5 swapped :frowning:

A few bad reviews on Steam can do miracles too :laughing:

1 Like
16

The bug of key rebinding has not been fixed. Every time I open the game, I need to manually rebind it. I’m tired of it. I hope it can be fixed as soon as possible. I really don’t like the default key position.

17

Hey zerone, i moved this here, so we have everything in one place :slight_smile:

1 Like
18

I want to know when this bug can be fixed, which means that the custom button is restored to the default after restarting the game.

19

In the control scheme “Mouse and WASD”, the offhand use binding cannot be assigned to mouse side buttons. For example, by default, if you change “run” from “Space” to “Shift” and then reassign “offhand use” from “!” to a mouse side button, saving the settings and restarting the game will result in offhand use being triggered simultaneously when running.

20

My key settings for running, support weapon, and parry are different from default setting
When I try to run in my house, the game keeps asking me whether to remove chests, cause it doesn’t seem to change with that
Running-Lshift
Parrying-M4button
Support Weapom-Rbutton
Also, whenever I use 3rd rune skill, which is R in keyboard, my character parrys, even default the key isn’t to parry
And certain keys like ’ and capslock don’t work
I thought the issues will be fixed soon but surprisingly no one mension it or they are not fixed at all with patches