Satisfactory Server Quickstart

A Satisfactory dedicated server keeps the factory running while nobody is logged in. Unlike most games, its setup happens in-game through the Server Manager: you claim the server, set an admin password, and create or upload a save. This quickstart covers that flow and the few files that matter. Panel basics are in Access Your Game Server Panel.

Claim the server#

1. Start the server from the panel and wait for the console to show it listening.
2. Open Satisfactory, then Server Manager from the main menu, and click Add Server. Enter IP:7777 (Satisfactory 1.0 uses a single port for game and query; check the panel's Network tab if yours differs).
3. Claim it. The first person to connect names the server and sets the admin password. Store it in a password manager; it is what makes you the owner.
4. Create a session (a new game with the starting area and settings you want) or upload a save under Manage Saves, then Load it. The server autosaves from here on.

Everyone else adds the server the same way and, if you set one, enters the server password (separate from the admin password) to join.

Settings in the Server Manager#

• Auto pause when no players are connected, so the factory does not run without you (turn it off if you want it to).
• Auto save on player disconnect, and the autosave interval.
• Server and admin passwords, session management (which save is active), and console access for admins.

Files worth knowing#

FactoryGame/Saved/SaveGames/server/       # saves; upload .sav files here to load them from the manager
FactoryGame/Saved/Config/LinuxServer/Game.ini
FactoryGame/Saved/Config/LinuxServer/Engine.ini
FactoryGame/Saved/Config/LinuxServer/ServerSettings.ini

Raise the default player limit by adding to Game.ini (stop the server, edit, restart):

[/Script/Engine.GameSession]
MaxPlayers=8

Mods#

Satisfactory mods install with the Satisfactory Mod Manager (SMM), which supports dedicated servers: mods and their versions must match between server and clients. Install server-side via SFTP or the manager's server target, keep the list short, and update on the same day the game updates; a mismatched mod is the usual reason a server disappears from the manager after a patch.

Backups and megafactories#

Saves are single files that grow with your factory; schedule nightly backups and download a copy at each phase milestone. Big factories are CPU-bound on the server: if the console shows tick-rate warnings or the panel graphs pin CPU, a plan with more clock is a prorated upgrade.

Updates#

Coffee Stain ships updates that require server and client to match. Restart the server from the panel after a game update; the install routine fetches the current build. Experimental and Early Access branches are different builds; ask us in a ticket if you want the server on a specific branch.