We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Following along with a Satisfactory server? Deploy yours in minutes.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!
Satisfactory guide

Satisfactory Server Settings Explained: Autosave, Max Players and More

By the ChicagoServers team · Updated · 7 min read

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. On ChicagoServers the ini files are on the Configs tab, and launch options are staff-only.

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.1). Where the wiki gives no default, we say so instead of guessing.

Quick answer
  • MaxPlayers under [/Script/Engine.GameSession] in Game.ini is the player cap; the default is four. On ChicagoServers player slots are controlled by the panel and your plan, so an edit in the file may not stick; contact support to change the cap.
  • Autosave interval is in Server Manager (minutes) or via the console command FG.AutosaveInterval (seconds, 300 by default). Kept autosaves are Rotating autosaves kept on the Startup tab, which is mNumRotatingAutosaves in Engine.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.
  • Game.ini, Engine.ini and GameUserSettings.ini on the Configs tab are all marked stop first: click Stop, edit, Save, then Start.
On this page
  1. How to change these settings on a ChicagoServers server
  2. Where Satisfactory server settings live
  3. Server Manager settings
  4. Max players: Game.ini
  5. Autosave interval and number of autosaves
  6. Network settings: timeouts, tick rate, ports
  7. Applying and checking your changes
  8. Seasonal events and other launch options
  9. Frequently asked questions

How to change these settings on a ChicagoServers server

  1. Stop the server

    Open your server in the panel and click Stop. The ini files are "stop first" files, and the Configs tab shows "Stop the server before editing this file" because the game would otherwise undo your change.

  2. Edit an ini file

    Open the Configs tab and pick Game.ini, Engine.ini or GameUserSettings.ini. Edit in the Settings view or switch to Text, paste the snippets from this guide, and click Save. A file that does not exist yet says so, and saving creates it.

  3. Change the autosave count

    On the Startup tab, change Rotating autosaves kept, then click Save startup.

  4. Start the server

    Click Start. Changes apply when the game next starts.

  5. Use Server Manager for the rest

    Sign in as administrator in the game's Server Manager for the server name, passwords, autosave interval, auto pause and network quality.

Where Satisfactory server settings live

LocationWhat 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.iniPlayer limit (on ChicagoServers, controlled by the panel and your plan)
Engine.iniAutosave rotation, connection timeouts, tick rate, reliable-port range, crash reporting
Launch argumentsPorts, seasonal events, and any ini value via -ini: (staff-only on ChicagoServers)
Startup tab (ChicagoServers)Rotating autosaves kept
Console tab in Server Manager (in game)Commands such as server.SaveGame

The game keeps the ini files in FactoryGame/Saved/Config/WindowsServer/ or FactoryGame/Saved/Config/LinuxServer/ under the server install directory. On ChicagoServers you do not need to find them: use the Configs tab. 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.

SettingWhat it does
Server NameName shown for the server
Admin PasswordThe administrator password set when the server is claimed
Player Password ProtectionOptional join password for players; off by default
Auto-Load Session NameSession whose most recent save the server loads on startup
Auto PausePauses the game automatically when no players are connected
Auto-Save on Player DisconnectSaves 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 QualityHigher values may improve client load times and network performance at the cost of server framerate
Send Gameplay DataUnticking 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 (the Configs tab, stop first). On ChicagoServers the panel writes player slots from your plan at every start, so if the value does not stick, contact support to change the cap.

Game.ini
[/Script/Engine.GameSession]
MaxPlayers=8

The game also accepts the same value as a launch argument, but launch options are staff-only on ChicagoServers:

Launch argument form (staff-only on ChicagoServers)
-ini:Game:[/Script/Engine.GameSession]:MaxPlayers=8

The 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: Rotating autosaves kept on the Startup tab on ChicagoServers. In the game's files this is mNumRotatingAutosaves in Engine.ini, under [/Script/FactoryGame.FGSaveSession]. The default is three, named SessionName_autosave_0.sav through _2.sav.
Engine.ini (what the Startup field sets)
[/Script/FactoryGame.FGSaveSession]
mNumRotatingAutosaves=10

A manual save is available from the Server Manager console tab in the game with server.SaveGame <saveName>; quote names that contain spaces. Autosaves rotate, so they are not a long-term backup. Use Back up now on the Backups tab before big changes, and star a backup to keep it.

Network settings: timeouts, tick rate, ports

These are advanced and only worth touching if you have a measured problem. On ChicagoServers they live in Engine.ini on the Configs tab.

SettingFile and sectionDocumented default
InitialConnectTimeout, ConnectionTimeoutEngine.ini, [/Script/OnlineSubsystemUtils.IpNetDriver]30 seconds; the wiki says a higher limit may be needed in some cases
NetServerMaxTickRate, LanServerMaxTickRateEngine.ini, IpNetDriver and EpicNetDriver sections30 ticks per second; the wiki says raising it will not help with lag
NetClientTicksPerSecondEngine.ini, [/Script/Engine.Engine]30
PortRangeBegin, PortRangeLengthEngine.ini, [/Script/ReliableMessaging.ReliableMessagingTCPFactory]8888 and 512 ports. On ChicagoServers the panel assigns ports, so leave these alone
bImplicitSendEngine.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 on the Configs tab, click Save, then start the server. Check the Console tab output and FactoryGame/Saved/Logs/FactoryGame.log (on the Files tab) for errors, and join to confirm the behavior 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>.sav file, so include that file in backups along with your saves (a World and settings backup on the Backups tab covers saves and configs).
  • Launch arguments: these are staff-only on ChicagoServers. If a setting needs one and has no Startup field, contact support.

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, the launch argument is -DisableSeasonalEvents. There is no Startup field for it, and launch options are staff-only on ChicagoServers, so contact support to have it added. The wiki also mentions a GameUserSettings.ini entry for it (a file the Configs tab lists) 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. On ChicagoServers the panel manages the ports for you.

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; the default cap is four, and the wiki warns higher counts can hurt stability and performance. On ChicagoServers player slots are written by the panel from your plan at every start, so contact support if an edit does not stick. A launch argument form also exists, but launch options are staff-only.

How do I change the autosave interval on a Satisfactory server?

Use the Autosave Interval (minutes) setting in the Server Manager in the game, 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. On ChicagoServers change it with Rotating autosaves kept on the Startup tab (Save startup, then Restart). In the game's files it is 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.

We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Following along with a Satisfactory server? Deploy yours in minutes.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

We offer quality support, a detailed knowledgebase, video tutorials on most topics, and even live support in case you prefer a live human.

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!