Using FerriteCore on a Server and With Other Players

FerriteCore is not client-only. It runs on the server too, where it reduces the memory footprint of blockstate and model data held by the server process. This matters most for modded servers with many players and large worlds.

Server-side setup

1. Install the FerriteCore build matching your server's loader (Fabric, Forge, NeoForge, or Quilt) into the server's mods folder.

2. Restart the server and check the startup log to confirm the mod loaded without errors.

3. Monitor your server's heap usage before and after; the reduction is usually most visible on packs with many block variants.

Client and server together

1. Players do not need FerriteCore installed to join a server that has it, and vice versa — it is not a content mod, so it does not affect registry sync.

2. However, clients running it will see their own local memory drop, which helps players on low-RAM machines.

3. If a player crashes only when connecting to your server, the cause is almost always a different mod, not FerriteCore.

What it does not do

FerriteCore does not reduce world size, chunk generation time, or network traffic. If your server lags rather than runs out of memory, look at entity counts, chunk loading, and tick performance instead.