Cannot bind "caps" key in control settings

Doesn't happen on PC, so this is probably a LWJGL issue (which would still be valid). Going to take a look.

EDIT: Can't find an existing LWJGL report. Did binding caps work correctly in Minecraft 1.12.2?

Maybe only for macOS. At least it worked on pre 1.12 versions, and I used it many times.

To answer @unknown, it did work correctly in 1.12.2

Still happens in MacOS 10.13.2 and snapshot 18w01a

Still happens in 18w03a

Still occurs in 18w10d.

Still occurs in 18w11a

Still occurs in 18w15a

Still occurs in 18w16a

Still occurs in 18w19a

Same here, using MacOS (10.12.6), still occurs in 18w21a.

Still occurs in 1.13pre-1

Still occurs in 1.13pre-2, but I have figured something. I configured my controls in 1.12, and bound Capital as the Sneak button. Then I updated to 1.13pre-2 and in my control page, the sneak button is now called "Caps Lock"

Except it still doesn't work in game. So my guess is that the game still thinks the caps key is the one to sneak, but Caps Lock doesn't really exists as a keyboard key. By the way, if I try to change the key while playing in 1.13, the game won't be able to recognize my capital key as caps lock. So there isn't any known way to bind the Caps key as a control key... Hope all this made sense, I'm french so my english might be br0ken.

Can someone please check if this is still an issue in -pre4?

Yes it is, still occurs in 1.13pre-4 😞

Continues to occur in 1.13-pre6

@@unknown I'm assuming you meant to link to https://www.youtube.com/watch?v=HaXC7Al_dWc instead of attaching it? I'll add a web link to that video.

It's still not fixed now that the official release is out.

@@unknown: 1.13 is already marked as affected. Please check the affected versions before confirming an issue.

Still occurs in 18w31a

Still occurs in 18w32a

Still occurs in 1.13.1-pre1.

Still occurs in 1.13.1-pre2

Still occurs in 1.13.1

Still occurs in 1.13.2-pre1

Still occurs in 1.13.2-pre2

Still occurs in 1.13.2

Still occurs in 18w43b

Still occurs in 18w44a

Still occurs in 18w45a

Also affects macOS 10.14 and 10.14.1.

Still occurs in 18w46a

Still occurs in 18w47a and 18w47b

Still occurs in 18w48a

Still occurs in 18w48b

Still occurs in 18w49a

Still occurs in 18w50a

Still occurs in 19w02a

Still occurs in 19w03c

Still occurs in 19w04b

Still occurs in 19w05a

Still occurs in 19w06a

This is incredibly frustrating as while not entirely intended, Caps Lock is the only way to continually hit a button while AFK and not stop when the window isn't selected. It can also be force-bound by the options file but pressing the button yields nothing.

Still occurs in 19w07a

Still occurs in 19w08a and 19w08b

Still occurs in 19w09a

Still occurs in 19w11a

Still occurs in 19w12a

Still occurs in 19w12b

Still occurs in 19w13a

Still occurs in 19w14a

Still occurs in 1.14 Pre-Release 1

Still occurs in 1.14 Pre-Release 2

Still occurs in 1.14 Pre-Release 3

Still occurs in 1.14 Pre-Release 4 & 5

Still occurs in 1.14

Still occurs in 1.14.1 Pre-Release 1

Still occurs in 1.14.2

Still occurs in 1.14.3 pre-1

Seems to be fixed in 1.14 pre-3!

Others may want to test, however.

Can you please check 1.14.3-pre2? They switched to LWJGL 3.2.2 in that version (it was 3.2.1 in 1.14.3-pre1).

It also seems fixed in 1.14.3 pre-2

Great, thanks.

The relevant GLFW fix is in #1373, which was fixed in GLFW 3.3 (which LWJGL 3 updated to). There's also issue #1368 which says that it's possible to get a check for when Caps Lock is enabled/disabled, but it's harder to handle it as an actual key. To my understanding, you mac people are used to having Caps Lock act as a key that's held down when it's on (so you keep shifting), which is the behavior they just reimplemented. (I should note that at least the last time I checked, other platforms use it as a real key so you don't get this hold effect. But if it's back to the state you're expecting, that's probably the fix you wanted in the first place.)

Affects 1.14.4 and 19w34a, despite 1.14.3 fixing it. Please reopen.

Affects 19w35a

Affects 19w36a and 19w37a

Affects 19w38a and 19w38b

Affects 19w39a

Affects 19w40a

Affects 19w41a

To my understanding, the underlying complaint here was that you could no longer bind a key that toggled sneak (which caps lock happened to do on macOS prior to LWJGL 3, though not on other platforms IIRC). If I'm not remembering wrong, I'm pretty sure they added an option to specify sneak and sprint as toggleable keys in 19w41a. So while you still presumably can't use caps lock, you can emulate the effect you were originally looking for with another key.

@Pokechu22 It's still in the wrong place on the keyboard for what I'm used to (and presumably other people).

@Pokechu22 While it's true that toggle was added for shift, that's not the only use for the caps key. You're still unable to say "toggle" the right-click (or any other) action.

Affects 19w42a

Affects 19w44a, 19w45a, 19w45b, 19w46a, 1.15-pre1, 1.15-pre2, 1.15-pre3, 1.15-pre4

Also affects 1.15-pre5, 1.15-pre6, 1.15-pre7, 1.15, 1.15.1-pre1

Note that we can't easily set older affected versions, only the most recent ones (it's possible to manually do it via the API, but if it's something that would be clearly covered by another span, there isn't much of a point; it's only worth it if there's specific versions in between doesn't happen in, which is unlikely here)

1. Noted

2. Affects 1.15.1

Affects 1.15.2-pre1

Affects 1.15.2-pre2

Bug does not occur on windows or linux systems, I believe.

Mac is the only platform affected by this problem.

Try changing your keyboard settings. Above is a photo of keyboard settings. I am a windows user because apple blows.

Change it to that or from that? Mine (and the default) is set to this:

Changing it to how that screen shot is does two things:

1. Disables caps lock entirely

2. Does not fix the issue

Affects 1.15.2

Affects 20w06a

Affects 20w07a

Affects 20w08a

Affects 20w09a

Affects 20w10a

Affects 20w11a

Affects 20w12a

Affects 20w13a

Affects 20w13b

Affects 20w14a

Affects 20w15a

Affects 20w16a

Affects 20w17a

Affects 20w18a

Affects 20w19a

Affects 20w20b

Affects 20w21a

Affects 20w22a

Affects 1.16-pre1

Affects 1.16-pre2

Affects 1.16-pre3

Affects 1.16-pre4

Affects 1.16-pre5

Affects 1.16-pre6

Affects 1.16-pre8

Affects 1.16-rc1

I no longer use Mac as my main gaming machine, so I would like Avakining to be the reporter of this bug.

Affects 1.16.1

Affects 20w27a

Affects 20w28a

Affects 20w29a

Affects 20w30a

Affects 1.16.2-pre1

It's worth noting (I think because of this change) that any installation of Minecraft Forge since 1.14.3-27.0.0 has fixed this bug.

Could it be possible for something similar to be incorporated into vanilla?

Affects 1.16.2-pre2

Affects 1.16.2-pre3

Affects 1.16.2-rc1

Affects 1.16.2

Fixed in 22w16a, likely due to LWJGL being updated to 3.3.1

I can confirmed fixed in 22w16a