What Minecraft 1.21.7 Adds and Why Server Admins Should Care
Minecraft 1.21.7 is a small Java Edition hotfix after Chase the Skies: a new music disc and painting, data pack and resource pack version bumps, and bug fixes, plus what server admins should check before updating.
ChunkPod Team · · 5 min read
What Minecraft 1.21.7 Adds and Why Server Admins Should Care
Minecraft 1.21.7 came out on June 30, 2025, as a small Java Edition update after 1.21.6 Chase the Skies. It adds one music disc and one painting, bumps the data pack and resource pack versions, and fixes a batch of bugs left over from 1.21.6. It's mostly a hotfix, and the blog's 1.21.8 post ("What Minecraft 1.21.8 Changes for Server Admins") picks up from here.
For players, it's a quick update. For server admins, the version bumps matter more than the new content.
What's new in 1.21.7
The content side is short:
- "Lava Chicken" music disc. A new disc by Hyper Potions. It drops when you kill a baby zombie that's riding a chicken, the chicken jockey.
- A new 3x3 painting. Mojang's changelog describes it as a painting "to honor everyone's best friend", by artist Sarah Boeving.
That's all the new content. No new mobs, blocks or mechanics.
Technical changes
The changelog lists two version bumps:
- Data pack version is now 81.
- Resource pack version is now 64.
If you run data packs, check them against the new pack_format. Custom loot tables, recipes, advancements and world generation packs are the ones most likely to need a new number in pack.mcmeta. The same goes for server resource packs sent to players on join.
Bug fixes that matter on a server
Most of the fixes in 1.21.7 are client-side. The list covers rendering problems on Qualcomm and AMD graphics, startup crashes on some graphics hardware, text display z-fighting, blindness and darkness fog not working underwater, and memory leaks when resource packs reload.
One fix is worth noting for admins: the data version wasn't being written during a force upgrade. If you use --forceUpgrade to convert a world to a new version before opening it to players, that's the part of the changelog to read.
Why point releases like this can still break things
A .x release inside the 1.21 line looks small from a player's side. From a server admin's side, a few things can change under the hood, and any one of them can take a server down.
- The protocol version. When Mojang bumps the network protocol, clients on the old version can't join a server on the new build, and the other way around. On a network running Velocity or BungeeCord, the proxy also has to know the new protocol before it will forward anyone. Mojang's changelog doesn't list protocol numbers, so the release notes for your proxy and server software are where you'll see what changed.
- The data pack and resource pack versions. 1.21.7 bumps both. Older packs may load with warnings or not load at all until they declare support for the new format. A data pack that fails quietly is worse than one that errors loudly, because nobody notices until a loot table or recipe stops working.
- The world format. Once a new server version has loaded a world, going back to the old version isn't guaranteed to work cleanly. That's why a backup from before the update matters more than any backup you take after.
Plugins are the other weak spot. Anything that reaches into internal server code, like WorldEdit, some anti-cheat plugins and protocol libraries such as ProtocolLib, can break on even small internal changes. Anti-cheat and world protection are the risky ones, because when they fail silently you find out from a griefed base, not from the console. Well-maintained plugins usually list which Minecraft versions they support, and that list is the thing to check before you move.
How server software catches up
Mojang releases the vanilla server. Everything else follows on its own schedule, and 1.21.7 works the same way.
- Vanilla is available as soon as the release is out, from the launcher and from minecraft.net.
- Paper builds new versions after Mojang's release and marks early builds as experimental until the team is happy with them. Purpur and other Paper forks follow Paper, so they come a bit later.
- Spigot and CraftBukkit are built through BuildTools once the mappings are updated.
- Fabric loader rarely needs to change for a point release, but Fabric API and every mod you use has to be updated by its author. That's where modded servers wait the longest.
- Forge and NeoForge follow their own release cycles, and the mods on top of them update on their own schedules too.
- Velocity and BungeeCord have to add support for a new protocol before they can proxy the new version. Until then, a network stays on the old build even if the backend servers are ready.
On a plugin server, the slowest plugin you can't live without sets the timeline. On a modded server it's the slowest mod. Because 1.21.7 is a hotfix with little new content, there's not much to gain from rushing it on a live world before your software and plugins confirm support.
If you'd rather not manage updates yourself, ChunkPod is a Minecraft host in early access. You can join the waitlist at chunkpod.com. The free tools at chunkpod.com/tools, including the server.properties Generator, the Velocity Config Builder and the JVM Arguments Generator, are open to anyone and don't need an account.