Fabric for 1.21.6+ is Here: Big Changes for Mod Developers

Fabric Updates Are Live — Time for Mod Developers to Update

Fabric has rolled out support for Minecraft 1.21.6, 1.21.7, and 1.21.8, and there's some important housekeeping happening under the hood. If you're running a Fabric server or playing with Fabric mods, be patient with developers — they'll need time to update their mods to work with these versions. Back up your worlds just in case!

The Spring Cleaning: What Got Removed

Fabric did some major cleanup by removing several long-deprecated modules that were cluttering the API. The command and keybinding modules are finally gone (some have been deprecated for nearly 5 years!), and a couple of rendering-related modules got merged into other APIs. If you're a mod developer, this means checking your dependencies — any mods relying on these old modules will need updates. The good news? This cleanup actually improves performance when setting up new development environments.

Two notable mergers happened: the client tags API was consolidated into the general tag API, and block render layer stuff moved into the rendering API. The Rendering API also ditched its Material API entirely, which the Fabric team deemed unnecessary complexity.

The Big API Rewrites

Fabric's HUD API got completely rewritten. Instead of the old system, you'll now use HudElementRegistry to register custom UI elements. The new approach gives you fine-grained control over where your HUD elements render — before vanilla chat, after all HUD layers, or wherever you need them.

Tooltips also got a fresh approach: there's now a ComponentTooltipAppenderRegistry that lets you position tooltips relative to vanilla items and other mods' additions. This prevents conflicts and makes complex item tooltip systems much cleaner.

New Capabilities for Modders

Fabric added several powerful new features: the LootTable API expanded to handle drop customization, entity tracking data handlers got their own registry (preventing conflicts between mods), and there are now dedicated events for player join/leave that fire on the main thread. Biome tagging also improved with wood-type based tags, and chunk loading level changes now trigger events.

The model loading API can now register custom "unbound" models, giving rendering mods more flexibility. There's also a new FabricSoundsProvider for datagen that makes creating sounds.json files way easier.

What This Means for Server Owners

If you're running a Fabric server, hold off on updating immediately. Give mod developers 1-2 weeks to release compatible versions. Once plugins update, the improvements to performance (especially from the API cleanup) should make things run smoother. Just make sure to back up your world before updating anything!

Minecraft's Rendering Overhaul Continues

Mojang is still in the middle of restructuring Minecraft's rendering system to separate "data extraction" from "rendering." This started in 1.21.2 and continues through these versions. Many RenderSystem methods got removed, but the same capabilities exist through the new RenderPipeline and RenderLayer system. For mod developers, this means you might need to refactor rendering code, but you're not losing functionality — just gaining more flexibility.

NBT and Data Handling Got Smoother

BlockEntity serialization now uses ReadView and WriteView abstractions instead of directly touching NBT. This handles errors better and tracks registries throughout serialization. It might look different in your code, but it's actually cleaner and more robust. Similar improvements happened with data generation — the old getOrCreateTagBuilder is now valueLookupBuilder.