ModRegFixer

ModRegFixer

Join vanilla, Paper, Folia and Velocity servers with your content mods still installed. No need to swap to a second instance or swap jars.

ModRegFixer is a small client-side Fabric mod for Minecraft 26.1 – 26.3. It stops the crash you get when you join a server that doesn’t have one of your content mods (Biomes O’ Plenty, for example):

java.lang.IllegalStateException: Missing element ResourceKey[minecraft:trim_material / biomesoplenty:glowworm_silk]

Install it, keep your normal modpack, and join any server.

✨ What it does

This is not "disable all mods in multiplayer"

Sodium, Iris, AppleSkin, Xaero’s, JEI, Litematica, ModernFix and the rest are never touched. ModRegFixer works on individual registry entries and treats the server’s own registry data as the source of truth. It only removes what would crash you.

📦 Installation

1. Install Fabric Loader 0.19.5+ and Fabric API.
2. Download the file that matches your Minecraft version:
   • modregfixer-<version>+26.3.jar → 26.3
   • modregfixer-<version>+26.2.jar → 26.2
   • modregfixer-<version>+26.1.jar → 26.1, 26.1.1, 26.1.2
3. Put it in your mods folder. That’s all.

✅ Client only. Servers don’t need to install anything.

🔧 How it works (short version)

When you join a remote server, Minecraft 26.x re-checks every item’s default components against the server’s registries. If a modded item says "I am the trim material biomesoplenty:glowworm_silk" and the server has never heard of it, vanilla crashes.

ModRegFixer checks each server-dependent component of each item on its own. When a component points at something the server doesn’t have, that component is left out and the item keeps everything else.

• Nothing is faked
• No registries are modified
• Singleplayer rebuilds everything fresh every time you load a world

Example: with Biomes O’ Plenty on a vanilla server, ModRegFixer filters exactly 3 components:

biomesoplenty:glowworm_silk       -> provides_trim_material
biomesoplenty:rose_quartz_chunk   -> provides_trim_material
biomesoplenty:music_disc_wanderer -> jukebox_playable

💬 Commands (client-side)

⚙️ Configuration

File: config/modregfixer.properties

enabled=true                       # false = the mod does nothing at all
debug=false                        # log every filtered component + full server report on join
hideUnsupportedCreativeItems=true  # on non-Fabric servers, hide creative items the server can't know

You can also force any option with a JVM argument, for example -Dmodregfixer.debug=true.

⚠️ Limitations

• Modded items don’t become usable on vanilla servers. The server doesn’t have them. ModRegFixer gets you connected and keeps your client mods working. It doesn’t invent content.
• Only standard registration paths are filtered. That covers Item.Properties delayed components (trim materials, jukebox songs, fire resistance, pot patterns, tools and similar) and Fabric API’s DefaultItemComponentEvents. If a mod registers things another way and that fails, ModRegFixer logs a precise report (item, mod, missing entry) and the connection fails the same way it would without the mod. Nothing gets corrupted. Please open an issue with the log.
• It only fixes the configuration-phase component crash. Mods that send custom packets the server rejects, or that need a server-side counterpart for gameplay, still need that server support.
• Not for 1.21.x or older. This crash can’t happen there; the system involved was added in 26.1.

🗑️ Uninstalling

Delete mods/modregfixer-*.jar and, if you want, config/modregfixer.properties. The mod writes nothing else to disk.

🐛 Bugs & Source

Found a mod that still crashes? Please open an issue and attach your latest.log (run /modregfixer report first if you can connect).

Source code & issues: GitHub

Licensed under MIT.