Dedicated Server Setup: Hosting, Ports, and Multiplayer Configuration

The Problem

You've died to a Leyak for the third time because your friend who was supposed to watch your back lagged out. Or worse—you built an entire base in Cascade Labs only to realize your host's save file corrupted when they went to bed. Abiotic Factor's peer-to-peer hosting works for short sessions, but if you're planning a multi-week run through the GATE Facility, you need a dedicated server.

Dedicated servers keep your world running 24/7, fix the "host goes to sleep" problem, and eliminate the host advantage in PvP if you're running Order vs. Scientist shenanigans. This guide covers everything from your first download to port forwarding.

The Solution

Option 1: Self-Hosted (Free, Requires Technical Know-How)

You'll need a Windows or Linux machine that can stay on 24/7. The server is lightweight—a Raspberry Pi 4 running Ubuntu can handle a 4-player world, but you'll want at least 4GB RAM and a modern CPU for 6+ players.

What you need:

• SteamCMD installed (free from Valve)
• The Abiotic Factor dedicated server tools (also free)
• Ports forwarded on your router
• A copy of the game on your Steam account (the server doesn't need a license, but you do)

Option 2: Game Server Hosting (Paid, Zero Configuration)

Services like GTXGaming, Survival Servers, and Citadel Servers offer one-click Abiotic Factor deployment. Expect to pay $10-15/month for 8-12 player slots. This is the "I just want to play" option.

Step-by-Step: Self-Hosted Setup

1. Install SteamCMD and the Server

Windows:

1. Download SteamCMD from Valve's official site
2. Extract to C:\steamcmd
3. Open Command Prompt as Administrator
4. Run:

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

Linux (Ubuntu/Debian):

sudo apt update && sudo apt install steamcmd
steamcmd +login anonymous +force_install_dir ~/abiotic_server +app_update 2946260 validate +quit

2. Configure the Server

Navigate to your server folder. You'll find AbioticFactor/Binaries/Win64/ on Windows or AbioticFactor/Binaries/Linux/ on Linux.

Create a file called Game.ini in: AbioticFactor/Saved/Config/WindowsServer/ (Windows) AbioticFactor/Saved/Config/LinuxServer/ (Linux)

Minimal working configuration:

[/Script/Engine.GameSession]
MaxPlayers=8

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

Important settings:

• ServerPassword — leave blank for public, set for private
• AdminPassword — required for in-game admin commands
• MaxPlayers — 4 is stable on low-end hardware, 8+ needs good CPU

3. Port Forwarding

Abiotic Factor uses three ports by default:

Router steps:

1. Find your local IP: ipconfig (Windows) or ip a (Linux)
2. Log into your router (usually 192.168.1.1 or 192.168.0.1)
3. Find "Port Forwarding" or "Virtual Server"
4. Create three rules forwarding UDP 7777, 7778, and 27015 to your server's local IP
5. Save and reboot router

Test your ports: Use canyouseeme.org or yougetsignal.com. Enter port 7777—if it says "Success," you're good.

4. Launch the Server

Windows: Run AbioticFactorServer.exe from the install folder Linux: Run ./AbioticFactorServer.sh

For persistent operation (survives SSH logout on Linux):

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

5. Connect Your Friends

In-game, open console with ~ and type:

open YOUR_PUBLIC_IP:7777

Or have friends search in the Server Browser (Steam → View → Servers). Your server should appear under "Abiotic Factor" if port 27015 is forwarded correctly.

Common Mistakes

Mistake #1: Forgetting to allow the server through Windows Firewall The server will run locally but no one can connect. Add inbound rules for UDP ports 7777, 7778, and 27015 in Windows Defender Firewall.

Mistake #2: Using the wrong app ID The server app ID is 2946260, not the game's Steam ID. Double-check you're downloading the dedicated server tools, not the game client.

Mistake #3: Not setting an admin password Without AdminPassword in Game.ini, you can't use admin commands. You'll need to restart the server to add it later.

Mistake #4: Running the server on the same machine you play on You can, but expect lag. The server is CPU-intensive—if you're fighting a Phantom pressure wave while the server is calculating physics, everyone suffers. Use a separate machine or rent.

Mistake #5: Ignoring the save file location Server saves are in AbioticFactor/Saved/SaveGames/. Back these up weekly. I lost a 40-hour world to a power outage. Don't be me.

Mistake #6: Not updating the server after game patches After every Abiotic Factor update, re-run the SteamCMD command. Old servers won't show up in the browser and may crash on join.

Admin Commands (Once Connected)

Open console with ~ while on your server. Requires the admin password set in Game.ini.

Quick Checklist

• Installed SteamCMD and server files
• Created Game.ini with ServerName and AdminPassword
• Forwarded ports 7777, 7778, 27015 (UDP)
• Allowed server through firewall
• Tested connection with canyouseeme.org
• Backed up default save files
• Set up auto-restart script (optional but recommended)

Your server is now running. Go survive the GATE Facility with your friends, and remember: the Leyak doesn't care about your ping.