Fix "Mod rejections" and modded version mismatches
Forge, NeoForge and Fabric compare mod lists at the door and refuse a player whose list does not match. The rejection screen names the mods, which is more help than it looks.
6 min read · Updated Oct 21, 2026 · By GuavaHost Team
The screens you will meet:
Connection Lost
Mod rejections [mod:examplemod]
Incompatible FML modded server
This server has mods that require FML/Forge to be installed on the client
Missing mods
The following mods are missing: examplemod 2.1.0, anothermod 1.4
All three are the same problem seen from different angles: the client and the server do not agree on what is installed.
Why modded Minecraft is strict about this
Plugins live entirely on the server. Players join a plugin server with a plain client and never know the plugins exist.
Mods are different. Many of them add blocks, items, entities and recipes that both sides have to know about, with matching internal IDs. If the client does not have a mod the server uses, it has no idea what a block it is being told about even is. So rather than let you join and then break in confusing ways, the loader does a handshake on connect, compares lists, and refuses mismatches up front.
That is why you cannot "just join" a modded server. Players need the same mods you do.
Step 1: Read the rejection
The rejected list is the answer, so read it properly.
| What the screen says | What it means |
|---|---|
Mod rejections [mod:x] | The client and server both have mod x, at different versions |
| Missing mods, with versions | The client does not have those mods at all |
Incompatible FML modded server | The client has no mod loader, or the wrong one |
| A mod listed that you deliberately removed | The server still has it, or the client cached an old list |
Then check the server's side. Open the Console tab in the panel and look at the lines from startup: the loader prints how many mods it loaded, and it also logs the rejection when it happens, often with more detail than the client screen gives.
Step 2: Match the loader, exactly
Mods are built for one loader and one Minecraft version, and loaders are not interchangeable.
- Forge and NeoForge are separate projects now, despite the shared history. A Forge mod does not load on NeoForge and the reverse is also true. For 1.20.2 onwards, most mods have moved to NeoForge.
- Fabric is a different ecosystem again, and most Fabric mods also need the Fabric API mod alongside them.
- Quilt is Fabric-compatible in many cases but not all.
Check all of this on the server first. The Version page under Minecraft tools in the server menu shows what you are running and lets you change it: How to change your Minecraft Java server version covers that. Then have your players match it.
The loader's own version matters too, not just Minecraft's. A client on Forge 47.2.0 and a server on Forge 47.1.3 for the same 1.20.1 will usually work, because minor loader versions are compatible, but a larger gap will not. When in doubt, tell your players the exact build number.
Mods, plugins, modpacks and datapacks explained is worth five minutes if any of this is new, because picking the wrong category is the root cause of a lot of these errors.
Step 3: Sort out client-only and server-only mods
Not every mod belongs on both sides, and putting one in the wrong place is a common cause of a mismatch.
Client-only mods make sense only on a player's computer: shader loaders, OptiFine and its alternatives, minimaps, inventory sorting, HUD tweaks, zoom. These either crash a server on startup or sit there uselessly. On Forge the crash reads Attempted to load class net/minecraft/client/... for invalid dist DEDICATED_SERVER. On Fabric it mentions environment type SERVER. Delete them from the server's mods folder and let players keep them locally.
Server-only mods are performance and administration mods the client neither needs nor should have.
Everything else needs to match on both sides. Content mods, almost without exception, belong in this group.
Well-behaved mods declare which side they are needed on, and the handshake only rejects mods that declare they must match, so a minimap on one side alone is normally fine.
Install Fabric, Forge and NeoForge server mods covers getting them onto the server, and stick to the official project pages when you download them.
Step 4: Share a pack properly, not file by file
The reliable way to get a group onto the same mod list is to give everyone the same modpack, rather than a folder of jars and good luck.
- Use a published modpack where you can. Install the pack on your server from the panel, tell your players its exact name and version, and have them install the same thing from the same launcher. Version numbers matter: pack 1.4.2 and pack 1.4.3 can have different mod lists. Install Minecraft Java modpacks covers the server side.
- If you built the pack yourself, export it from your launcher as a pack file and share that one file. Every launcher worth using can export and import. This beats zipping your
modsfolder, because the export records the loader version and the mod versions too. - Keep a note of what changed. When you add a mod to the server, your players need the same addition. A pinned message in your Discord with the current pack version saves a great deal of confusion.
- Change one thing at a time. Adding six mods and then debugging a rejection is much harder than adding one.
If your group is not technical, a published pack is worth choosing over a custom list for exactly this reason.
Step 5: When the server itself will not start
A mod mismatch on the server, rather than between server and client, shows up as a startup failure instead of a rejection. Look for:
Missing or unsupported mandatory dependencies
Mod 'examplemod' requires 'library' which is missing
That is a mod needing a library mod you have not installed. The message names it. Install the version it asks for.
Minecraft server crashing? Read the crash report covers reading these properly, including the case where the server dies before the mod list even appears.
If your players are on wildly different versions
Sometimes the honest answer is that a modded server cannot accommodate everyone. Mods are version-locked in a way plugins are not, and the translation tools that let vanilla clients join across versions do not extend to mod content. If half your group cannot run the pack, the choice is to change the pack or change the group, not to work around the handshake.
Common questions
Why do my friends need the same mods as the server?
Because many mods add blocks, items and entities that both sides have to know about by the same internal IDs. The loader compares lists when a player connects and refuses a mismatch up front, rather than letting you join and break in confusing ways later.
Can I join a Forge server with NeoForge installed?
No. Forge and NeoForge are separate projects with incompatible mod formats, despite sharing a history, so a client on one cannot join a server on the other. Check which one your server runs on the Version page and have everyone install that.
Do client-side mods like minimaps cause rejections?
Usually not, because well-behaved client-only mods declare that they do not need to be present on the server. Problems start when a client-only mod is installed on the server, which typically crashes it on startup rather than causing a rejection.
What is the easiest way to get everyone on the same mods?
Use a published modpack and tell your players the exact pack name and version number, including the minor version. If the pack is your own, export it from your launcher as a pack file and share that single file rather than a zipped mods folder.
Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.
- minecraft
- java
- mods
- forge
- fabric
- troubleshooting
Host a Minecraft Java server From $3.99/mo, with instant setup and DDoS protection.
Still need help? Our team is online 24/7 to answer questions.