Balm and Client-Only Mods Explained

Understand why dependency placement follows the mod that requests it. Learn more about Balm Mod.

Check the dependent mod first

A client-only mod runs in a different environment from a dedicated-server mod. Read the dependent project's side requirements and the selected release details before deciding where its dependencies belong. Do not assume that every library installed by your client should also be copied to the server. The appropriate setup depends on the mods and releases you actually use.

Keep the environments distinct

Maintain separate client and server file lists when their contents differ. A server pack may need a dependency that your client also uses, but that overlap is not a rule for every installed mod. Likewise, a local successful launch does not demonstrate that the dedicated server has the correct requirements. Inspect each environment independently when a dependency message appears.

Verify the intended workflow

Test client startup for a client-only setup. When the chosen mods require a server component, also check server startup and a connection from the intended client. Keep logs from both sides when troubleshooting. Compare the reported requirements rather than copying every client JAR onto the server as a general response to an error.