Back to mods
ModRegFixer project artwork

CurseForge · Minecraft mod

ModRegFixer

A simple client-side mod for minecraft resolving issues where gameplay mods don't allow a player to connect to a vanilla server.

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which ModRegFixer release matches 26.1?

Updated 10 days ago
Best match for your filters modregfixer-1.0.0+26.1
Game version 26.1, 26.1.1, 26.1.2
Loader Fabric

modregfixer-1.0.0+26.1 targets 26.1, 26.1.1, 26.1.2 with Fabric. The project page does not say whether this file belongs on the client, dedicated server, or both. All 1 required mods have matching files.

Where it goes

Is ModRegFixer required on the client, server, or both?

The project page does not say whether this file belongs on the client, dedicated server, or both.

Client Source doesn’t say
Dedicated server Source doesn’t say
Loader for this release Fabric
Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

The source does not explicitly classify this release as client-only or server-only.

What else does modregfixer-1.0.0+26.1 need?

modregfixer-1.0.0+26.1 on 26.1. Every mod below is checked against that same setup.

All 1 required mods have matching files

Install Fabric API first. We found matching files for this game-version and loader setup.

Fabric API Needed by modregfixer-1.0.0+26.1
required
Matching file found Matched file: [26.1.2] Fabric API 0.155.3+26.1.2

We only count dependency files that match this setup. A file for another loader does not fill the gap.

Before you install it

Add ModRegFixer without breaking your instance.

Built for modregfixer-1.0.0+26.1 on 26.1. Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use modregfixer-1.0.0+26.1. It targets 26.1, 26.1.1, 26.1.2 with Fabric; another release may have different loader, side or dependency requirements.

  2. 02

    Bring the mods it needs

    Install Fabric API first. We found matching files for this game-version and loader setup.

  3. 03

    Put it on the correct side

    The project page does not say whether this file belongs on the client, dedicated server, or both.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside modregfixer-1.0.0+26.1. It opens that exact file at the source.

About this project

What does ModRegFixer add?

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

Where you play What happens
🏠 Singleplayer Nothing changes. Every mod, item, trim material and worldgen feature works normally.
🧩 Modded server that has your mods Nothing changes. The server provides the content, so nothing gets filtered.
🌐 Vanilla / Paper / Folia / Velocity You can connect. Item data that points at content the server doesn't have (like "glowworm silk is a trim material") is skipped for that connection only. Everything else keeps working.

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)

Command Description
/modregfixer Shows the current connection: server, brand, and what was filtered from which mod
/modregfixer report Writes a full report to logs/latest.log
/modregfixer debug on / off Turns verbose logging on every join on or off (saved to config)

⚙️ 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.

Project description from CurseForge.

Pick your setup

ModRegFixer by Minecraft version and loader

Choose the version and loader you play, then open the matching release.

5 available setups

Check the dependencies, then try the file in a copied instance before changing a world you care about.

Recent files

ModRegFixer versions and loaders

1 of 3 releases match
Clear filters

Looking for an older file? The official CurseForge project page is in Resources.