Add Fabric mods
Know which mods belong on the server, client or both.
Know where a mod belongs#
Server-only mods change server logic or performance and do not need a player download. Client-only mods change rendering or controls and must not be placed on a dedicated server. Both-side mods add shared content or networking and need the same compatible version on server and clients.
Fabric Loader loads the mods. Fabric API is a common library many mods call. Other dependencies are separate mods one project requires. Datapacks use Minecraft’s built-in data system. Bukkit/Paper plugins do not run on a plain Fabric server.
Sodium is mainly a client rendering optimization. It normally belongs on each player’s computer, not the dedicated server.
Choose carefully#
Use Modrinth ↗ or CurseForge ↗ and prefer the project’s official page. Avoid random rehosting sites: they may serve old, modified or malicious files.
Common server-side optimization projects include Lithium, FerriteCore, Krypton, ServerCore and Alternate Current. Chunky or Fabric-compatible pregeneration tools may help exploration. Verify the exact Minecraft version, Fabric support, environment and dependencies on each project page; none is compatible with every release.
Upload a mod safely#
- 1Create a backup, then stop the server.
- 2Download the correct Fabric
.jarfor the exact Minecraft version. - 3Read the Requirements/Dependencies section.
- 4In Crafty’s file manager, open the server’s
modsfolder. - 5Upload the
.jarwithout unzipping it. - 6Start the server and read the console.
- 7Join once and test the mod’s feature.
- 8Add only a few more mods before testing again.
The official Fabric mod guide ↗ warns that even nearby patch releases can be incompatible and recommends trusted sources.
The server crashes immediately
Read the first Caused by or dependency message. Check that the file says Fabric—not Forge, NeoForge or Quilt—and is not marked client-only. Missing dependencies are usually named in the error.