Installing a Mod

Step 1: Subscribe Locally

Subscribe in Steam and let it download to Steam\steamapps\workshop\content\211820\<ModID>\.

Step 2: Upload to the Server

Copy each mod's contents.pak into your server's mods/ folder via SFTP, giving each a unique name:

mods/
  AvaliRace.pak
  FrackinUniverse.pak
  ImprovedContainers.pak

Step 3: Restart

The server detects new mods on boot (Asset source loaded: ...). Failures print the file and reason.

Step 4: Client Compatibility

Every player must have the same mods, or they cannot connect. The cleanest fix is a Steam Workshop collection your players one-click subscribe to. Create one at steamcommunity.com/sharedfiles/managemyworkshop/collections/?p=2&appid=211820. As a looser alternative, set checkAssetsDigest to false in the config (less strict, but mismatched assets can cause subtle issues).

Popular Mods

• Frackin' Universe: the big total overhaul. Hundreds of biomes, races, technologies. Significantly increases CPU and RAM use.
• Maple32: a content overhaul similar in scope to FU (do not run both; they conflict).
• Avali Race: popular custom race.
• Improved Containers and Enhanced Storage: container quality-of-life.
• More Action Bars: more hotkey slots.

Test mod combinations in a single-player save first, since some overhauls are mutually incompatible.

What to Read Next

• Maintenance and back up before adding or removing overhauls like FU, which can leave orphan data
• Server Configuration for the checkAssetsDigest and safeScripts settings