Buried in the Wilderness Bound changelog, under a heading most players scrolled straight past, is the largest under-the-hood change Minecraft has shipped in years:
Minecraft now uses SDL3 instead of GLFW for window management, input, and platform integration.
Two days later, the mod ecosystem is finding out what that means.
What was replaced
GLFW is a small library that handles the unglamorous parts of running a game: opening a window, reading the keyboard and mouse, talking to the operating system. Minecraft has used it for over a decade and almost nobody had reason to learn its name.
SDL3 does the same job with a wider remit – broader controller support, better handling of modern display servers, and a considerably more active development pace. Swapping one for the other touches every input event and every window operation in the game.
The change you will actually notice
One line further down the same section:
Keyboard input now uses SDL scancodes for physical key positions and SDL keycodes for layout-dependent text editing shortcuts.
Read that alongside a separate entry under UI – “Key bindings now use physical keys instead of keyboard-layout-specific key codes” – and the practical result is that a keybind is now tied to where a key sits on the board rather than what letter the operating system thinks it produces.
On a QWERTY layout this changes nothing at all. On AZERTY, QWERTZ, Dvorak or any non-Latin layout it fixes a decade-old annoyance where the movement keys landed in the wrong physical positions.
Everything else the swap brought with it
- The Raw Input mouse setting is gone – mouse input now always uses relative mouse mode in game.
- Borderless Fullscreen is now the default fullscreen mode.
- Switching between Borderless and Exclusive Fullscreen no longer requires a restart.
- On Linux, the game now uses and prefers Wayland natively where available.
- On macOS, holding a key while typing now shows the native accent and candidate popup.
- A new “Quit Shortcuts” option in Controls decides whether Alt+F4, Cmd+Q and Cmd+W can close the game.
That last one is small and welcome. Closing Minecraft by accident while reaching for something else is a widely shared experience.
The bug list tells the same story
Several fixes in the same release only make sense as consequences of the swap: the game not using borderless fullscreen (MC-121367), focus not handing off when clicking links on Wayland (MC-311113), and the window incorrectly restoring to a borderless windowed state when pressing Windows and Down in fullscreen (MC-311722).
Fullscreen behaviour has been churning quietly through this whole development cycle, and the mid-cycle snapshot that first touched it reads differently now that the reason underneath is visible.
What has already broken
Freecam shipped 1.5.0-alpha.1 on 16 September with a fix and an unusually direct explanation. Its “tripod” keybindings – F4 held together with a hotbar number key – had stopped working, and the author’s note says exactly why: 26.3 moved from GLFW to SDL for input handling, which inadvertently broke the combination.
That is the shape of the problem. Nothing about a camera mod is related to windowing, but anything reading a key combination is now reading it through a different system. The mod’s release-day build is covered in our piece from Tuesday.
And on the rendering side
Sodium Extra 0.9.4, also on 16 September, reworked its macOS Reduce Resolution option to use SDL’s high pixel-density window handling instead of its own workaround. In the same release it removed the Wayland and XWayland fullscreen resolution option entirely, because Sodium now provides that support.
Both are the same pattern: a mod that had been compensating for a platform gap no longer needs to, because the new backend closes it. The full release notes have the detail.
What to check on your own setup
- Any keybind using a modifier plus another key – combinations are where the breakage is concentrated.
- Controller bindings, if you play with a pad. That path changed the most.
- Fullscreen mode, since the default moved to Borderless.
- Non-QWERTY layouts – your binds may now sit where you always wanted them, which means they have moved.
- On Linux, whether the game picked Wayland, and whether that is what you want.
Why it is worth knowing about
Backend swaps produce a long tail of bugs in places with no obvious connection to the change. A chat mod breaks. A camera mod loses a keybind. A rendering mod discovers its platform workaround is now redundant.
For the next few weeks, when something stops working in 26.3 and the cause makes no sense, this is the first thing worth suspecting. Mod authors will also fix it faster if bug reports mention the input path rather than only the symptom.
Why Mojang would take this on
Replacing a windowing library is a large amount of work with no feature to show for it, which is usually a sign the old one had become a ceiling rather than a floor.
The visible payoffs in this release point at what that ceiling was: native Wayland on Linux, proper text input handling on macOS, borderless fullscreen that behaves, and fullscreen mode switching without a restart. Every one of those is a platform-integration problem rather than a game problem.
What it sets up
- Controller support on a library built around it, rather than bolted on.
- Display-server handling that keeps pace with Linux desktop changes.
- Text input that respects the operating system’s own conventions.
- Fewer per-platform special cases in the game and in mods.
None of that arrives fully formed in the first release. Backend work is infrastructure, and infrastructure is judged over the next several versions rather than this one.
Images: Controlify project gallery on Modrinth.