[MC-32778] Cannot assign keypad 5 key to motion any longer

Older versions I have mapped the `5` key on the keypad to the Back motion. But in these newer snapshots it no longer has any effect. It doesn't "register" the key. When I set it it says "NONE" in the configuration, and does nothing. Before it said NONE also, but still worked.

Comments 19

Noah Norrod 2013-09-27T22:47:33Z

Yeah. Having this problem on PC as well. Not just you!

PC/Windows 7/Lenovo B570/13w39b

Another snapshot after you found it, still no fix.

Keith Dart 2013-11-28T10:00:03Z

It's still not working in the latest snapshot (13w48b).

Thanks for responding.

PTR_91 2013-12-02T17:04:27Z

Stupid question, do you have NUM LOCK on?

Noah Norrod 2013-12-02T18:09:35Z

Grant Cohrs, this occurs when you DON'T have NUMLOCK. With it on, you would be assigning it to 5, which would work. SInce the Numpad 5 has no function, it chooses not to work. This worked until 1.6.4, and now it doesn't, which breaks my controls. When I use 1.6.4 or 1.7.2, I am forced to use the + button for jump on the numpad, as my entire control set is on the numpad.

PTR_91 2013-12-02T19:02:52Z

Sorry, but I haven't used a keyboard with a numpad while playing Minecraft since 1.6.1.

9 more comments

Torabi 2013-12-02T21:55:28Z

If you load up a version in which numpad 5 works and set it to move backwards, what does it say in the options.txt file for "key_key.back:"? If you load up a later version in which it does not work, does that line change? What does it change to?

Keith Dart 2013-12-03T03:50:37Z

My numlock is off.

In 1.6.4 the config shows:

key_key.back:0

and the GUI says NONE.

But that is actually wrong. Yet, it still works in 1.6.4. It's the same in 1.7.2, but now now longer works.

The keycode for that is actually:

keycode 84 (keysym 0xff9d, KP_Begin)

Thanks ! I'm so used to this setting (for this and other games) that having it not working really blows me up. 😉

Torabi 2013-12-03T07:03:40Z

Well... that pretty much explains it. Numpad 5 is the only key on most keyboards that has no inherent function (when numlock is off). Key codes aren't universal. Neither are scancodes. The Java constant VK_NUMPAD5 == 101. All that's relevant to Minecraft is what LWJGL returns: 76.

What probably happened in previous versions was LWJGL didn't return a keycode for that particular key, and instead returned 0, because "LWJGL returns key code 0 when a key is pressed but it doesn't know what key." Older versions of Minecraft may have naively accepted that value, but it was probably changed to either fix some other bug, or when upgrading the code to use a newer version of LWJGL.

What happens if you manually set "key_key.back:" to 76 in options.txt? Does it then function? On 1.7.X? older versions?

Keith Dart 2013-12-03T10:22:40Z

When I manually add that value the GUI now says "NUMPAD5". But pressing has no effect. I tried this on 1.7.2. I didn't try it with 1.6 yet.

PTR_91 2013-12-03T14:20:35Z

I'm guessing NONE/0 is disabled so that someone can't enable the cinematic camera without changing the controls, as it uses the control NONE by default.

PTR_91 2013-12-17T18:02:06Z

Does this still happen in 1.7.4? My keyboard lacks a numpad so I can't check...

Noah Norrod 2013-12-18T04:19:27Z

This still occurs. I don't think Mojang has even seen it. I'll tweet it to Jeb and Dinnerbone!

Note: I'm glad that this bug was reported before I even had the chance! It's pretty vital to some of our controls.

Keith Dart 2013-12-18T21:36:18Z

It's still an issue with 1.7.4. Although it does detect a keypress, as it always has, the name ends up NONE in the GUI, and zero value in the config. The real issue seems to be that you could map a zero value to an action. But now that is not allowed.

Noah Norrod 2013-12-18T22:46:01Z

Keith, dang! Now we need to find a workaround. Maybe (if this is possible) making NONE change to the Pause key, which would then be registered as the desired function. I can use the 5 as NONE in Garry's Mod and TF2 the same way, with no problem. Only seems to be affected in Minecraft.

Noah Norrod 2014-04-21T03:03:34Z

I believe that this is still an issue. Keith needs to update. Pretty sure this is the only bug that's been missed for over 25 updates.

Torabi 2014-04-21T15:09:52Z

What do you mean by "only bug that's been missed for over 25 updates"? There are currently 1113 unresolved issues older than this one. Only counting unconfirmed issues, there are still 116 that are older.

Noah Norrod 2014-04-21T21:56:41Z

Oh, I was just making a point. Didn't actually check. I was just saying that this one has been here for a long time and still hasn't even been assigned.

Wasn't stating it as fact, sorry if I gave that impression.

galaxy_2alex 2014-10-30T19:22:27Z

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.

Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been deliviered.

Keith Dart 2015-10-24T05:00:51Z

This seems to be fixed in the latest snapshot version.