Dedicated server setup: hosting, ports, and multiplayer configuration

Prerequisites

Before setting up a dedicated server, check that you meet these requirements:

• A Windows or Linux machine that can remain powered on continuously. The server does not require a graphics card, but a modern CPU and at least 4 GB of RAM are expected for stable operation with 4–6 players.
• A Steam account that owns a copy of Abiotic Factor. The dedicated server files are free, but the game license is needed to connect.
• Basic familiarity with your router’s administration interface for port forwarding.
• For self-hosting on Linux, comfort with the command line and tools like screen or tmux.

Choosing Between Self-Hosted and Rented Server

You have two main routes for running a dedicated server. The table below outlines the tradeoffs to help you decide.

If you have a machine that stays on anyway and you are comfortable with command-line tools, self-hosting gives you full control at no extra cost. If you prefer to avoid networking setup or lack a suitable machine, a rented server is the simpler option.

Self-Hosted Setup Workflow

1. Install SteamCMD and Download the Server Tools

SteamCMD is Valve’s command-line tool for downloading dedicated server files. It does not require a Steam login for public server downloads.

On Windows:

• Download SteamCMD from Valve’s official site and extract it to a folder such as C:\steamcmd.
• Open Command Prompt as administrator and run:

cd C:\steamcmd
steamcmd +login anonymous +force_install_dir C:\abiotic_server +app_update 2946260 validate +quit

On Linux (Ubuntu/Debian):

• Install SteamCMD via your package manager:

sudo apt update && sudo apt install steamcmd

• Then run:

steamcmd +login anonymous +force_install_dir ~/abiotic_server +app_update 2946260 validate +quit

The app ID 2946260 points to the Abiotic Factor dedicated server tools. Using the wrong ID will download the game client instead, which will not function as a server.

2. Configure Server Settings

After the download completes, navigate to the server installation directory. The configuration file Game.ini must be placed in the correct subfolder:

• Windows: AbioticFactor/Saved/Config/WindowsServer/Game.ini
• Linux: AbioticFactor/Saved/Config/LinuxServer/Game.ini

Create the file with the following minimal content:

[/Script/Engine.GameSession]
MaxPlayers=8

[/Script/DeepField.AbioticFactorGameMode]
ServerName=My GATE Facility
ServerPassword=
AdminPassword=changeme123

Key settings to adjust:

• ServerName – appears in the server browser.
• ServerPassword – leave blank for a public server. Set a password to restrict access.
• AdminPassword – required to use in-game admin commands. Without this, you cannot manage the server after launch.
• MaxPlayers – lower values (4–6) reduce CPU load on weaker hardware. Higher values (8+) require a stronger processor.

3. Forward Ports on Your Router

Abiotic Factor’s dedicated server listens on three UDP ports by default. You must forward these from your router to the local IP address of the server machine.

Steps to forward ports:

1. Find the server machine’s local IP address. On Windows, run ipconfig and look for the IPv4 address. On Linux, run ip a.
2. Log into your router’s admin panel (commonly at 192.168.1.1 or 192.168.0.1).
3. Locate the port forwarding section (sometimes called “Virtual Server” or “Port Forwarding”).
4. Create three separate rules, each forwarding one UDP port to the server’s local IP.
5. Save the settings and restart the router if prompted.

Recovery advice: If external port check tools (such as canyouseeme.org) report port 7777 as closed, verify that the server machine has a static local IP. A dynamic IP that changes after a reboot will break the forwarding rules. Set a static IP in your router’s DHCP reservation settings.

4. Launch the Server

On Windows: Run AbioticFactorServer.exe from the installation folder.

On Linux: Run ./AbioticFactorServer.sh from the installation folder. To keep the server running after you close the terminal, use screen:

screen -S abiotic
./AbioticFactorServer.sh
# Press Ctrl+A, then D to detach the session

To reattach later, run screen -r abiotic.

5. Connect and Verify

In the game client, open the console with the ~ key and type:

open YOUR_PUBLIC_IP:7777

Replace YOUR_PUBLIC_IP with your external IP address (find it by searching “what is my IP” in a web browser). Alternatively, friends can find the server in Steam’s server browser (View → Servers) under the Abiotic Factor tab if port 27015 is correctly forwarded.

Common Failure Points and Recovery

Server runs locally but no one can connect from outside. Check that Windows Defender Firewall (or your Linux firewall) allows inbound UDP traffic on ports 7777, 7778, and 27015. On Windows, add inbound rules for these ports in “Windows Defender Firewall with Advanced Security.”

The server appears in the browser but connections time out. Verify that your router is not using Carrier-Grade NAT (CGNAT), which prevents inbound connections. If your router’s WAN IP differs from the IP shown by “what is my IP,” contact your ISP to request a public IP or switch to a rented server.

Admin commands do not work. This means AdminPassword was not set in Game.ini before launch. The server must be stopped, the file corrected, and the server restarted. There is no way to set the admin password while the server is running.

Save file loss after a crash or power outage. Server saves are stored in AbioticFactor/Saved/SaveGames/. Schedule regular backups of this folder. On Linux, a cron job that copies the folder to a separate drive or cloud storage once per day is a practical safeguard.

The server stops when you close the terminal on Linux. Use screen or tmux to run the server in a detached session, as shown in step 4. Without this, the server process receives a hangup signal and terminates.