Minecraft 26.4 Snapshot 8 Fixes the Ender Dragon's Broken Flight (Finally)

Mojang dropped 26.4 Snapshot 8 this week, and the headline fix is one players have been waiting on for a genuinely long time: the Ender Dragon can fly properly again. If you've ever watched that dragon get stuck zig-zagging between two points like it forgot where the exit portal is, this snapshot is for you.

There's also new language support, a handful of balance tweaks to the frost-themed mobs Mojang's been building out this cycle, and some back-end changes to data packs and networking that server admins and datapack authors should actually pay attention to. Let's break down what's worth caring about.

The Dragon Finally Remembers How to Fly

Mojang's own patch notes open with a bit of self-deprecating honesty here:

"Well, it seems like our Ender Dragon has forgotten a thing or two about flying! In 26.4 Snapshot 8, we've fixed several issues with the dragon's flight behavior to help get it back on track."

That's putting it lightly. This snapshot closes out a cluster of bugs that have plagued the End fight for ages, including dragons diving toward players when they shouldn't, dragons getting stuck flying back and forth between two points, and incorrect vertical velocity causing erratic movement. Anyone who's grinded dragon fights for speedruns or server events knows how janky this could get.

This matters more for server owners than it might seem. Any SMP running dragon fight events, resource world resets, or custom End content has been dealing with an AI that occasionally just... breaks. A more predictable dragon means fairer fights, which matters for PvP servers and minigame maps built around the End dimension.

There's also a smaller fix in the same family: rideable entities launched by wind charges no longer have their motion stop mid-flight. Small, but if you've built contraptions around wind charge launches, it's a welcome fix.

Frost Content Keeps Getting Balanced

This snapshot cycle has introduced frost-themed additions like Frostbite mobs, Sulfur Cube archetypes, and Ice Crystals, and Snapshot 8 spends a fair bit of energy tuning them. The changes are small individually but add up to a more coherent system.

• Undead mobs are now immune to the Freezing effect entirely, which fixes the odd case of skeletons still getting chilled despite living in cold biomes without issue lore-wise.
• Ice Ball damage got nerfed. If Frostbite mobs were hitting too hard in testing, this should calm that down.
• Cold Sulfur Cubes no longer float, matching how other archetypes behave, and they stop accidentally freezing flowing water into ice.
• Snow Layers and Snow Blocks got moved next to the Snow Brick set in Creative, a tiny quality-of-life fix for builders tired of hunting through tabs.

None of this is earth-shattering on its own. But it's a good sign Mojang is iterating on new content in public rather than just shipping it and moving on. Worth watching how Frostbite and Sulfur Cubes evolve before this stuff lands in a full release.

Data Pack Validation Just Got Stricter

This is the part server admins running custom data packs need to actually read. The Data Pack version jumped to 127.0, and buried in the technical changes is a meaningful shift in how loot tables, predicates, item modifiers, and villager trades get validated.

Previously, a lot of validation issues in these registries were warnings that didn't stop a pack from loading. Now several of them are hard errors that can prevent pack loading entirely or break command compilation. Specifically:

• Recursive calls to the same element, whether through tags or namespaced IDs, will now fail to load.
• Using context values that aren't available in a given execution context is now an error. Mojang's own example: you can't use minecraft:apply_bonus (which needs tool context) inside an item ... modify command, because that command doesn't provide tool context.
• The old minecraft:command context got split into minecraft:command_predicate and minecraft:command_modifier, which could break packs referencing the old unified context.

Mojang also added a new loot_context_requirements.json report to help pack authors figure out what context is allowed where, which is a genuinely useful addition given how opaque this system has historically been. If you're running a server with heavily customized loot tables or custom enchantments, it's worth testing your data packs against this snapshot before assuming they'll carry over cleanly to the next stable release. Some packs that technically "worked" through silent failures may now just refuse to load.

Small Stuff That Matters for Plugin and Mod Devs

Two changes here are easy to skim past but worth flagging. A new pattern command argument type was added specifically to support commands added by server-side mods and plugins, letting them match against regular expressions natively instead of hacking around it with string parsing.

On the networking side, the entity position synchronization packet now includes full-precision head rotation. That's a protocol-level change that anti-cheat developers and PvP-focused plugin authors should note, since head rotation precision affects things like hit registration checks and aim-detection heuristics. It's a quiet change, but it's the kind of thing that can break a plugin relying on the old packet structure if that plugin hasn't been updated.

Rendering Changes You Won't Notice (Probably)

There's a chunk of shader and rendering work in this snapshot that's mostly invisible to players but relevant if you run shader packs or resource packs with custom rendering hooks. Terrain vertex data is now pulled from a texel buffer instead of traditional vertex buffers, and the Order-Independent Transparency shaders were converted to rely on subpasses. The water mask handling also changed, moving from the terrain depth buffer to a separate render target.

If you maintain a shader pack, this is your cue to check compatibility before the next snapshot drops. For everyone else, this is purely under-the-hood plumbing meant to make rendering more efficient down the line.

Other Fixes Worth Knowing About

• Trees growing next to unrelated logs no longer cause their leaves to decay incorrectly, which should save some builders a headache on tree farms.
• A crash related to canyon generation with misconfigured noise settings got patched, good news for anyone running custom world generation data packs.
• Entity and GUI textures now actually reload without relaunching the game, which resource pack testers will appreciate.
• Exposed bedrock in some Nether ravines has been fixed, closing off an annoying generation edge case.
• A crash tied to arrow key navigation in the statistics menu got squashed, a reminder that snapshots catch the small stuff too, not just the flashy fixes.

The full list runs much longer and covers everything from narrator fixes to music disc capitalization. If you want the exhaustive version, Mojang's original patch notes have it all.

What This Means If You Run a Server

Snapshots aren't stable releases, so don't go pushing this onto a live server expecting smooth sailing. But there are a few practical takeaways here. Test your data packs now if they lean on loot tables, item modifiers, or villager trades with complex conditions, since the validation changes could surface errors that were silently ignored before. If your server runs dragon fight events or End-based content, the flight fixes alone are reason enough to keep an eye on when this lands in a full release. And if you maintain shader packs or anti-cheat plugins, the rendering and networking changes deserve a closer look before they ship wider.

As always with snapshots, expect more iteration before this becomes part of an actual version release. Mojang's been chipping away at this frost content and dragon behavior for a few snapshots now, and Snapshot 8 feels like cleanup work rather than a flashy content drop. That's not a bad thing. Sometimes the most useful update is the one that just fixes what's been broken for a decade.