HomeGuidesMinecraft software, plugins and mods

Install mods and give your players the matching client pack

Server mods versus client mods, keeping both sides in sync, and the easiest way to hand your players the right files.

1 min readUpdated 2026-09-14Diese Anleitung auf Deutsch lesen →

Server side

On a Fabric, Forge or NeoForge server the Mods tab works like the plugin installer: search Modrinth, click install, the jar lands in mods/. Mods marked client-side only are hidden, because they would crash the server.

The rule that causes most confusion

Every mod that adds blocks, items, entities or dimensions must be on the server AND on every player's client. Mods that only change rendering, sounds or the UI (Sodium, JEI, minimap) go on the client only and are optional per player. Performance mods for servers (Lithium, FerriteCore) go on the server only.

Keep clients in sync

The reliable way: build a client modpack and hand it out.

  1. Install a launcher that understands packs: Prism Launcher or Modrinth App.
  2. Create an instance with the same Minecraft and loader version as your server, add the server mods plus the client mods your players should have.
  3. Export the instance (Prism: right-click → Export → Modrinth pack). You get one .mrpack file.
  4. Share the file. Players import it with one click; everyone has identical versions.

Whenever you add or update a mod on the server, update the pack and post the new version. Mismatched versions cause "Incompatible mods" kicks.

Mods from CurseForge

Download the jar from CurseForge in your browser and upload it to mods/ via the Files tab. The installer cannot fetch CurseForge files yet.