Fabric mods

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.

Last checked: August 18, 2026. Use each project’s version filters rather than assuming every project already supports the newest game release.

Performance mods#

Install only a compatible subset and benchmark the same workload. Optimization mods can overlap or alter behavior; “more” is not automatically “faster.”

World generation#

Terralith ↗ and Tectonic ↗ are major terrain projects. They publish different formats/builds over time, including datapack or mod-oriented options. Choose one supported path, read compatibility notes and decide before players explore widely.

Changing world generation affects new chunks, not terrain already created. The border between old and new generation can be visible. Back up before adding/removing a generator and test with a new seed/world first.

Quality of life#

Useful server-side quality-of-life mods can add homes, claims, sleep changes, maps or administration without a client install—but environment varies by project. Prefer a few maintained projects with clear docs over a broad “must-have” list.

Gameplay and content#

New blocks, items, mobs, dimensions or interfaces commonly require the mod on both server and client. Match versions and configs through a pack. Removing a content mod can delete or corrupt its blocks/items, so keep the pre-removal backup.

Client-only mods#

Sodium and many minimap, shader, UI or rendering mods are client-side. Do not install a client-only rendering mod on a dedicated server unless the project’s current page explicitly supports the server environment.

Fabric project metadata can declare client, server or both. Trust the release file and documentation, not a list copied from an old video.

Upload a mod safely#

1. 1
   Create a backup, then stop the server.
2. 2
   Download the correct Fabric .jar for the exact Minecraft version.
3. 3
   Read the Requirements/Dependencies section.
4. 4
   In Crafty’s file manager, open the server’s mods folder.
5. 5
   Upload the .jar without unzipping it.
6. 6
   Start the server and read the console.
7. 7
   Join once and test the mod’s feature.
8. 8
   Add 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.