Keybindings (e.g. Ctrl+A) are being mapped to the US keyboard layout even if you're using another layout
The bug
If you're using a keyboard layout where the letter A is not on the same position as on a QUERTY keyboard (for example, the French AZERTY layout), Minecraft still maps keybindings as if you were using a US/QUERTY keyboard.
How to reproduce
- Select the French AZERTY keyboard layout (other keyboard layouts are affected as well, see above).
- Type something into the chat.
- Press Ctrl+A (where A is the key directly to the right of the tab key).
- Note that nothing happens.
- Press Ctrl+Q (where Q is the key directly to the right of the CAPS LOCK key).
- Note that the text you typed into the chat is being selected.
Other keybindings are affected as well, for example F3+Q and F3+A. This also applies to Mac where for example Command+A is expected to select all text, but quits the app instead.
Code analysis
This is caused by the method glfwSetKeyCallback who returns a key code assuming a US keyboard layout.
To fix it, instead of directly testing the key code returned by glfwSetKeyCallback with the GLFW_KEY constants, it has to be converted to his printable character with the glfwGetKeyName method.
– mrpingouin1 in this comment
Linked Issues
is duplicated by44
relates to5
- Unresolved
Aeldrion- 121
- 54
- Confirmed
Normal
- Platform
- Accessibility
- accessibility azerty keybinding keyboard layout lwjgl qwerty
17w43a - 1.21
17w43a 17w43b 17w45a 17w47b 17w50a 18w01a 18w02a 18w07c 18w10d 18w16a 18w21a 18w22a 1.13-pre1 1.13-pre2 1.13-pre4 1.13-pre5 1.13-pre6 1.13-pre7 1.13-pre8 1.13-pre9 1.13-pre10 1.13 18w30a 18w30b 18w31a 18w32a 18w33a 1.13.1-pre1 1.13.1 1.13.2-pre1 1.13.2-pre2 1.13.2 18w43a 18w43b 18w43c 18w44a 18w46a 18w47a 18w48a 18w48b 18w49a 18w50a 19w04a 19w04b 19w05a 19w06a 19w07a 19w08a 19w09a 19w11a 19w11b 19w12a 19w12b 19w13a 19w14a 1.14-pre1 1.14-pre2 1.14-pre3 1.14-pre4 1.14-pre5 1.14 1.14.1 1.14.2-pre1 1.14.2-pre2 1.14.2-pre3 1.14.2-pre4 1.14.2 1.14.3-pre1 1.14.3-pre2 1.14.3 1.14.4-pre1 1.14.4-pre3 1.14.4-pre4 1.14.4-pre5 1.14.4-pre6 1.14.4 19w34a 19w35a 19w36a 19w37a 19w38b 19w39a 19w40a 19w41a 19w42a 19w45b 19w46b 1.15-pre1 1.15-pre2 1.15-pre3 1.15-pre4 1.15-pre5 1.15-pre6 1.15-pre7 1.15 1.15.1 1.15.1-pre1 1.15.2-pre1 1.15.2-pre2 1.15.2 20w06a 20w07a 20w08a 20w09a 20w10a 20w11a 20w13a 20w13b 20w15a 20w17a 20w18a 20w19a 20w20a 20w20b 20w21a 20w22a 1.16-pre2 1.16-pre3 1.16-pre5 1.16-pre6 1.16-pre7 1.16-pre8 1.16-rc1 1.16 1.16.1 20w28a 20w30a 1.16.2-pre1 1.16.2-rc1 1.16.2-rc2 1.16.2 1.16.3-rc1 1.16.3 1.16.4-pre1 1.16.4-pre2 1.16.4-rc1 1.16.4 20w46a 20w48a 20w51a 21w03a 1.16.5 21w05a 21w05b 21w06a 21w07a 21w11a 1.17-pre2 1.17 1.17.1 1.18.2 22w16b 1.19.2 22w42a 1.19.3 1.19.4 23w12a 23w14a 23w16a 23w17a 23w18a 1.20-pre1 1.20.2 1.20.4 24w13a 1.20.5-rc2 1.20.6 1.21
Created Issue:
I can't use CTRL+A to select the text in the World name entry field
Ctrl+A does nothing and I have to waste these two precious seconds of my life pressing the backspace button to delete the "New world" text.
Environment
Windows 7 professional, Java 1.8.0_91-b14, Old "alternative" launcher, Intel HD Graphics 2000 GL 3.1.0 (I have no idea of what this means), i3, not modded, no shaders
Ctrl+Adoes nothing and I have to waste these two precious seconds of my life pressing the backspace button to delete the "New world" text.The select all keybinding (ctrl+a for me) does nothing and I have to waste these two precious seconds of my life pressing the backspace button to delete the "New world" text.
I can't use CTRL+Ato select the text in the World name entry fieldI can't use CTRL+Q to select the text in the World name entry field
I can't use CTRL+Qto select the text in the World name entry fieldI can't use CTRL+A to select the text in the World name entry field
I can't use CTRL+Ato select the text in the World name entry fieldI can't use CTRL+Q to select the text in the World name entry field
I can't use CTRL+Qto select the text in the World name entry fieldI can't use CTRL+A to select the text in the World name entry field
The bug
If you're using a keyboard layout where the letter A is not on the same position as on a QUERTY keyboard (for example, the French AZERTY layout), Minecraft still maps keybindings as if you were using a US/QUERTY keyboard.
How to reproduce
- Select the French AZERTY keyboard layout (other keyboard layouts are affected as well, see above).
- Type something into the chat.
- Press Ctrl+A (where A is the key directly to the right of the tab key).
- Note that nothing happens.
- Press Ctrl+Q (where Q is the key directly to the right of the CAPS LOCK key).
- Note that the text you typed into the chat is being selected.
Original Report
The select all keybinding (ctrl+a for me) does nothing and I have to waste these two precious seconds of my life pressing the backspace button to delete the "New world" text.
The bug
If you're using a keyboard layout where the letter A is not on the same position as on a QUERTY keyboard (for example, the French AZERTY layout), Minecraft still maps keybindings as if you were using a US/QUERTY keyboard.
How to reproduce
- Select the French AZERTY keyboard layout (other keyboard layouts are affected as well, see above).
- Type something into the chat.
- Press Ctrl+A (where A is the key directly to the right of the tab key).
- Note that nothing happens.
- Press Ctrl+Q (where Q is the key directly to the right of the CAPS LOCK key).
- Note that the text you typed into the chat is being selected.
Original
ReportThe select all keybinding (ctrl+a for me) does nothing and I have to waste these two precious seconds of my life pressing the backspace button to delete the "New world" text.
The bug
If you're using a keyboard layout where the letter A is not on the same position as on a QUERTY keyboard (for example, the French AZERTY layout), Minecraft still maps keybindings as if you were using a US/QUERTY keyboard.
How to reproduce
- Select the French AZERTY keyboard layout (other keyboard layouts are affected as well, see above).
- Type something into the chat.
- Press Ctrl+A (where A is the key directly to the right of the tab key).
- Note that nothing happens.
- Press Ctrl+Q (where Q is the key directly to the right of the CAPS LOCK key).
- Note that the text you typed into the chat is being selected.
Other keybindings are affected as well, for example F3Q and F3A.
Code analysis
This is caused by the method glfwSetKeyCallback who returns a key code assuming a US keyboard layout.
To fix it, instead of directly testing the key code returned by glfwSetKeyCallback with the GLFW_KEY constants, it has to be converted to his printable character with the glfwGetKeyName method.– mrpingouin1 in this comment
Original description
The select all keybinding (ctrl+a for me) does nothing and I have to waste these two precious seconds of my life pressing the backspace button to delete the "New world" text.
I can't use CTRL+A to select the text in the World name entry fieldKeybindings (p.g. Ctrl+A) are being mapped to the US keyboard layout even if you're using another layout
The bug
If you're using a keyboard layout where the letter A is not on the same position as on a QUERTY keyboard (for example, the French AZERTY layout), Minecraft still maps keybindings as if you were using a US/QUERTY keyboard.
How to reproduce
- Select the French AZERTY keyboard layout (other keyboard layouts are affected as well, see above).
- Type something into the chat.
- Press Ctrl+A (where A is the key directly to the right of the tab key).
- Note that nothing happens.
- Press Ctrl+Q (where Q is the key directly to the right of the CAPS LOCK key).
- Note that the text you typed into the chat is being selected.
Other keybindings are affected as well, for example F3Q and F3A.
Code analysis
This is caused by the method glfwSetKeyCallback who returns a key code assuming a US keyboard layout.
To fix it, instead of directly testing the key code returned by glfwSetKeyCallback with the GLFW_KEY constants, it has to be converted to his printable character with the glfwGetKeyName method.– mrpingouin1 in this comment
Original description
The select all keybinding (ctrl+a for me) does nothing and I have to waste these two precious seconds of my life pressing the backspace button to delete the "New world" text.
The bug
If you're using a keyboard layout where the letter A is not on the same position as on a QUERTY keyboard (for example, the French AZERTY layout), Minecraft still maps keybindings as if you were using a US/QUERTY keyboard.
How to reproduce
- Select the French AZERTY keyboard layout (other keyboard layouts are affected as well, see above).
- Type something into the chat.
- Press Ctrl+A (where A is the key directly to the right of the tab key).
- Note that nothing happens.
- Press Ctrl+Q (where Q is the key directly to the right of the CAPS LOCK key).
- Note that the text you typed into the chat is being selected.
Other keybindings are affected as well, for example F3+Q and F3+A.
Code analysis
This is caused by the method glfwSetKeyCallback who returns a key code assuming a US keyboard layout.
To fix it, instead of directly testing the key code returned by glfwSetKeyCallback with the GLFW_KEY constants, it has to be converted to his printable character with the glfwGetKeyName method.– mrpingouin1 in this comment
Original description
The select all keybinding (ctrl+a for me) does nothing and I have to waste these two precious seconds of my life pressing the backspace button to delete the "New world" text.
is duplicated by
is duplicated by
The bug
If you're using a keyboard layout where the letter A is not on the same position as on a QUERTY keyboard (for example, the French AZERTY layout), Minecraft still maps keybindings as if you were using a US/QUERTY keyboard.
How to reproduce
- Select the French AZERTY keyboard layout (other keyboard layouts are affected as well, see above).
- Type something into the chat.
- Press Ctrl+A (where A is the key directly to the right of the tab key).
- Note that nothing happens.
- Press Ctrl+Q (where Q is the key directly to the right of the CAPS LOCK key).
- Note that the text you typed into the chat is being selected.
Other keybindings are affected as well, for example F3+Q and F3+A.
Code analysis
This is caused by the method glfwSetKeyCallback who returns a key code assuming a US keyboard layout.
To fix it, instead of directly testing the key code returned by glfwSetKeyCallback with the GLFW_KEY constants, it has to be converted to his printable character with the glfwGetKeyName method.– mrpingouin1 in this comment
Original description
The select all keybinding (ctrl+a for me) does nothing and I have to waste these two precious seconds of my life pressing the backspace button to delete the "New world" text.
The bug
If you're using a keyboard layout where the letter A is not on the same position as on a QUERTY keyboard (for example, the French AZERTY layout), Minecraft still maps keybindings as if you were using a US/QUERTY keyboard.
How to reproduce
- Select the French AZERTY keyboard layout (other keyboard layouts are affected as well, see above).
- Type something into the chat.
- Press Ctrl+A (where A is the key directly to the right of the tab key).
- Note that nothing happens.
- Press Ctrl+Q (where Q is the key directly to the right of the CAPS LOCK key).
- Note that the text you typed into the chat is being selected.
Other keybindings are affected as well, for example F3+Q and F3+A
.Code analysis
This is caused by the method glfwSetKeyCallback who returns a key code assuming a US keyboard layout.
To fix it, instead of directly testing the key code returned by glfwSetKeyCallback with the GLFW_KEY constants, it has to be converted to his printable character with the glfwGetKeyName method.– mrpingouin1 in this comment
The bug
If you're using a keyboard layout where the letter A is not on the same position as on a QUERTY keyboard (for example, the French AZERTY layout), Minecraft still maps keybindings as if you were using a US/QUERTY keyboard.
How to reproduce
- Select the French AZERTY keyboard layout (other keyboard layouts are affected as well, see above).
- Type something into the chat.
- Press Ctrl+A (where A is the key directly to the right of the tab key).
- Note that nothing happens.
- Press Ctrl+Q (where Q is the key directly to the right of the CAPS LOCK key).
- Note that the text you typed into the chat is being selected.
Other keybindings are affected as well, for example F3+Q and F3+A. This also applies to Mac where for example Command+A is expected to select all text, but quits the app instead.
Code analysis
This is caused by the method glfwSetKeyCallback who returns a key code assuming a US keyboard layout.
To fix it, instead of directly testing the key code returned by glfwSetKeyCallback with the GLFW_KEY constants, it has to be converted to his printable character with the glfwGetKeyName method.– mrpingouin1 in this comment
Windows 7 professional, Java 1.8.0_91-b14, Old "alternative" launcher, Intel HD Graphics 2000 GL 3.1.0 (I have no idea of what this means), i3, not modded, no shaders
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Yeah...
It is crazy...
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
MC-136132
relates to
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
Still in 1.14 Pre-Realease 2
is duplicated by
relates to
is duplicated by
relates to
still in 19w34a
is duplicated by
is duplicated by
is duplicated by
Keybindings (p.g. Ctrl+A) are being mapped to the US keyboard layout even if you're using another layoutKeybindings (e.g. Ctrl+A) are being mapped to the US keyboard layout even if you're using another layout
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Duplicates of MC-121278, caused by non QWERTY keyboard
Sounds like a duplicate of MC-121278
Forward-resolving to MC-121278
Thank you for your report!
However, this issue is a Duplicate of MC-121278.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Found the issue I was thinking of: MC-121278, "Keybindings (p.g. Ctrl+A) are being mapped to the US keyboard layout even if you're using another layout"
Thank you for your report!
However, this issue is a Duplicate of MC-121278.
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
So, if I understand this correctly, this is what you did:
- Write something
- Press Ctrl + Shift + A. The A does not appear.
- Write something else
- Everything written in Step 1 disappears.
Is this correct? If yes, that's what MC-121278 is about.
Is this MC-121278?
"Alt Gr" is equal to pressing "Alt" + "Ctrl". Now, if you hold "Alt Gr" for something like a second, it will be as if you released "Alt" but NOT "Ctrl".
Using an AZERTY keyboard, "Alt Gr" is needed for several characters that are useful for commands : " ~ " , "@" , " ^ " , "{ }" and "[ ]"
Because it simulates a locked "Ctrl", actions like deleting text or moving the cursor with arrows will be work "word by word" instead of "character by character". For example :
/give @a[distance=..10,limit=5,sort=random] minecraft:blue_wool
First, if you do a typo, you're likely to not realise about the bug and delete the whole argument, if not several of them (here, write "blue_wiil" and you have what you need to delete literally everything. Although the most annoying is often when deleting a target selector).
Now, if you want to change to "red_wool", and / or something in the target selector maybe, you will have write the whole argument again (but the most annoying is really when you delete everything just because you didn't realise the bug was there. While most people probably won't even understand what the bug is)
Another problem is that Ctrl + A selects the whole text, but the game then still writes the letter too. So because of that, whenever you press the letter "A", everything you wrote will be replaced by "a". It took me quite some time to realize that because of MC-121278.
But what it means is : if MC-121278 is solved before this one is, it will become far, FAR worse than it is now ! (as long as it's not solved, it is the letter "q" that is a real problem, but it is rather uncommon. Which is not at all the case of the letter "a")
Pressing "v" can be annoying too, but at least it won't make you lose everything, it's a less common letter, and if you pressed "c" or "x" before, you won't notice anything. Unless you needed for later use what you last copied, since you won't have anymore anything to paste. Anywhere).
Notes :
1) There is a way to stop this bug : Press the LEFT "Ctrl" key (the right one does nothing. At least for me).
2) While holding "Alt Gr", pressing another key before the bug starts ensures that it will never start (until you release then hold again "Alt Gr").
3) The bug seems to be related to a "bad" framerate (including minor / average fps drops while otherwise having a good framerate), and maybe lag spikes, although the bug never seems to start instantaneously (and a lag spike is pretty short).
Please do not mark unreleased versions as affected. You don't have access to them yet.
Thank you for your report!
However, this issue is a Duplicate of MC-121278.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Does MC-121278 describe your issue?
This is MC-121278, right?
Ah, that's unfortunate and probably not fixable because of the differences between LWJGL 2 and LWJGL 3. This report was about all keybinds being completely reset, though.
See also MC-121278, it's also about difficulties with different keyboard layouts in 1.13.
Thank you for your report!
However, this issue has been closed as a Duplicate of MC-121278.
It has been linked to this report. If you have additional information, please add it to the duplicated report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
However, this issue is a Duplicate of MC-121278.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Duplicate of MC-121278.
Ah, that's a known issue with non-QWERTY keyboards then, see MC-121278. You can use Cmd+Q instead of Cmd+A as a workaround.
Duplicates MC-121278
Sounds like MC-121278
I can only agree with @ZeNico13 (and, I mean, it's the bug update. If it's not a priority now, when will it be ?). However, and although it does not concern me anymore thanks to my new computer (but for the sake of those that are still affected), I'd like to remind you that there's also MC-127862, which will become worse if and when MC-121278 will be fixed (if it's the only one of the pair to be fixed).
In short, it would become worse because it would mean that Ctrl+A wouldn't require to actually (physically) do Ctrl+Q on the keyboard, hence with MC-127862, when writing something, it would become far, far more common to lose everything, since "A" is obviously much more common than "Q" (MC-12762 is basically the Ctrl key being virtually locked, so keyboard shortcuts can interfere, in a variety of ways, while doing something else).
Thank you for your report!
We're tracking this issue in MC-121278, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Does ctrl+q do anything. I'm referencing MC-121278
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-121278, which is a report that has not been resolved yet.
If you want, you can upvote the parent ticket, and enable watching to receive any updates about it - if you believe you have any information that may be important for this issue, please leave a comment on the parent. Please also use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
Thank you for your report!
We're tracking this issue in MC-121278, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-121278, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Does MC-121278 describe your issue?
Thank you for your report!
We're tracking this issue in MC-121278, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
What is your keyboard layout? I believe this might be MC-121278.
Duplicate of MC-121278.
Thank you for your report!
We're tracking this issue in MC-121278, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Sounds like you are using AZERTY, so the shortcut is messed up due to MC-121278. Try F3 + A instead
Thank you for your report!
We're tracking this issue in MC-121278, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
When using ctrl+a, ctrl+c, ctrl+x and ctrl+v the respective letter (a,c,x or v) will be typed this causes:
- ctrl+a replaces the entire text with just a and removes the selection
- ctrl+c replaces the selected text with c but correctly copies the text
- ctrl+x is identical to ctrl+c
- ctrl+v appends a v to the end of the text
This appears similar to MC-121278 but should be a different issue as I can recreate the issue when using US layout
Related to MC-121278
Works for me (Windows 10, idk if it matters)
Make sure the text field is actually selected.
It matters.
Just to be sure, do you rather mean CTRL+A in the title?
Otherwise I can also confirm that using CTRL+A to select text isn't working, and I have to use CTRL+Q instead.
The F3+A and F3+Q shorcuts are also affected and thefore swapped out.
It seems to be caused by the use of an azerty keyboard in my case
Using CTRL+A to select the text works for me. - Windows 10
Confirmed even more by digging a bit :
This is caused by the method glfwSetKeyCallback who returns a key code assuming a US keyboard layout.
To fix it, instead of directly testing the key code returned by glfwSetKeyCallback with the GLFW_KEY constants, it has to be converted to his printable character with the glfwGetKeyName method.
Still present in 18w01a
Still present in 18w07c
Still present in 18w10d
Confirm for 18w16a
Confirm for 18w22a
Confirm for 1.13-pre1
It's very very worrying for the French players considering the imminent arrival of the 1.13... :/
Confirmed present in 1.13-pre2
Still in 1.13-pre4
Still present in 1.13-pre5
Still in 1.13-pre6
Still in 1.13-pre7
Still in 1.13-pre9...
Still in 1.13-pre10
Is the assigned manager really fixing the bug? Because, this is a very painful bug for anyone with an AZERTY keyboard...
Especially that the 1.13 must release tomorrow! It is crazy that nobody takes seriously this bug!
Could we just have news as for the correction of the latter please? Thanks
This also affects the port of the control settings from 1.12.2 to 1.13-pre10
Still in 1.13 Release guys ....
Broken keybindings in the official release. Ouch.
I know right, especially knowing that bug was reported early
@Bertrand @Valentin @Jonathan
In my opinion, having this bug still around is still better than fixing it BUT not fixing at the same time MC-127862. For a short explanation of the issue : "Alt Gr" can cause "Ctrl" to be virtually locked. Meaning that when it's the case, typing the letter "A" (quite common letter) would delete everything (which already happens on QWERTY / QWERTZ keyboards that also have an Alt Gr key, such as german ones).
Of course, that bug isn't problematic only with "A" key, but it would make it worse.
@Azkunki Okay, but why did it work very well before and without problems? Plus, there, we are talking about keyboard shortcuts that are often used in game!
@ZeNico
I said "having this bug still around is still better than fixing it BUT not fixing at the same time MC-127862". That means "the best would be to fix them BOTH as soon as possible", not "it's better to not fix these bugs at all".
"Plus, there, we are talking about keyboard shortcuts that are often used in game!"
Except that it does not have irreversible consequences, it's annoying at most. Whereas MC-127862 is a bug that is far worse since there you can lose everything you were writing (something you might not remember well, and the bug stays active as long as you don't happen to press "Ctrl". And in top of that, only the left one works if I'm not mistaken. So if you don't know how to stop the bug, you're in for a lot of trouble, maybe up to restarting your game. Because EVERY time you will use arrow or deletion keys, it will act for the whole word). And if you fix the bug with shortcuts combinations using A (or Q / Z / W / M), as I already said, it will just make MC-127862 much worse. Because then, every single time you will type an "A" while the bug is active will instantaneously delete everything you were writing (I mean, this time you won't even have the time to realize you should stop pressing backspace (most likely) and maybe save some text from deletion, and it will occur insanely often since the letter "A" is a pretty common one. Maybe even more (a little more) in French than in English ("on vA pAs se mentir, cette combinAison de bugs est pArticulièrement chiAnte").
In other word, to never be affected by this bug even when it's active, you would manage to always write exactly what you wanted to write (so never in need to modify anything) while doing a lipogram in "A"... Good luck :/ (a lipogram in "Q" is much, much, much easier, you can't disagree on that)
NB : A "lipogram" is a text in which you purposely omit one of several letters. Doing so with the letter "E" of course is the hardest, but it's still quite a challenge as well with the letter "A". While the letter "Q" is
quitepretty easy to avoid.Still in 18w30a
Still in 18w30b
Still in 18w31a
Still in 18w32a...**
FIX PLEASE !!!!!!!!
Still in 18w33a...
Still in 1.13.1-pre1
Still in 1.13.1 RELEASE
FIX PLEASE
Still in 1.13.2-pre1...
Fix it please ! :'(
Still in 1.13.2-pre2
Still in 18w43a
Still in 18w43b
Still in18w44a :angry:
Still in 18w46a
Another developer can do it?
Still in 18w47a
Still in 18w50a
Still in 19w04a
Still in 19w05a...
Still in 19w06A
Yeah... Is the assigned manager can fix the bug please? Because, this is a very painful bug for anyone with an AZERTY keyboard...
Still in 19w07a
Still in 19w08a
Still in 19w08a
Still in 19w09a
Still in 19w11a
Still in 19w11b
Still in 19w12a
Still in 19w12b
Still in 19w13a
This is the third most voted bug and has been reported over two years ago and is still not fixed. It is really annoying. It seems that voting for a bug to be fixed doesn't matter at all in prioritizing the work ?
For other players: a decent workaround is to put your cursor at the end which is the case when you rename something in the anvil. Then press Shift+Begin (the arrow above end key), it will behave as a ctrl+a for a single line of text. Still better than nothing.
@val59000mc you can also use crtl+q instead, it works exactly like crtl+a should work
@stebo02 @Steb B
You might understand his opinion as for a game that is 10y old, and own by Microsoft, a simple ctrl+a should work, as we are used to do it on our azerty keyboard, ofc he knows that he can ctrl+q as he doesn't have any other choice so far ^^'
@Stef B
Except that if you start doing that in Minecraft, you'll get used to doing that out of Minecraft as well :/ Which then makes it annoying anywhere, not only in Minecraft. And to make it even worse, Ctrl+Q is a shortcut that can sometimes act like Alt+F4 (and you won't always get a warning saying you have unsaved changes. For instance, if I do it like that, when writing in my browser, it won't always warn me about anything, depending on what site I'm writing (although it doesn't seem to work anywhere anyway right now, for me. Which is weird, especially that I'm pretty sure it should have worked on Firefox and windows explorer (also tried on Notepad++, but I may have unbound that there, which could be an explanation). Maybe I've got some bug that makes that useless yet potentially annoying shortcut not work anymore for me ?)
@val59000mc
It's not at all the third most voted bug (it's the 287th), and it has been reported around 1.5 year ago. Which doesn't change that it's surprising such a bug is still around after so long of course, it's like they don't care (which is why I'm not active anymore here, and as well why I have much higher hopes in "you-know-what-game-I'm-talking-about" (or maybe not, but I obviously can't say here clearly what I'm talking about). At least it's quite promising on every aspect so far (and with some luck, maybe it will make Mojang wake up)).
This is a bug tracker, not a forum. This bug will be fixed when it is fixed, complaining here won't change that. Please comment here only if you have something new to add to the ticket. Off-topic comments will be removed.
If you need to discuss this issue anyway, feel free to open a thread on /r/Mojira.
Still in 19w14a
Still in 19w14a
Still in 1.14 Pre-Release 1
Can confirm in 1.14 Pre-Release 1
Still in 1.14 Pre-Release 2
Still in 1.14 Pre-Release 4.
1.14 will be released on Tuesday and this bug is still not fixed since snapshot 1.13 !
When will you solve it? It's really annoying for azerty keyboard users and even more so if we also play with versions below 1.13, we have to constantly think if we need to do Ctrl + A or Ctrl + Q
Still in 1.14 Pre-Release 5
I also have this issue. It didn't exist in previous versions. I think before 1.13
Copy and Paste are the most problematic ones.
OS: Kubuntu 18.04 (64 bit)
Still in the release (1.14) WTF
Please fix this ... (still in 1.14)
Still in 1.14.1 Release
Still in 1.14.2 Pre-Release 1
Still in 1.14.2 Pre-Release 2
If you ever fix this bug, please add customization support. Actually some of these keys are bend to specific letters for their easy access in US keyboard, not for their significance. One example is F3 + N which is switching gamemode, very useful for ops or on a creative map. With this key combination, you can currently reach both keys with one hand on any keyboard layout. If this bug is fixed, I won't be able to use this key without loosing my mouse control anymore, as F3 and N are very far away from each others on my layouts and will require to use both hands.
Still in 1.14.2 Release
Still in 1.14.3 Pre-Release 1 & 1.14.3 Pre-Release 2
Still in 1.14.3 Release
Still in 1.14.4 Release
Still in snapshot 19w35a
Still in 19w36a
I can only agree with @ZeNico13 (and, I mean, it's the bug update. If it's not a priority now, when will it be ?). However, and although it does not concern me anymore thanks to my new computer (but for the sake of those that are still affected), I'd like to remind you that there's also MC-127862, which will become worse if and when MC-121278 will be fixed (if it's the only one of the pair to be fixed).
In short, it would become worse because it would mean that Ctrl+A wouldn't require to actually (physically) do Ctrl+Q on the keyboard, hence with MC-127862, when writing something, it would become far, far more common to lose everything, since "A" is obviously much more common than "Q" (MC-12762 is basically the Ctrl key being virtually locked, so keyboard shortcuts can interfere, in a variety of ways, while doing something else).
Same. It's been affecting me for so long and I still trip over it all the time. This really needs to be fixed, it's a source of chronic frustration for the entire french playerbase.
You know you can change the Minecraft controls? I set my drop key from q to ` as I kept dropping my items when walking.
@anonymous : No. We're talking about a keyboard shortcut that can more or less work anywhere, not only on Minecraft. And for this reason, even if it was possible to change the keyboard shortcut, it would be a bad idea since you would get used to your custom shortcut on Minecraft and keep doing it outside of Minecraft as well, where it would still be Ctrl+A. If would ever get used to your custom shortcut on Minecraft (which wouldn't prevent using the wrong shortcut more or less often, even out of Minecraft, most likely).
Also, even if it was possible to change the shortcut AND that it was a thing only on Minecraft, it could still be an issue, since as you said yourself, not every key fits the way you play.
What are you doing Mojang ? It's frustrating to have some changed shortcuts (on azerty keyboard we need to use qwerty shortcut wtf ??) on a single game and this from several large versions ... Please fix this, this is really important ...
I think it's more complex than just fixing the key code. For instance, a usefull shortcut for server admins is the ability to change game mode with F3 + N. On qwerty keyboard, you can hit the 2 keys with one hand. On another keyboad (bépo), you need 2 hands. This means a simple fix could break the current accessibility being offered. So a proper fix means we would need a way of customizing those controls.
Still in 20w08a
Still in 20w18a...
This is still a thing, over 3 years later, and apparently, has been resolved by LWJGL (cf: https://bugs.mojang.com/browse/MC-121278?focusedCommentId=706194&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-706194)
all that's needed now is for someone to notice this, change a couple lines of code, and that's it
Can some please check if this is fixed in 22w16b as this snapshot comes with the latest LWJGL version.
@[Mod] Michael Wobst I checked in 22w16b and unfortunatly, the bug is still present.
Can confirm in 1.19.3.
Can confirm in 1.19.4
Can confirm: 23w12a
Can confirm in 1.20-pre1 under Linux using a french BÉPO keyword
Can confirm in 23w44a.
Confirmed in 24w12a
Can confirm in 24w14a.
Can confirm in 1.20.5-rc2.
Can confirm in 1.20.6 and 24w20a