When attempting to switch to a different input method, Minecraft automatically switches it back to what is usually the last used English keyboard layout. (Other times, it will be automatically switched back to the system default “ABC.” I cannot find any way to predict this behavior.)
This makes it impossible to type in any language that does not use the Latin alphabet, such as Chinese, Japanese, Russian, Armenian, &c., as well as impossible to type characters that may not be included in the user’s English-language layout, such as â, ö, ê, ü, &c. If the user changes their input method, the game should respect this.
From what I’ve found online, this is supposedly the result of a change to the game to automatically switch the user’s input method based on the language they’ve selected in-game, though I haven’t found any mention of this in the game’s changelogs, and trying the same input methods while using their matching language does not solve the problem. (Regardless, there would be plenty of scenarios where someone might want to type in multiple languages without changing their in-game language option.)
Environment
MacOS Tahoe 26.2
Linked issues
duplicates 1
Comments 3
Firstly, yes, this seems to be the same issue. I’m not sure why I couldn’t find it when searching existing reports. Secondly, from my testing, the issue is mostly fixed in the current snapshot, though the RIME IME I use seems to reset to it’s default input mode (Latin alphabet) when exiting an input field, which differs from the behavior of other IMEs, such as the MacOS’s built-in Japanese input, as well as behavior in previous versions of the game.
The layout selected by the system itself is not changed, though, so switching back when opening a new text field is trivial, (a single key press) so I can understand if this is too minor and / or niche of an issue to bother with.
Sorry for taking up your time!
Does MC-308219, or one of the issues linked as related to it (see the Issue Links Panel button on the right-hand side), describe your issue? And does the issue still occur in the latest snapshot (currently 26.3 Snapshot 6)?