✦ Craft & Quest

Home / Satisfactory / Guide

Satisfactory 1.0 · Dedicated Servers & Netcode

Satisfactory 1.0 Dedicated Server Guide: Tick Rate, Desync & INI Optimization

On this page
  1. Satisfactory 1.0 Dedicated Server Architecture
  2. The 60 Hz Tick Rate Upgrade: ServerSettings.ini & Engine.ini
  3. Bandwidth & Packet Desync Tuning: Eliminating Belt Stutter
  4. Port Forwarding & Firewall Protocol Matrix
  5. Linux File Permissions & Cross-Platform Save Migration
  6. Automated Save Backups, Memory Leak Mitigation & Cron Services
  7. Troubleshooting & Multiplayer Latency FAQ
  8. Satisfactory tools

Satisfactory 1.0 completely revamps dedicated server stability with native crossplay, in-game Server Manager controls, and optimized netcode. However, default configuration files cap server tick rates at 30 Hz and restrict client bandwidth to 15 KB/s, causing conveyor belt item stuttering, vehicle desync, and hyper tube ejection errors in factories exceeding 50,000 entities. Upgrading Engine.ini and ServerSettings.ini with ServerTickRate=60, TotalNetBandwidth=104857600 (100 MB/s), and MaxClientRate=10485760 restores true 780 and 1,200 items/minute belt saturation across multiplayer sessions.

Version boundary: Verified for Satisfactory 1.0.0.6+ (Full Release). Production recipes, MAM Alien Technology research trees, fluid dynamics, power scaling formulas, and dedicated server parameters reflect current stable game code.

Satisfactory 1.0 Dedicated Server Architecture

Satisfactory 1.0 transitions the game to Unreal Engine 5.3, overhauling the underlying multiplayer networking architecture. The dedicated server binary operates as a headless console application that runs the complete game simulation independently of any graphical client. In Satisfactory 1.0, Coffee Stain Studios implemented native crossplay between Steam and Epic Games, introduced an integrated Server Manager UI accessible directly from the main menu, and unified world save management under an authenticated API.

Hosting a stable dedicated server for mid-to-late-game factories requires understanding the computational demands of Massage-2(AB)b. The server calculates tick rates, physics collisions, conveyor belt item arrays, pipe fluid hydraulic networks, train signals, and creature AI simultaneously. Review the baseline and recommended hardware specifications before deploying a server instance:

Server Hardware Component Early Game (Phase 1–2, <10k Entities) Mid Game (Phase 3, 10k–50k Entities) Late Game Mega-Factory (Phase 4–5, 50k+ Entities)
Processor (CPU) 2 Cores @ 3.0 GHz 4 Cores @ 3.8 GHz+ 6+ Cores @ 4.5 GHz+ (High Single-Thread Score)
Memory (RAM) 8 GB DDR4 16 GB DDR4/DDR5 32 GB DDR4/DDR5 (High Bandwidth)
Storage Drive Standard SATA SSD NVMe SSD (PCIe Gen 3) NVMe SSD (PCIe Gen 4/5, >3,500 MB/s Read)
Network Uplink 25 Mbps Up / Down 100 Mbps Up / Down 1 Gbps Symmetrical Fiber (Low Jitter)
Operating System Windows Server 2022 / Ubuntu 22.04 LTS Ubuntu 22.04 LTS / Debian 12 Ubuntu 24.04 LTS / Arch Linux (Optimized Kernel)

Single-threaded CPU performance represents the absolute performance ceiling for Satisfactory servers. Unreal Engine 5 executes the core factory tick loop on a primary game thread; while audio, save serialization, and network replication run asynchronously across worker threads, a single CPU core with weak IPC will bottleneck the entire simulation once entity counts surpass 50,000 buildings.

In-game Server Manager interface showing tick rate configurations, pause on empty toggles, and player management
Server Manager UI: inspect the Server Settings tab to configure tick rate, auto-pause behavior, and admin privileges. · Tested on Satisfactory 1.0+ (Full Release) · Craft & Quest Automation Workshop.

The 60 Hz Tick Rate Upgrade: ServerSettings.ini & Engine.ini

By default, Satisfactory dedicated servers ship with a conservative target tick rate of 30 Hz (30 ticks per second). While 30 Hz conserves CPU cycles on budget virtual private servers (VPS), it causes noticeable physics degradation in multiplayer games. At 30 ticks per second, high-speed vehicles clip through terrain, pioneer animations appear jittery to other players, and fast-moving items on conveyor belts suffer from positional interpolation stutter.

Upgrading your server simulation to a locked 60 Hz tick rate doubles the fidelity of physics calculations, eliminates client jitter, and smooths out train block signal arbitration. To configure a 60 Hz tick rate, shut down your dedicated server instance and modify the server configuration files according to your operating system:

Open Engine.ini in a text editor (such as Notepad or nano). Scroll to the bottom of the file and append the following configuration block:

[/Script/OnlineSubsystemUtils.IpNetDriver]
NetServerMaxTickRate=60
LanServerMaxTickRate=60

[/Script/Engine.Engine]
NetClientTicksPerSecond=60
SmoothedFrameRateRange=(LowerBound=(Type="ERangeBoundTypes::Inclusive",Value=30.000000),UpperBound=(Type="ERangeBoundTypes::Inclusive",Value=60.000000))

Next, open ServerSettings.ini located in the same directory. Ensure the auto-pause setting is configured properly to prevent the simulation from running unattended when all players disconnect:

[/Script/FactoryGame.FGServerSubsystem]
mAutoPause=True
mAutoSaveOnDisconnect=True

Setting mAutoPause=True freezes the simulation when zero players are online, preventing power plants from burning through stored fuel or AWESOME sinks from processing infinite items while your team sleeps. When the first player reconnects, the simulation immediately resumes within 1.5 seconds.

High-speed Mk.5 conveyor belt manifold with splitters running at 780 items per minute without item micro-stutter
Throughput verification: inspect saturated Mk.5 belts entering splitters to detect packet-loss desync stalls. · Tested on Satisfactory 1.0+ (Full Release) · Craft & Quest Automation Workshop.

Bandwidth & Packet Desync Tuning: Eliminating Belt Stutter

The most pervasive technical complaint in Satisfactory multiplayer involves conveyor belt throughput desynchronization. On large multiplayer servers, players frequently observe Mk.5 Conveyor Belts (rated at 780 items/min) or Mk.6 Belts (rated at 1,200 items/min) experiencing micro-pauses where items freeze for a fraction of a second before lurching forward. This intermittent freezing reduces effective belt throughput by 3% to 8%, starving downstream Manufacturers and causing production efficiencies to fluctuate between 92% and 97%.

This throughput loss is not an engine simulation bug; it is an artifact of network bandwidth throttling. Default Unreal Engine network drivers cap per-client bandwidth at 15,000 bytes per second (roughly 15 KB/s). When multiple players view complex mega-factories containing thousands of moving conveyor items, the server saturates the 15 KB/s bandwidth cap immediately, dropping item replication packets and forcing client prediction rollbacks.

To eliminate bandwidth bottlenecks, open Engine.ini on your dedicated server and insert the following unthrottled networking parameters:

[/Script/Engine.Player]
ConfiguredInternetSpeed=104857600
ConfiguredLanSpeed=104857600

[/Script/OnlineSubsystemUtils.IpNetDriver]
MaxClientRate=10485760
MaxInternetClientRate=10485760
TotalNetBandwidth=104857600
NetServerMaxTickRate=60

[/Script/SocketSubsystemEpic.EpicNetDriver]
MaxClientRate=10485760
MaxInternetClientRate=10485760
TotalNetBandwidth=104857600

These values uncap client bandwidth from 15 KB/s up to 10 MB/s (80 Mbps) per connected player, allowing the server to transmit the exact coordinate and inventory state of every conveyor item in real-time. Connecting players must also configure their client network settings: in the game pause menu, navigate to Options → Gameplay → Network Quality and set the slider to Ultra. This matches the client netcode to the server's unthrottled parameters, restoring saturated 780 and 1,200 items/min belt flow.

Configuration editor window editing Engine.ini with ServerTickRate and TotalNetBandwidth parameters
Engine configuration file: verify ServerTickRate=60 and TotalNetBandwidth parameters in Engine.ini for high-capacity multiplayer. · Tested on Satisfactory 1.0+ (Full Release) · Craft & Quest Automation Workshop.

Port Forwarding & Firewall Protocol Matrix

Satisfactory 1.0 dedicated servers communicate across three separate network ports. To allow external players to discover, authenticate, and connect to your self-hosted server, you must forward these ports through your home router or cloud provider firewall (such as AWS Security Groups, Google Cloud VPC Firewall, or Oracle Cloud Ingress Rules).

Network Port Protocol Network Service Function Firewall Action Required
7777 UDP Primary Game Simulation Traffic (Player movement, factory updates, voice chat). Forward to Server Local IP (Inbound & Outbound)
15000 UDP Beacon / Query Port (Server ping response, player count query, Steam server list). Forward to Server Local IP (Inbound & Outbound)
15777 UDP Server Management API (In-game Server Manager authentication, save loading, console). Forward to Server Local IP (Inbound & Outbound)

Ensure that all forwarded ports use the UDP protocol. Forwarding TCP 7777 will not work; Unreal Engine's replication driver operates strictly over stateless UDP. On Linux servers running ufw (Uncomplicated Firewall), execute the following commands to permit traffic:

sudo ufw allow 7777/udp comment 'Satisfactory Game Port'
sudo ufw allow 15000/udp comment 'Satisfactory Beacon Port'
sudo ufw allow 15777/udp comment 'Satisfactory Server API'
sudo ufw reload
Operating system file manager displaying FactoryGame Saved SaveGames directory and automated backup zip files
Save directory structure: locate your .sav world files in FactoryGame/Saved/SaveGames/server for scheduled automated backups. · Tested on Satisfactory 1.0+ (Full Release) · Craft & Quest Automation Workshop.

Linux File Permissions & Cross-Platform Save Migration

Transferring save files between local Windows machines and dedicated Linux servers requires strict attention to POSIX file ownership and case-sensitive path handling. On Linux distributions, Unreal Engine 5 enforces case sensitivity: naming a file MyWorld.sav and attempting to load myworld.sav will cause the server to fail to find the save, launching a blank new session instead.

Follow these exact administrative commands to stage and permissions-lock migrated saves on Linux:

  1. Locate Source Save: On your local gaming PC, press Win + R, enter %LOCALAPPDATA%FactoryGameSavedSaveGames, and identify the active world file (e.g., Apex_Foundations.sav).
  2. Transfer via Secure Copy (SCP): Open PowerShell or terminal and transfer the file to the dedicated server using SCP:
    scp Apex_Foundations.sav steam@your-server-ip:~/.config/Epic/FactoryGame/Saved/SaveGames/server/
  3. Enforce Ownership and Read/Write Permissions: Because the server daemon runs under the unprivileged steam user, root-transferred files will trigger permission denied errors during auto-saves. Log into the Linux server and execute:
    sudo chown -R steam:steam ~/.config/Epic/FactoryGame/Saved/SaveGames/
    sudo chmod 644 ~/.config/Epic/FactoryGame/Saved/SaveGames/server/*.sav
  4. Set Active Save in Server Manager: Launch Satisfactory on your client machine, open Server Manager → Manage Saves → Load Save, select Apex_Foundations.sav, and click Load Game. The server will restart the simulation with your imported factory world.
Network Directive in Engine.ini Default Value Optimized 1.0 Value Network Performance Benefit
NetServerMaxTickRate 30 60 Doubles physics simulation rate, eliminating vehicle clipping and belt stutter.
LanServerMaxTickRate 35 60 Locks local network replication to match dedicated server tick frequency.
MaxClientRate 15000 10485760 Uncaps client bandwidth from 15 KB/s to 10 MB/s, preventing packet loss.
TotalNetBandwidth 32000 104857600 Provides up to 100 MB/s aggregate bandwidth pool for multi-engineer sessions.
ConnectionTimeout 30.0 120.0 Extends handshake window, allowing slow clients to load heavy 100+ MB saves.
InitialConnectTimeout 60.0 180.0 Prevents connection drops during initial world state serialization.

Automated Save Backups, Memory Leak Mitigation & Cron Services

As factories expand into Phase 4 and Phase 5, Satisfactory world save files (.sav) swell from 5 MB up to 120 MB. A server crash or power outage during an auto-save cycle can corrupt the active world file. Implementing an automated backup script paired with scheduled service restarts safeguards hundreds of hours of team construction.

On Linux servers, deploy a systemd service file to manage the dedicated server daemon. Create the service file at /etc/systemd/system/satisfactory.service:

[Unit]
Description=Satisfactory Dedicated Server
After=network.target

[Service]
Type=simple
User=steam
WorkingDirectory=/home/steam/satisfactory
ExecStart=/home/steam/satisfactory/FactoryServer.sh -multihome=0.0.0.0 -ServerQueryPort=15777 -BeaconPort=15000 -Port=7777 -unattended
Restart=on-failure
RestartSec=10
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target

To mitigate the gradual RAM creep observed during continuous 72-hour server sessions (where Unreal Engine 5 garbage collection retains lingering asset references in memory), configure a daily cron job to execute an automated rolling restart and offsite backup. Open the crontab editor with crontab -e and add the following scheduled task:

# Daily automated backup and restart at 04:00 AM server time
0 4 * * * /bin/bash /home/steam/backup_and_restart.sh >> /home/steam/server_maintenance.log 2>&1

The companion maintenance script (backup_and_restart.sh) archives the world save directory into a compressed tarball with a date stamp, rotates backups older than 14 days, and restarts the systemd service:

#!/bin/bash
SAVE_DIR="/home/steam/.config/Epic/FactoryGame/Saved/SaveGames/server"
BACKUP_DIR="/home/steam/backups/satisfactory"
DATE=$(date +"%Y%m%d_%H%M%S")

mkdir -p "$BACKUP_DIR"
# Create compressed archive of world saves
tar -czf "$BACKUP_DIR/satisfactory_save_$DATE.tar.gz" -C "$SAVE_DIR" .
# Purge backups older than 14 days
find "$BACKUP_DIR" -type f -name "*.tar.gz" -mtime +14 -delete
# Gracefully restart server service
sudo systemctl restart satisfactory.service
echo "[$(date)] Automated backup and service restart completed successfully."

Troubleshooting & Multiplayer Latency FAQ

Why do players encounter the error "UNetConnection::Tick: Connection TIMED OUT" during connection?

This timeout occurs when a connecting client takes longer than the default 30-second handshake window to download the world save file. Large mega-factory saves exceeding 60 MB saturate slow client connections, causing the server to assume the client disconnected. To fix this, increase the connection timeout in Engine.ini on the server: add ConnectionTimeout=120.0 and InitialConnectTimeout=180.0 under the [/Script/OnlineSubsystemUtils.IpNetDriver] block, giving clients up to 3 minutes to load heavy world saves.

How do I resolve the "Server is Paused" bug where players cannot move upon joining an empty server?

If mAutoPause=True is active in ServerSettings.ini, the server freezes physics when empty. Occasionally, when a player joins, the un-pause trigger fails to fire, leaving the player suspended in mid-air. To un-pause the game, the server administrator can open the in-game Server Manager (Server Manager → Server Settings) and toggle the Pause Game switch off manually. Alternatively, setting mAutoPause=False in ServerSettings.ini permanently prevents the server from pausing, though this causes machines to consume fuel continuously when no players are present.

What causes hyper tubes to catapult multiplayer clients out of bounds while the host travels smoothly?

Hyper tube ejection glitches occur when client-side character movement prediction falls out of sync with the server's physics tick rate. If the dedicated server runs at 30 Hz while the client renders at 144 FPS, high-velocity tube junctions desynchronize, clipping the player through tube walls. Upgrading the server to NetServerMaxTickRate=60 in Engine.ini and configuring client Network Quality to Ultra resolves this issue. Additionally, avoid stacking more than 10 Hyper Tube Entrances consecutively on dedicated servers.

How can I migrate a single-player save (.sav) to a dedicated server without losing player inventory or research?

Single-player world saves are stored locally at %LOCALAPPDATA%FactoryGameSavedSaveGames{SteamID}. Copy the desired .sav file to the server's save directory (~/.config/Epic/FactoryGame/Saved/SaveGames/server/ on Linux). In Satisfactory 1.0, player character inventories are linked directly to player online platform IDs (Steam ID or Epic Account ID). When joining the dedicated server, log in using the exact same Steam/Epic account used to create the single-player world. The server will recognize your account ID and restore your character inventory, equipped equipment, and hotbars automatically.

Why does dedicated server RAM climb continuously from 6 GB to 28 GB after 48 hours of continuous uptime?

This gradual memory accumulation is caused by Unreal Engine 5 actor garbage collection cycles retaining transient object references (such as vehicle tire collision traces and dropped foliage physics bodies). While not an acute memory leak, it gradually fragments memory pools. Setting up the automated daily restart cron job detailed in the maintenance section above (running at 04:00 AM) clears memory fragments daily, keeping RAM usage stabilized between 6 GB and 10 GB indefinitely without manual administrator intervention.

Plan it. Try it. Make it yours.

Satisfactory tools

All game tools
Satisfactory 1.0 Rocket Fuel Blenders and Fuel-Powered Generators

Satisfactory / Factory & power ratios

Production Line & Rocket Fuel Planner

Size 1.0 Rocket Fuel generator arrays, 19/24 Compacted Coal loops, and zero-screw Heavy Modular Frame factories.

  • 4.1667 m³/min generator ratio
  • 19/24 Compacted Coal loop
  • Belt & pipeline tier checks
Satisfactory 1.0 · Rocket Fuel & Heavy Modular Frames
Open tool