Satisfactory Control Center

← All guides · GAME GUIDE

---

Satisfactory uses its own in-game Server Manager for initial setup. Synix can install and launch the dedicated server, but you still need to claim it and complete that game-owned setup.

The optional local API connection adds monitoring and administration inside Synix. Normal Synix Start, Stop, and Restart controls do not require an API token.

1. Install and finish the game's setup

1. Create a Satisfactory entry in Synix and start it.
2. Wait for the dedicated server to finish loading.
3. Open Satisfactory's in-game Server Manager and add/select your server.
4. Claim the server, set its administrator password, and sign in as administrator.
5. Create or load the session you want to use.

Synix's template includes supported configuration files under FactoryGame\Saved\Config\WindowsServer. It manages the launch port and supported MaxPlayers value; it does not replace the game's claiming and session-creation process.

2. Connect with one button

1. Keep the server running with -NewConsole. Satisfactory templates introduced in v1.0.24 include this argument; check older or imported entries and restart through Synix if you add it.
2. Run Synix and the server with the same Windows permission level, preferably both as a normal user.
3. Select the server in Synix.
4. Open Server Options → Satisfactory Control Center → Connect API.
5. Choose Connect automatically once and wait for the result.

Synix sends server.GenerateAPIToken, reads the complete newly printed token from the selected server's output, verifies the local API connection, and saves the token encrypted for your Windows account.

Successful setup reports Token verified and saved securely and opens the Overview. There is no need to copy the console line into Notepad or paste a token manually.

A failed attempt keeps any previously saved connection. The command is not automatically retried.

What the tabs do

Tab	Available workflow
Connect API	Establish the optional local connection
Overview	Refresh session name, connected-player count/limit, game state, average tick rate, session play time, and technology tier
Server settings	Read the options exposed by this server, edit values, and apply changed settings
Saved games	List saves, save now, load a selected save, upload a save, or download a selected save
Advanced console	Send a supported individual server command with confirmation

Dashboard player counts refresh automatically while the connection is healthy. The Overview table refreshes on request. The API integration reports a player count, not a named-player roster.

A paused game session or a server waiting for a session is not the same as a stopped server process.

Server settings

Choose Refresh, edit supported values, then Apply changes. Read pending values after refreshing; some settings require a restart. Applying options does not automatically restart the server.

Technical setting keys and values remain in English as required by the game.

Saves

• Save now can use a supplied name or a dated Synix name. Reusing a name may overwrite an existing save.
• Load selected asks for confirmation and saves current progress first when a game session is active. Loading can disconnect players.
• Upload save may replace a same-named save but does not automatically load it.
• Download selected saves a copy to your chosen local path.

Keep a separate backup before replacing or loading important saves. The integration imposes a 512 MB save-transfer safety limit. The API may be temporarily unavailable while a session is loading.

Advanced console

Use game commands in their original English syntax. Scripts, token/password commands, and insecure-access changes are blocked in this view. Supported stop commands go through Synix's stop workflow rather than bypassing the watchdog.

Command output remains in that window; it is not posted to the dashboard or Synix text logs. The game itself can still produce its own logs.

Token security

The token grants administrator access, not just read-only monitoring.

• Synix verifies that the local API endpoint belongs to the selected running server and pins its certificate.
• Synix stores its saved token with Windows user-bound encryption, not in game configurations or launch arguments.
• Satisfactory prints tokens in its own console and logs. Keep those private and redact them from screenshots and support reports.
• Remove saved token removes Synix's saved connection; it does not revoke the token at the server.
• To revoke existing application tokens, use server.InvalidateAPITokens in Satisfactory's own server console/Server Manager console. This also affects other integrations using those tokens.

For a different Windows account or a moved installation, reconnect if Windows cannot unlock the stored token. Do not disable certificate checks to resolve a connection error.

This feature connects to the server on this PC using its configured game/API port. It does not require a new router forwarding rule for Synix and is not a hosted remote-control service. Players still need the game's appropriate network access.

Troubleshooting automatic connection

Message or symptom	What to check
Console unavailable	Server launched with -NewConsole; correct server selected; same Windows permission level
Unfinished command in the console	Clear the command input yourself; Synix will not overwrite it
Command runs but no token is captured	Server has finished loading; its log is writable; wait for a complete new output line
Console filters interfere	Clear include/exclude filters and allow the console to respond
Local API port belongs to another process	Correct the selected server's configured game port; do not send the token to an unrelated listener
Token rejected or saved token cannot be unlocked	Complete initial setup, then use Connect automatically again
API unavailable	Check the server log and allow startup or save loading to finish
Previous connection kept	The new attempt failed before saving; do not assume the old token was replaced

Capture uses fresh output after the command, not an arbitrary old token found in a log. A newly generated response can contain the same token value as an earlier response.

If connection fails, inspect the specific message before trying again. Never post the token line when requesting help.

Implementation reference: Satisfactory integration source.