Split from the now-fixed MC-147718 as per request by Mojang.
As it currently is, the Escape key is used for bringing up the game menu, as well as for exiting (or, for nested cases such as options submenus, going “up one level”) whatever user interface is currently “open”. For example, if the pause menu is open, pressing escape will close it.
It is currently not possible to bind either of these functionalities to another button, unlike most of the controls in game.
How to reproduce: note that if something is bound to the Esc key, there is no conflict shown, which shows that there is no other control registered as being bound to it, demonstrating that it is hardcoded.
Note that trying to actually bind something to the Esc key will simply unbind it instead. This is a separate issue that I will report separately. The demonstrational screenshot attached to this ticket was achieved via options.txt editing, showing that there exists functionality for binding to this key, as well as an existing translation string.
To fix: make Escape’s functionality rebindable - either both the “open game menu” and “exit current menu” functionalities should be classed under the same thing, or they should be two separate, individually rebindable controls which are both bound to Escape by default.
Linked issues
is duplicated by 1
Attachments
Comments 5
Thank you for your report!
After consideration, the issue is being closed as Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit The official Minecraft feedback site or visit the Minecraft Feedback Discord server.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
It seems contradictory to me that a report specifically requested to be made by Mojang themselves would instantly be dismissed as feature request spam. If this ticket shouldn't have existed, wouldn’t it have made more sense to say that instead? I’d have expected a WAI or Won’t Fix resolution instead if there was an internal discussion regarding this key.
To clarify, the comment on MC-147718 said:
“Removing the “Esc key functions” part of this issue. If you’d like, please submit a new ticket for the remapping of the Esc key, as a separate decision needs to be made on that.”
It is impolite to make assumptions, but for this ticket to get shot down as abusing the bug tracker to weasel in a game suggestion almost seems to imply that the closing of this ticket was a decision made by someone with no communication with anyone from 147718 - as mentioned before, Works As Intended would have been the expected resolution for a report concerning intended behaviour misinterpreted as an issue.
Is there any chance this ticket’s resolution could be reconsidered, even if it isn’t ultimately reopened, just in case there’s been a mixup somewhere?
Can confirm, relates to MC-256811