Satisfactory Server Settings Explained: Autosave, Max Players and More
Satisfactory splits its dedicated server settings three ways. Most day-to-day options (autosave interval, auto pause, network quality, restart hour) are in the in-game Server Manager. Player count and a few advanced options are in Game.ini and Engine.ini. Launch arguments cover ports and seasonal events.
Below, each setting is tagged with where it lives and what could be verified. The sources are the Satisfactory Wiki's pages on dedicated servers and configuration files, written for 1.0 and later (latest patch confirmed: 1.2.4.0). Where the wiki gives no default, we say so instead of guessing.
- Edit
MaxPlayersunder[/Script/Engine.GameSession]inGame.ini; the default cap is four players. - Autosave interval is in Server Manager (minutes) or via the console command
FG.AutosaveInterval(seconds, 300 by default). Kept autosaves aremNumRotatingAutosavesinEngine.ini, three by default. - Auto Pause, Auto-Save on Player Disconnect, Network Quality, Server Restart and Auto-Load Session Name are Server Manager settings with no documented ini key.
- Server Manager settings are stored in a binary
ServerSettings.<port>.sav, not in an ini file. - Always edit ini files with the server shut down.
On this page
Where Satisfactory server settings live
| Location | What goes there |
|---|---|
| Server Manager (in game) | Server name, admin password, player password, auto-load session, auto pause, auto-save on disconnect, autosave interval, restart hour, network quality, gameplay data sharing |
Game.ini | Player limit |
Engine.ini | Autosave rotation, connection timeouts, tick rate, reliable-port range, crash reporting |
| Launch arguments | Ports, seasonal events, and any ini value via -ini: |
| Console tab in Server Manager | Commands such as server.SaveGame |
The ini files are in FactoryGame\Saved\Config\WindowsServer\ on Windows and FactoryGame/Saved/Config/LinuxServer/ on Linux, under the server install directory. They may not exist until the server has been closed gracefully once. Make ini changes with the server stopped.
Server Manager settings
These appear once you are signed in as the server administrator. The wiki documents what each does but does not list default values, so none are given here.
| Setting | What it does |
|---|---|
| Server Name | Name shown for the server |
| Admin Password | The administrator password set when the server is claimed |
| Player Password Protection | Optional join password for players; off by default |
| Auto-Load Session Name | Session whose most recent save the server loads on startup |
| Auto Pause | Pauses the game automatically when no players are connected |
| Auto-Save on Player Disconnect | Saves automatically whenever a player disconnects |
| Autosave Interval (minutes) | Saves every set number of minutes |
| Server Restart Interval (hours) | Despite the name, this sets the hour of day the server restarts, for example 06:00. It is not a repeating interval |
| Network Quality | Higher values may improve client load times and network performance at the cost of server framerate |
| Send Gameplay Data | Unticking it stops data being sent to Coffee Stain Studios |
Max players: Game.ini
The default player cap is four. To raise it, set MaxPlayers under [/Script/Engine.GameSession] in Game.ini:
[/Script/Engine.GameSession]
MaxPlayers=8You can set it without editing a file by adding a launch argument instead:
-ini:Game:[/Script/Engine.GameSession]:MaxPlayers=8The wiki is clear about the trade-off. The server is tuned for the default cap of four, and raising it may hurt stability, performance and resource use. It says up to 127 players are theoretically possible but not in practice, and suggests 16 GB of RAM may be worth having for more than four players. Raise the number in small steps and watch the server's CPU and memory while players build.
Autosave interval and number of autosaves
Two settings control autosaves, and they do different jobs.
- How often: set Autosave Interval (minutes) in Server Manager. The wiki's configuration page also documents the console command
FG.AutosaveInterval xxx, with the value in seconds and a default of 300 (five minutes). Use the Server Manager field first, and the command only if you prefer it. - How many are kept:
mNumRotatingAutosavesinEngine.ini, under[/Script/FactoryGame.FGSaveSession]. The default is three, namedSessionName_autosave_0.savthrough_2.sav.
[/Script/FactoryGame.FGSaveSession]
mNumRotatingAutosaves=10A manual save is available from the Server Manager console tab with server.SaveGame <saveName>; quote names that contain spaces. Autosaves rotate, so they are not a long-term backup. Copy the server save folder yourself before big changes.
Network settings: timeouts, tick rate, ports
These are advanced and only worth touching if you have a measured problem.
| Setting | File and section | Documented default |
|---|---|---|
InitialConnectTimeout, ConnectionTimeout | Engine.ini, [/Script/OnlineSubsystemUtils.IpNetDriver] | 30 seconds; the wiki says a higher limit may be needed in some cases |
NetServerMaxTickRate, LanServerMaxTickRate | Engine.ini, IpNetDriver and EpicNetDriver sections | 30 ticks per second; the wiki says raising it will not help with lag |
NetClientTicksPerSecond | Engine.ini, [/Script/Engine.Engine] | 30 |
PortRangeBegin, PortRangeLength | Engine.ini, [/Script/ReliableMessaging.ReliableMessagingTCPFactory] | 8888 and 512 ports |
bImplicitSend | Engine.ini, [CrashReportClient] | Set to False to stop crash report uploads (Linux uploads by default) |
For lag, the wiki says raising the tick rate will not help. The documented network trade-off is the Server Manager's Network Quality setting, which can improve client load times and network performance at the cost of server framerate.
Applying and checking your changes
- Ini edits: stop the server, edit the file, start the server, then check
FactoryGame/Saved/Logs/FactoryGame.logfor errors and join to confirm the behaviour changed. Unreal may remove lines that equal a default, so a missing line is not necessarily a lost edit. - Server Manager changes: make them while signed in as administrator. They are written to the
ServerSettings.<port>.savfile, so include that file in backups along with your saves. - Launch arguments: change them in whatever starts the server (a script, service definition or hosting panel) and restart.
Keep a note of every change you make and why. Early in a save, it is easy to forget that a lowered network setting or a raised player cap was the cause of a later problem.
Seasonal events and other launch options
To turn off seasonal events on a dedicated server, add -DisableSeasonalEvents to the launch line. The wiki also mentions a GameUserSettings.ini entry for it but describes it ambiguously, so the launch argument is the safer route.
Other launch options the wiki lists are -Port=, -ReliablePort=, -ExternalReliablePort=, -DisablePacketRouting, and on Windows -Log, -NewConsole and -Unattended.
Hosted servers expose these files differently, but the keys are the game's. Hosting with ChicagoServers? The Satisfactory server hosting page lists what is included, such as free server backups and SFTP file access.
Frequently asked questions
How do I increase max players on a Satisfactory dedicated server?
Set MaxPlayers under [/Script/Engine.GameSession] in Game.ini, or pass -ini:Game:[/Script/Engine.GameSession]:MaxPlayers=8 as a launch argument. The default cap is four, and the wiki warns higher counts can hurt stability and performance.
How do I change the autosave interval on a Satisfactory server?
Use the Autosave Interval (minutes) setting in the Server Manager, or the console command FG.AutosaveInterval with a value in seconds. The wiki documents a default of 300 seconds for the command.
How many autosaves does a Satisfactory server keep?
Three by default, named SessionName_autosave_0.sav to _2.sav. Change it with mNumRotatingAutosaves under [/Script/FactoryGame.FGSaveSession] in Engine.ini.
What does Server Restart Interval do in Satisfactory?
Despite its name it sets the time of day, such as 06:00, at which the server restarts daily. It is not a repeating interval in hours.