Satisfactory dedicated server mods: SMM and compatibility

Check mods and installation access

Ficsit documentation distinguishes server-compatible mods from unsupported ones. Also check the instance's Windows or Linux target. Record required versions and identify mods that supply objects already present in the save.

Ask the provider whether you can reach the installation root containing FactoryServer.exe or the corresponding server script. SFTP access limited to saves may not allow loader and mod installation. Confirm the workflow supported by the selected plan.

Add the server to Satisfactory Mod Manager

Use a Satisfactory Mod Manager release supporting dedicated servers; its documentation describes this capability from SMM 3. Open Other, then Manage Servers, and add the instance with its server type, connection details and installation path.

Use your own transfer credentials and keep them private. Stop the server and back up the world before applying changes. The manager needs the full server installation rather than a personal-file subdirectory.

Build a reproducible mod setup

Select mods marked compatible with the destination. Check dependencies, apply installation and inspect errors before starting. Give players a profile matching the selected mods' client requirements.

Begin on a copy or separate test session. Verify joining, representative modded objects, saving and restarting. A completed installation alone does not prove every mod feature works on a server.

Maintain a compatible combination

Before updating, retain the world, configuration and version list. Avoid updating clients days before the server when matching mod versions are required.

Test removal of content mods on a copy because buildings or items may depend on them. Recovery may require the complete earlier combination. This workflow concerns PC dedicated servers; it does not make consoles compatible with PC mods.

Frequently asked questions