
Vulkan Goes Live: Minecraft 26.4 Snapshot 9 Makes a Big Graphics Call
Key Points
- Vulkan is now the default graphics backend instead of being randomly assigned, and Mojang says it's no longer considered experimental.
- Dispensers are now fully data-driven, so every single dispense behavior (shooting arrows, placing boats, waxing blocks, the works) can be customized through datapacks.
- Fog finally has its own dedicated setting instead of being tied to Improved Transparency, which should fix a lot of complaints about visual trade-offs.
- The Recipe Book and Creative Inventory are now fully keyboard navigable, with narrator support to match.
- A new server property lets admins control how often connection keys rotate, part of a change to the login encryption handshake.
- Plenty of long-standing bugs got squashed, including phantoms attacking through corners and snowballs failing to knock back blocking players.
Mojang dropped 26.4 Snapshot 9 this week, and buried under the usual pile of bug fixes is one genuinely big decision: Vulkan is no longer the experimental option you had to go looking for. It's the default. There's also a quietly massive change to how dispensers work under the hood, a new fog setting for people who've been fighting with their graphics options, and a solid batch of accessibility work for keyboard and screen reader users.
This isn't a flashy content snapshot. No new mobs, no new blocks. But a few of these changes will ripple out to server admins, resource pack creators, and anyone running a datapack-heavy world.

Vulkan Is No Longer a Side Experiment
For a while now, Minecraft has been randomly tossing players between OpenGL and Vulkan to gather performance data without anyone really opting in. That phase is over. Starting with this snapshot, Vulkan is the default backend for everyone, and Mojang has dropped the "experimental" label entirely.
The plan is to ship 26.4 with Vulkan graphics API being the default one unless any critical issues are discovered before the full release.
That's a notable commitment. Graphics backend swaps are the kind of thing that can quietly break mods, shaders, and resource packs that poke at rendering internals, so if you run a server with a community built around specific shader packs or performance mods, this is worth testing before 26.4 goes final. The upside is potentially better performance on modern GPUs and drivers, especially on hardware where OpenGL has aged badly. The downside, and Mojang basically admits this themselves, is that it's still possible something critical shows up before launch and forces a rollback.
Worth remembering this has been in testing for several snapshots already. Making it the unconditional default, rather than a coin flip, suggests Mojang is fairly confident in the stability at this point. Still, if players on your server start reporting weird crashes or black screens after updating, Vulkan is the first thing to check.
Fog Gets Its Own Setting (Finally)
Previously, the Improved Fog effect was bundled into the Improved Transparency setting, which meant you couldn't get one without the other. That annoyed a lot of players who liked the transparency changes but didn't want the fog blending sky and clouds into the render distance haze. Now they're separated.
- Turn on both Improved Fog and Improved Transparency together, and you get the same look as before: sky and clouds both blend into the fog.
- Enable Improved Fog alone and only the sky blends in, clouds stay untouched.
- Want Improved Transparency without any of the fog blending? Now you can just turn Improved Fog off.
The setting is on by default for Fancy and Fabulous presets and off for Fast, which makes sense given Mojang says the performance hit is minimal but can show up on weaker hardware. Not a huge change, but exactly the kind of fine-grained control players have been asking for since the transparency rework shipped.
Dispensers Just Became a Modder's Playground
This is the part of the patch notes that's easy to skim past and probably shouldn't be. Dispense behaviors, meaning what happens when you put an item in a dispenser and hit the button, are now fully data-driven through a new dispense_behavior registry folder.
Every vanilla dispenser interaction has a name now: minecraft:shoot_projectile, minecraft:place_boat, minecraft:equip, minecraft:transform_block, and a couple dozen more. Datapacks can reference these directly, chain them in sequence, or attach a brand new minecraft:dispense_behavior data component to an item to override what it does entirely.
Some of the new behaviors are genuinely fun to poke at. There's minecraft:brush_armadillo for automated scute farms, minecraft:equip_sulfur_cube, and a block transformer system that lets dispensers wax blocks with honeycomb now. If you run a server with heavy redstone or technical Minecraft communities, this is the kind of change that gets discovered within a day of release and turned into something nobody expected.
It's a quiet change on the surface but it's the sort of infrastructure work that tends to pay off two or three updates later once people figure out what's actually possible with it.

Accessibility Gets Real Attention
The Recipe Book and Creative Inventory can both be fully operated with a keyboard now. Tab cycles through tabs, search, filters, recipes, and pages. Enter or Space places a recipe, Shift places as many as possible, and there's a new Repeat Recipe/Trade keybind (R by default) that repeats whatever you last crafted or traded, including with villagers.
Narration got the same treatment. The narrator now reads out recipe results, grid positions, tab names, and page numbers, and does the same for the Creative Inventory. This isn't a flashy feature anyone's going to make a trailer about, but it's a real improvement for players who rely on screen readers or can't use a mouse comfortably. Good to see this kind of polish land alongside the bigger rendering work instead of getting pushed to a future update.
Server Admins: Check the New Key Rotation Setting
Buried in the technical changes is a new key-rotation-period-seconds field for server.properties. It controls how often the server regenerates the keys used to establish new encrypted connections, part of a broader change to the login protocol's encryption handshake.
- Default is 60 seconds, which should be fine for most setups.
- Setting it to 0 generates a unique key for every single connection, which is more secure but adds overhead on servers with heavy player turnover.
Most admins won't need to touch this, but if you're running a server with strict security requirements or have had issues with connection spoofing in the past, it's worth knowing the option exists now.
Bug Fixes Worth Knowing About
The fix list is long, as always, but a handful actually change how the game plays:
- Phantoms could previously attack through corners, which made nighttime encounters in enclosed builds weirdly unfair. That's fixed.
- Snowballs now properly knock back players who are blocking, closing off a minor PvP exploit.
/killno longer fails against entities that recently survived absurd amounts of damage thanks to Resistance, a bug that's been quietly annoying command block builders.- A handful of
/itemcommand bugs around slot filtering and evaluation order got cleaned up, which matters if you've built anything complex around item manipulation commands. - Sound category fixes mean fire charges and fireworks shot from dispensers now use the Blocks sound category instead of being miscategorized under mob sounds, useful if your server lets players adjust sound sliders for farms.
The full list runs well past fifty entries, so if you want to go through every single fix, the original patch notes have the complete rundown with bug tracker links for each one.
What This Means Heading Into 26.4
Snapshot 9 doesn't feel like a snapshot racing toward a feature deadline. It feels like Mojang cleaning house before 26.4 locks in: finalizing the graphics backend decision, polishing accessibility work that's been building for a while, and laying data-driven groundwork that modders and datapack creators will spend months exploring after release.
For server owners, the Vulkan default is the one to actually test ahead of time. Get a few players on different hardware to try it out before the full release lands, especially anyone running older GPUs or unusual driver setups. The dispenser changes are lower stakes but worth a look if your community does anything technical.
As always with late-stage snapshots, expect a few more rounds of bug fixing before 26.4 goes final. Nothing here should be considered locked in stone just yet.