MC-265853Controls bound to "SLEEP" in 1.12.2 and earlier become unbound when upgrading to the latest version
The bug
If an in-game control is bound to the SLEEP key (numeric ID 223 in options.txt) in 1.12.2 or a prior version (likely in conjunction with the system settings being configured such that the system does not enter sleep mode when the button is pressed), and then a newer version is loaded, that control will be set to "Not Bound".
It is still possible to bind controls to this key in modern versions, in which it displays as "scancode.351" (see MC-170376), leading me to believe that the control becoming unbound is not intended, although the fix for this should preferably include a fix to MC-170376 for at least this specific button.
How to reproduce
- Have a keyboard with a "sleep" key - I'm using the Microsoft Natural Multimedia Keyboard 1.0A
- Load up version 1.12.2 or earlier
- Bind a control to this key
- Quit out of the game
- Load up the latest supported version in that same profile
- Check your key binds menu
Expected results
The control that was bound to "SLEEP" would automatically be converted over to a key named something along the lines of "Sleep".
Actual results
That control now says "Not Bound".
How to fix
Have old options.txt files which bind a key to 223 convert this over to scancode.351 (or preferably an actually named key ID which replaces this) instead of key.keyboard.unknown.
Further notes
Binding controls to the SLEEP key (in both 1.12.2 and before, and the latest supported version) works for some keyboards that have it, but not others. It works for the Microsoft Natural Multimedia Keyboard 1.0A, but not the Cherry DC 2000. This is very likely to be a GLFW bug.
Linked Issues
Created Issue:
Controls bound to "SLEEP" in 1.12.2 and earlier become unbound when upgrading to the latest version
Closely relates to
MC-265731.The bug
If an in-game control is bound to the SLEEP key (numeric ID 223 in options.txt) in 1.12.2 or a prior version (likely in conjunction with the system settings being configured such that the system does not enter sleep mode when the button is pressed), and then a newer version is loaded, that control will be set to "Not Bound".
It is still possible to bind controls to this key in modern versions, in which it displays as "scancode.351" (see MC-170376), leading me to believe that the control becoming unbound is not intended, although the fix for this should preferably include a fix to MC-170376 for at least this specific button.
How to reproduce
- Have a keyboard with a "sleep" key - I'm using the Microsoft Natural Multimedia Keyboard 1.0A
- Load up version 1.12.2 or earlier
- Bind a control to this key
- Quit out of the game
- Load up the latest supported version in that same profile
- Check your key binds menu
Expected results
The control that was bound to "Sleep" would automatically be converted over to a key named something along the lines of "Sleep".
Actual results
That control now says "Not Bound".
How to fix
Have old options.txt files which bind a key to 223 convert this over to scancode.351 (or preferably an actually named key ID which replaces this) instead of key.keyboard.unknown.
Attachments2
Closely relates to
MC-265731.The bug
If an in-game control is bound to the SLEEP key (numeric ID 223 in options.txt) in 1.12.2 or a prior version (likely in conjunction with the system settings being configured such that the system does not enter sleep mode when the button is pressed), and then a newer version is loaded, that control will be set to "Not Bound".
It is still possible to bind controls to this key in modern versions, in which it displays as "scancode.351" (see MC-170376), leading me to believe that the control becoming unbound is not intended, although the fix for this should preferably include a fix to MC-170376 for at least this specific button.
How to reproduce
- Have a keyboard with a "sleep" key - I'm using the Microsoft Natural Multimedia Keyboard 1.0A
- Load up version 1.12.2 or earlier
- Bind a control to this key
- Quit out of the game
- Load up the latest supported version in that same profile
- Check your key binds menu
Expected results
The control that was bound to "Sleep" would automatically be converted over to a key named something along the lines of "Sleep".
Actual results
That control now says "Not Bound".
How to fix
Have old options.txt files which bind a key to 223 convert this over to scancode.351 (or preferably an actually named key ID which replaces this) instead of key.keyboard.unknown.
Further notes
Binding controls to the SLEEP key (in both 1.12.2 and before, and the latest supported version) works for some keyboards that have it, but not others. It works for the Microsoft Natural Multimedia Keyboard 1.0A, but not the Cherry DC 2000.
Closely relates to
MC-265731.The bug
If an in-game control is bound to the SLEEP key (numeric ID 223 in options.txt) in 1.12.2 or a prior version (likely in conjunction with the system settings being configured such that the system does not enter sleep mode when the button is pressed), and then a newer version is loaded, that control will be set to "Not Bound".
It is still possible to bind controls to this key in modern versions, in which it displays as "scancode.351" (see MC-170376), leading me to believe that the control becoming unbound is not intended, although the fix for this should preferably include a fix to MC-170376 for at least this specific button.
How to reproduce
- Have a keyboard with a "sleep" key - I'm using the Microsoft Natural Multimedia Keyboard 1.0A
- Load up version 1.12.2 or earlier
- Bind a control to this key
- Quit out of the game
- Load up the latest supported version in that same profile
- Check your key binds menu
Expected results
The control that was bound to "Sleep" would automatically be converted over to a key named something along the lines of "Sleep".
Actual results
That control now says "Not Bound".
How to fix
Have old options.txt files which bind a key to 223 convert this over to scancode.351 (or preferably an actually named key ID which replaces this) instead of key.keyboard.unknown.
Further notes
Binding controls to the SLEEP key (in both 1.12.2 and before, and the latest supported version) works for some keyboards that have it, but not others. It works for the Microsoft Natural Multimedia Keyboard 1.0A, but not the Cherry DC 2000. This is very likely to be a GLFW bug.
Closely relates to
MC-265731.The bug
If an in-game control is bound to the SLEEP key (numeric ID 223 in options.txt) in 1.12.2 or a prior version (likely in conjunction with the system settings being configured such that the system does not enter sleep mode when the button is pressed), and then a newer version is loaded, that control will be set to "Not Bound".
It is still possible to bind controls to this key in modern versions, in which it displays as "scancode.351" (see MC-170376), leading me to believe that the control becoming unbound is not intended, although the fix for this should preferably include a fix to MC-170376 for at least this specific button.
How to reproduce
- Have a keyboard with a "sleep" key - I'm using the Microsoft Natural Multimedia Keyboard 1.0A
- Load up version 1.12.2 or earlier
- Bind a control to this key
- Quit out of the game
- Load up the latest supported version in that same profile
- Check your key binds menu
Expected results
The control that was bound to "S
leep" would automatically be converted over to a key named something along the lines of "Sleep".Actual results
That control now says "Not Bound".
How to fix
Have old options.txt files which bind a key to 223 convert this over to scancode.351 (or preferably an actually named key ID which replaces this) instead of key.keyboard.unknown.
Further notes
Binding controls to the SLEEP key (in both 1.12.2 and before, and the latest supported version) works for some keyboards that have it, but not others. It works for the Microsoft Natural Multimedia Keyboard 1.0A, but not the Cherry DC 2000. This is very likely to be a GLFW bug.
Closely relates to
MC-265731.The bug
If an in-game control is bound to the SLEEP key (numeric ID 223 in options.txt) in 1.12.2 or a prior version (likely in conjunction with the system settings being configured such that the system does not enter sleep mode when the button is pressed), and then a newer version is loaded, that control will be set to "Not Bound".
It is still possible to bind controls to this key in modern versions, in which it displays as "scancode.351" (see MC-170376), leading me to believe that the control becoming unbound is not intended, although the fix for this should preferably include a fix to MC-170376 for at least this specific button.
How to reproduce
- Have a keyboard with a "sleep" key - I'm using the Microsoft Natural Multimedia Keyboard 1.0A
- Load up version 1.12.2 or earlier
- Bind a control to this key
- Quit out of the game
- Load up the latest supported version in that same profile
- Check your key binds menu
Expected results
The control that was bound to "SLEEP" would automatically be converted over to a key named something along the lines of "Sleep".
Actual results
That control now says "Not Bound".
How to fix
Have old options.txt files which bind a key to 223 convert this over to scancode.351 (or preferably an actually named key ID which replaces this) instead of key.keyboard.unknown.
Further notes
Binding controls to the SLEEP key (in both 1.12.2 and before, and the latest supported version) works for some keyboards that have it, but not others. It works for the Microsoft Natural Multimedia Keyboard 1.0A, but not the Cherry DC 2000. This is very likely to be a GLFW bug.
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
![[Mojang] Maxime Lebrot](../../../data/avatars/users/18941.svg){kind=small}
Closely relates to
MC-265731.The bug
If an in-game control is bound to the SLEEP key (numeric ID 223 in options.txt) in 1.12.2 or a prior version (likely in conjunction with the system settings being configured such that the system does not enter sleep mode when the button is pressed), and then a newer version is loaded, that control will be set to "Not Bound".
It is still possible to bind controls to this key in modern versions, in which it displays as "scancode.351" (see MC-170376), leading me to believe that the control becoming unbound is not intended, although the fix for this should preferably include a fix to MC-170376 for at least this specific button.
How to reproduce
- Have a keyboard with a "sleep" key - I'm using the Microsoft Natural Multimedia Keyboard 1.0A
- Load up version 1.12.2 or earlier
- Bind a control to this key
- Quit out of the game
- Load up the latest supported version in that same profile
- Check your key binds menu
Expected results
The control that was bound to "SLEEP" would automatically be converted over to a key named something along the lines of "Sleep".
Actual results
That control now says "Not Bound".
How to fix
Have old options.txt files which bind a key to 223 convert this over to scancode.351 (or preferably an actually named key ID which replaces this) instead of key.keyboard.unknown.
Further notes
Binding controls to the SLEEP key (in both 1.12.2 and before, and the latest supported version) works for some keyboards that have it, but not others. It works for the Microsoft Natural Multimedia Keyboard 1.0A, but not the Cherry DC 2000. This is very likely to be a GLFW bug.
The bug
If an in-game control is bound to the POWER key (numeric ID 222 in options.txt) in 1.12.2 or a prior version (likely in conjunction with the system settings being configured such that the system does not shut down when the button is pressed), and then a newer version is loaded, that control will be set to "Not Bound".
It is possible to bind controls to this key in modern versions, in which it displays as "scancode.350" (see MC-170376), leading me to believe that the control becoming unbound is not intended, although the fix for this should preferably include a fix to MC-170376 for at least this specific button.
How to reproduce
It no longer appears to be possible to bind this control to keys in 1.12.2 or earlier - this may be a LWJGL or operating system issue, so unlike in MC-265731 and MC-265853 we'll have to force this by modifying options.txt.
- Load up version 1.12.2 or earlier
- Find options.txt in .minecraft
- Change one of the numbers after a keybind to 222
- Load up 1.12.2 or earlier
- Check your key binds menu
- Load up the latest supported version in that same profile
- Check your key binds menu again
Expected results
The control that was bound to "POWER" would automatically be converted over to a key named something along the lines of "Power".
Actual results
That control now says "Not Bound".
How to fix
Have old options.txt files which bind a key to 222 convert this over to scancode.350 (or preferably an actually named key ID which replaces this, as to permit compatibility across operating systems) instead of key.keyboard.unknown.