Registry Blocker
Every modpack developer eventually hits the same wall: Minecraft's registry is stubborn. You can overwrite an entry with a data pack, but you cannot simply delete it. That is exactly the gap Registry Blocker fills. This lightweight, data-driven mod lets you remove registry entries outright instead of replacing them, giving you surgical control over what actually loads in your world.
Whether you are trimming a sprawling kitchen-sink pack or building a tightly curated adventure map, understanding how Registry Blocker works will save you hours of trial and error. Let's break down what it does, how to configure it, and where it fits in your workflow.
What Registry Blocker Actually Does
Registry Blocker is a data-driven mod that removes registry entries rather than overwriting them with data pack values. In vanilla Minecraft, data packs can replace an entry, but the original definition still lingers in the registry. Registry Blocker changes that by letting you specify which registry identifiers and entry identifiers should be stripped entirely.
The configuration lives in config/registry-blocker.json. The structure is straightforward: the key is the registry identifier, and the value is the entry identifier you want gone. When you reload your data packs, the config reloads alongside them, so iteration stays fast.
One important caveat: if another entry still references something you removed, you will see an error in latest.log. That is not a bug so much as a warning that your dependency chain needs attention. Cleaning up those references is part of the job.
Supported Versions and Loaders
Registry Blocker targets modern Minecraft releases where the registry system is fully data-driven, and it is built for the Fabric and NeoForge ecosystems. Because registry behavior shifts between major updates, always confirm the specific game version listed on the mod's project page before you download Registry Blocker for a production pack. Mixing an incompatible build into a pack is the fastest way to generate a wall of startup errors.
Common Use Cases
So why would you want to delete registry entries in the first place? The applications are broader than they first appear.
- Removing structures. Strip out villages, pillager outposts, or any generated feature that clashes with your custom worldgen.
- Trimming items. Delete items your pack never uses, keeping the creative inventory and recipe book clean.
- Avoiding overlaps. Disable structure sets and regroup remaining structures into a few consolidated sets so terrain generation stops fighting itself.
- Streamlining published packs. Remove development-only content before you ship a release build.
A practical example looks like this: you might block minecraft:worldgen/structure_set entries such as minecraft:villages, or remove a block like minecraft:redstone_wire if your pack replaces it entirely. The exact entries depend on your goals, but the syntax stays consistent.
Pairing With Data Dumper
Finding the right entry identifiers by hand is tedious. Registry Blocker works best alongside a data-dumping tool that can export matched registry entries using tags or regular expressions. Dump the list, identify what you want gone, and paste those identifiers into your config. This combination turns a guessing game into a repeatable process.
Pairing With Mod Sets
If you maintain a published pack, a mod-sets utility complements Registry Blocker nicely. You can disable mods that are still under development without deleting them from your workspace, keeping your release build lean while your experimental content stays intact locally.
For players who prefer a frictionless setup, the foxygame.net launcher handles the heavy lifting: it installs Registry Blocker with a single click and keeps it updated automatically, so your registry cleanup rules never break after a game patch.
How to Install Registry Blocker
Getting started is quick, and knowing how to install it correctly avoids the usual headaches.
- Install a compatible mod loader for your Minecraft version.
- Place the Registry Blocker jar file into your
modsfolder. - Launch the game once to generate
config/registry-blocker.json. - Edit the config, adding registry identifiers as keys and entry identifiers as values.
- Reload your data packs and check
latest.logfor reference errors.
Remember that Registry Blocker for Minecraft is a pack-authoring tool first and foremost. It shines when you are iterating on a custom data pack or modpack, not when you are casually tweaking a survival world.
Final Thoughts
Registry Blocker solves a problem that vanilla data packs simply cannot: true removal of registry entries. By combining it with dumping and mod-management utilities, you gain precise control over structures, items, and worldgen behavior. Confirm your Minecraft version and loader, configure carefully, and watch those reference errors in the log. Do that, and your pack will be cleaner, lighter, and far more predictable.