Sodium Installed on Server

Sodium was installed on a server and it crashed. Sodium is a client-side rendering optimization mod, it replaces Minecraft's renderer and has no server-side function.

What does this error mean?
Sodium overhauls client rendering for higher FPS. On a server it tries to load client render classes (net.minecraft.client.render) that the dedicated server does not have, so loading fails. Sodium belongs only on the client.
Unsupported class: net.minecraft.client.render
Most Common Causes
  • The Sodium jar placed in the server mods folder.
  • Copying client rendering mods to the server.
  • Assuming Sodium improves server TPS (it does not).
  • A pack including Sodium in the server set.
  • Mirroring the client mods folder.
How To Diagnose
  1. Confirm the crash names Sodium / a client render class.
  2. Check the server mods folder for Sodium (and Iris).
  3. Recall Sodium is client-side rendering only.
  4. Look for other client rendering mods.
Recommended Fixes
  • Remove Sodium from the server
    Delete Sodium (and Iris) from the server, install them only on clients.
  • Use Lithium for server TPS
    For server performance, run Lithium (logic optimization), not Sodium (client rendering).
  • Keep rendering mods client-side
    Sodium runs on each player's client and never on the server.
  • Audit the server mods
    Remove other client-only rendering mods from the folder.
Frequently Asked Questions

No, it optimizes client rendering only. For server TPS use Lithium.

Sodium is client rendering, Lithium is server-side game logic, Lithium is the server-safe one.

Yes, on their clients. It just cannot be on the server.