Managing Your Satisfactory Dedicated Server — Admin Commands and Tools

Running a Satisfactory dedicated server involves more than keeping it online. This guide covers the administration tools you have as a server owner on LOW.MS — the in-game Server Manager, the limited server console, player management, scheduled restarts, and the LOW.MS control panel for tasks the game client cannot handle.

Admin authentication

Before you can manage your server, you need to be authenticated as an administrator.

Becoming an admin

The person who claims the server during first-time setup automatically becomes the first admin. To grant admin access to other players:

1. Open the Server Manager in Satisfactory and select your server.
2. You will be prompted to enter the Admin Password — this is the password set when the server was first claimed.
3. Once authenticated, you have full administrative control.

Any player who knows the admin password can authenticate as an admin. Keep this password private and only share it with trusted players.

Admin vs player passwords

• Admin Password — grants full server control: settings, saves, console, shutdown. Required for any administrative action.
• Player Password — optional. Restricts who can join the game. Players only need this password to connect and play, not to administer.

Using the in-game Server Manager

The Server Manager (accessed from Satisfactory's main menu) is the primary tool for server administration. Once authenticated as admin, you have access to several tabs.

Status tab

• View the current session name, number of connected players, and server uptime.
• Create Game — start a new world.
• Load Game — load a different save file.
• Save Game — trigger an immediate manual save.

Players tab

• View all currently connected players.
• Kick Player — disconnects a player immediately. They can rejoin, so kick is useful for temporary disruption or to free up a slot, not as a permanent measure.

Note that the in-game Server Manager does not currently expose a built-in ban feature on Satisfactory 1.0+ — only kick. There is no documented ban list file or persistent ban mechanism in the dedicated server. Ban functionality is a long-standing feature request on Coffee Stain's official Q&A site, but as of writing it has not been implemented. See the player management section below for the workaround.

Server Settings tab

• Change the Server Name displayed in the Server Manager.
• Update the Player Password or remove it entirely.
• Adjust the Admin Password (all current admins will need the new password to re-authenticate).
• Configure Autosave Interval and Autosave Count (how many rotating autosaves to keep).
• Set Network Quality to Ultra. This is the single most impactful setting for multiplayer feel — see the server settings guide for context.

Console tab

The Console tab in the Server Manager runs server commands directly. Satisfactory's documented server console surface is small and has changed across versions; the most reliable command worth knowing is quit, which gracefully shuts the server down (it writes the current state to disk before exiting).

For other commands, the in-game tilde console (~ key) gives admin-authenticated players access to the engine's console-variable surface. Be aware that many community guides reference console variables that are version-specific or have moved between releases — when in doubt, prefer the Server Manager UI or configuration files for anything you can set there. The community wiki and ficsit.app are the most reliable places to look up the current set of working commands.

The LOW.MS panel also exposes its own Web Console entry in the sidebar, which gives you the same console surface from your browser without needing to be in-game. Useful when you need to issue a command quickly without launching Satisfactory.

Configuration files

For settings the in-game UI does not expose directly, you can edit configuration files through the LOW.MS panel. Use Configuration Files in the sidebar for the in-panel editor (the easiest way to edit Game.ini, Engine.ini, and the other common files), or File Manager if you need to browse the full file tree.

Important: LOW.MS ships some additional Game.ini tuning by default to head off the most common Satisfactory multiplayer performance issues. Unless you have a specific reason and know what you are doing, leave the tuned values alone.

Be aware that on Satisfactory 1.0+ the core server identity (server name, admin password, client password, autosave interval, rotating autosave count) is not stored in GameUserSettings.ini any more — it lives in a ServerSettings.<PORT>.sav state file written by the dedicated server, and the correct way to manage those values is through the in-game Server Manager UI.

Engine.ini is still a plain INI and is where you tune networking.

Accessing config files

1. From the LOW.MS panel, go to Service Management → Game Services and click Manage on your Satisfactory server.
2. Open Configuration Files in the sidebar (or File Manager for raw browsing).
3. INI files live in FactoryGame/Saved/Config/WindowsServer/. The ServerSettings.<PORT>.sav file lives in FactoryGame/Saved/SaveGames/, just above your world saves.

Engine.ini

Engine.ini controls network and tick rate settings. A safe block looks like this:

[/Script/OnlineSubsystemUtils.IpNetDriver]
NetServerMaxTickRate=30
LanServerMaxTickRate=30
InitialConnectTimeout=60.0
ConnectionTimeout=60.0

[/Script/SocketSubsystemEpic.EpicNetDriver]
NetServerMaxTickRate=30
LanServerMaxTickRate=30

[/Script/Engine.Engine]
NetClientTicksPerSecond=30

A few notes on these values:

• NetServerMaxTickRate=30 matches Satisfactory's 30 TPS simulation target. There is no benefit to pushing it higher than the simulation can produce.
• The 60-second timeouts are a conservative bump from the 30-second defaults and help players on slower connections finish first-time syncs without being dropped.

Important: Always stop the server before editing configuration files, then restart it after saving your changes. Editing files while the server is running may result in your changes being overwritten the next time the server saves.

For the full settings reference, see the server settings guide.

Player management

Kicking players

Use kicks for:

• Players causing temporary disruptions.
• Getting a player's attention (they can rejoin immediately).
• Freeing up a player slot temporarily.

To kick a player:

1. Open the Server Manager in-game and go to the Players tab.
2. Select the player and click Kick.
3. The player is disconnected immediately but can rejoin.

Dealing with disruptive players (no built-in ban)

As noted above, Satisfactory 1.0+ does not expose a ban command or persistent ban list in the in-game Server Manager. Kicking a player only disconnects them temporarily; there is currently no first-party way to prevent them from rejoining.

The practical workaround for dealing with a genuinely disruptive player is:

1. Kick them from the Players tab.
2. Set (or change) the Player Password through the Server Manager's Server Settings tab, and share the new password only with the people you want on the server.
3. If the disruptive player already had admin access, change the Admin Password as well so they can no longer authenticate as admin.

This is not as clean as a real ban list, but it is the currently documented way to keep unwanted players out until Coffee Stain ships a proper kick/ban feature.

Server restarts and scheduling

Manual restarts

You can restart your server in several ways:

1. LOW.MS panel — on the service overview, click STOP then START. This is the most reliable method and works whether or not you are in-game.
2. In-game Server Manager — use the Console tab's quit command to gracefully shut the server down (it writes state to disk before exiting), then start it again from the panel.
3. Web Console in the LOW.MS sidebar — run quit directly from your browser via the panel's web console feature.

When to restart

Regular restarts maintain server performance, especially for long-running sessions with large factories. Restart:

• After game updates — ensures the server picks up the latest version. The sidebar's Switch to/Update Latest Release (or Switch to/Update Latest Experimental, depending on your branch) is the right place to apply a new build.
• When performance degrades — if tick rate drops or players report lag, a restart can clear accumulated memory usage.
• After configuration changes — changes to .ini files require a restart to take effect.
• On a daily schedule — see below.

Scheduled restarts (LOW.MS panel)

The in-game Server Manager does not include a built-in scheduled-restart feature. Schedule daily (or twice-daily) restarts from Scheduled Tasks in the LOW.MS panel sidebar. A typical setup is a single daily restart scheduled for whatever hour your group is least likely to be online — most groups pick the early hours of the morning.

The downtime is typically under a minute, and the difference in stability afterwards is noticeable. For very large factories on long uptimes, twice a day is even better.

Monitoring performance

LOW.MS panel monitoring

The service overview page shows live meters for Players, CPU, Memory, and Bandwidth, plus an Auto Refresh toggle so you can leave it open and watch values move. For historical trends rather than the current second, the Current Activity & Stats entry in the sidebar gives you charts over time.

You also have:

• Log Viewer — read the full server log with scrollback. Useful for spotting errors after a crash or examining mod boot output.
• Web Console — same console surface as in-game, from the browser.

Performance indicators to watch

• Server tick rate — a healthy Satisfactory server should hold close to 30 ticks per second. If TPS drops noticeably, the server is struggling with the current factory load.
• RAM consumption above 80% — if your server consistently uses more than 80% of allocated RAM, you are close to crashing during the next autosave. Optimise or upgrade.
• Save file size — large saves indicate a complex factory that may benefit from the optimisations in the performance tuning guide.

What to do when performance drops

1. Restart the server — clears accumulated memory and can restore tick rate.
2. Check Network Quality — ensure it is set to Ultra on the server. A low Network Quality setting often manifests as what looks like a performance issue.
3. Review factory design — extremely long conveyor runs, lots of trucks doing pathfinding, and large numbers of idle powered machines all consume simulation cycles. The performance tuning guide has the full list.

Backups and recovery

Automated backups

LOW.MS automatically backs up your server on a regular schedule. Backups include your save files and server configuration, so you can recover from accidental data loss or corruption. Manual backups can also be triggered from Cloud Backup in the panel sidebar at any time.

Manual saves

In addition to the rotating autosaves, trigger a manual save before:

• Making major factory changes or demolitions.
• Editing server configuration files.
• Allowing new or untrusted players to join.
• Installing or removing mods.

Use the Save Game button in the in-game Server Manager.

Restoring a backup

If something goes wrong — a corrupted save, accidental destruction, or a bad configuration change — restore from a backup through Cloud Restore in the LOW.MS panel sidebar, or use Backup Manager to browse and download existing backups. For more on managing saves directly, the published upload/download save guide covers the workflow.

Resetting admin access

On Satisfactory 1.0+, the admin password, server name, and client password are stored in a ServerSettings.<PORT>.sav file (where <PORT> is the server's game port — e.g. ServerSettings.7777.sav) that sits in FactoryGame/Saved/SaveGames/ next to your world saves. There is no plain-text password anywhere in the INI files, so resetting a lost admin password is done by deleting this settings file and reclaiming the server.

1. Open File Manager in the LOW.MS panel sidebar.
2. Navigate to FactoryGame/Saved/SaveGames/.
3. Delete the ServerSettings.<PORT>.sav file that matches your server's port.
4. Restart the server from the panel.
5. The next time you connect via the Server Manager, the server will appear unclaimed. Claim it again and set a new admin password.

Deleting this file also resets the server name, player password, auto-load session name, and server certificate. Your save files are not affected — the .sav world files in the same folder are left alone. If you want to be extra safe, take a manual backup through Cloud Backup in the sidebar before deleting anything.

Related guides

• Getting started with your Satisfactory server on LOW.MS — first-time setup walkthrough.
• Server settings guide — detailed configuration options.
• Performance tuning — optimise tick rate, RAM, and factory performance.
• Multiplayer setup and connection guide — multiplayer and networking guide.
• Common issues and fixes — troubleshooting guide.
• Setting up mods on a Satisfactory dedicated server — mod installation guide.