Function key can no longer be bound in macOS
Per Jinyu Meng's comment, it is possible to use external software to remap the keys. See that comment for more info.
The bug
Since 17w43a, the Function key can no longer be bound in controls in macOS. Previously, it could be bound and would show up as FUNCTION.
How to reproduce
- Go to Options > Controls.
- Select a control.
- Press the Function key to try to bind the key to the control. Notice that nothing happens; the key press is ignored.
Linked Issues
is duplicated by19
relates to7
Created Issue:
Function key can no longer be bound in macOS
Since 17w43a, the Function key can no longer be bound in controls in macOS. Previously, it could be bound and would show up as FUNCTION.
Steps to reproduce:
- Go to Options > Controls.
- Select a control.
- Press the Function key to try to bind the key to the control. Notice that nothing happens; the key press is ignored.
Since 17w43a, the Function key can no longer be bound in controls in macOS. Previously, it could be bound and would show up as FUNCTION.
Steps to reproduce:
- Go to Options > Controls.
- Select a control.
- Press the Function key to try to bind the key to the control. Notice that nothing happens; the key press is ignored.
The bug
Since 17w43a, the Function key can no longer be bound in controls in macOS. Previously, it could be bound and would show up as FUNCTION.
How to reproduce
- Go to Options > Controls.
- Select a control.
- Press the Function key to try to bind the key to the control. Notice that nothing happens; the key press is ignored.
relates to
is duplicated by
is duplicated by
is duplicated by
WorkaroundPer Jinyu Meng's comment, it is possible to use external software to remap the keys. See that comment for more info.
The bug
Since 17w43a, the Function key can no longer be bound in controls in macOS. Previously, it could be bound and would show up as FUNCTION.
How to reproduce
- Go to Options > Controls.
- Select a control.
- Press the Function key to try to bind the key to the control. Notice that nothing happens; the key press is ignored.
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
@Cole Smith I changed the keys in the script to "=" and ";". These keys are not commonly use in chat or commands.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Probably still in 1.16.1 and 20w29a since I'm seeing duplicates being created of this orignal report. (I don't own a Mac nor can I verify independetly myself, but it's probably safe to assume that this still affects newer versions).
is duplicated by
relates to
relates to
relates to
Can confirm in 24w03b, but may be Works as Intended/Won't Fix. My understanding is that Apple doesn't intend for apps (generally) to be able to intercept the function key since doing so interferes with the behavior of F1, F2, etc, which is why any apps which do wish to intercept it must use a special workaround. The fatc that Minecraft lacks such a workaround seems less like a bug and more like a choice to adhere to Apple's principles, annoying though they may be.
relates to
Duplicate of MC-121389.
Please search before creating a report to make sure your issue hasn't already been reported.
Thank you for your report!
We're actually already tracking this issue in MC-121389, so I resolved and linked this ticket 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 – π Game Wiki
Thank you for your report!
However, this issue is a Duplicate of MC-121389.
Please use the search function in the future to prevent duplicate reports.
Quick Links:
π Issue Guidelines – π¬ Community Support – π§ Customer Support – βοΈ Feedback and Suggestions – π Game Wiki
Fn key issue: MC-121389
Scrolling issue: check moderator note in MC-123773
As for the rest, please make sure you have the software installed for your mouse, and see if changing the settings as outlined in AntVenom's video fixes the issue.
Quick Links:
π Issue Guidelines – π¬ Community Support – π§ Customer Support – βοΈ Feedback and Suggestions – π Game Wiki
Thank you for your report!
We're tracking this issue in MC-121389, 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
Thank you for your report!
We're tracking this issue in MC-121389, 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-121389 describe your issue?
When will you fix thisοΌIt's very important to our Mac users. Use ctrl key to run will hurt our little finger.
Why hasn't this been fixed yet? Still not fixed in pre-4.
Is this bug that difficult to fix? What should our mac users do? buy an external keyboard? Okay. If Mojang can't fix that. I have a solution to temporary fix this problem.
{ "description": "Fn in Minecraft", "manipulators": [{ "conditions": [{ "file_paths": ["/Applications/Minecraft.app/Contents/runtime/jre-x64/1.8.0_74/bin/java"], "type": "frontmost_application_if" }], "from": { "key_code": "fn" }, "to": [{ "key_code": "equal_sign" }], "type": "basic" }, { "conditions": [{ "file_paths": ["/Applications/Minecraft.app/Contents/runtime/jre-x64/1.8.0_74/bin/java"], "type": "frontmost_application_if" }], "from": { "key_code": "semicolon", "modifiers": { "optional": ["any"] } }, "to": [{ "key_code": "fn" }], "type": "basic" } ] }To my understanding, yes, it is a complicated one. Partially because of
MC-29501, and partially because this is an issue in the library the game uses and not the game itself.I hate to be that one guy; however, @Jinyu Meng's solution is not viable. While it does let us use the "FUNCTION" key as our sprint, it makes us have to reconfigure our Dual-Wielding key. Along with that, in most scenarios, we'll have to use both hands in order to toggle our #F-keys rather than 1 as before. Using this solution also prevents us from typing the letter "F" in chat, making this extremely annoying on multiplayer as well as when you're doing command work. Lastly, using Karabiner effects ALL versions of the game, not just the 1.13 Pre-releases; moreover, making this a temporary but not great work-around
Really hoping this is fixed before the final release!
Would @Jinyu Meng's solution also be applicable to
MC-121376?Are you going to fix it? I really can't play in 1.13 because of that issue..
Please do something about that
I changed the keys in my script to "=" and ";". These keys are not commonly use in chat or commands.
Still occurs in 19w02a
Still hasn't been fixed. Really annoying. Used the fn key for changing perspective.
Why can't it just be reverted to how it was before?
Also, it affects every version from 1.13 and up
I couldn't get @Jinyu Meng's code to work initially, so I changed in the file path from "/Applications/Minecraft.app/Contents/runtime/jre-x64/1.8.0_74/bin/java" to "/Application Support/minecraft/runtime/jre-x64/jre.bundle/Contents/"
Hope this helps to anyone out there!
I use the fn key to sprint but since I can't bind it to sprint in 1.16, I have to use control, but that hurts my finger and when I sprint with it, and my attack/destroy keybind (left mouse button) doesn't work when I sprint with control.
Can confirm in 21w07a.
Can this still be reproduced in 22w16b or later?
Yes, still applies to 22w16b
i can confirm in 1.19.4
Can confirm in 24w03b, but may be Works as Intended/Won't Fix. My understanding is that Apple doesn't intend for apps (generally) to be able to intercept the function key since doing so interferes with the behavior of F1, F2, etc, which is why any apps which do wish to intercept it must use a special workaround. The fact that Minecraft lacks such a workaround seems less like a bug and more like a choice to adhere to Apple's principles, annoying though they may be.