Manual-first Windows server guide
Abiotic Factor Dedicated Server Setup and Crossplay Guide
Create an Abiotic Factor Windows server with a named Cascade world, explicit UDP game/query ports, a protected admin password, and a platform mode that matches the players who actually need to discover it.
Abiotic Factor accepts up to 24 through its player argument but the developer guide warns against more than six. Its platform limiter is equally specific: PC means Steam, Xbox includes Windows Store, PlayStation stands alone, and omitting the limiter enables current crossplay. Only Steam local worlds have an official dedicated-server migration path.
Steam application
App ID 2857200
The developer-maintained quickstart supports anonymous SteamCMD installation.
Server operating system
Windows officially supported
The official quickstart calls Linux a community workaround, so this product does not advertise Linux support.
World identity
Cascade by default
Keep an imported folder named Cascade or select it explicitly with -WorldSaveName=.
Player count
1-24 accepted; more than 6 not recommended
The command-line range is not the same as a developer-backed capacity promise.
Native administration
Admin password, Admin.ini, and Player Management
No official RCON channel is documented in the reviewed server wiki.
Protect the server first: Use Force World Save, close the process normally, and copy the entire Saved/SaveGames/Server tree before changing WorldSaveName, sandbox files, platform mode, or server binaries.
Size the host before downloading
PC and capacity guidance
The publisher provides product-level Steam requirements, not a player-count capacity table for the dedicated process. The profiles above are conservative editorial starting points, and the official warning against more than six players remains controlling.
| Profile | Players | Memory | Processor | Storage |
|---|---|---|---|---|
| Developer-sized private group Conservative starting point | 1-6 players | 16 GB total host RAM starting point | Four modern CPU cores available to the server workload | SSD with room for the install, growing world, logs, and snapshots |
| Host and play or exceed six players Conservative starting point | Host plus client, or 7-24 experimental players | 32 GB total system RAM starting point | Modern high-clock desktop CPU; measure sustained server load | SSD with external backup retention |
First boot
Install the Windows server with an explicit identity
A short launch line is easier to audit than a copied collection of obsolete performance switches. Begin with the arguments the current developer wiki documents.
- 1
Install the official server
Use anonymous SteamCMD and a dedicated folder on an SSD.
steamcmd +login anonymous +force_install_dir D:\Servers\AbioticFactor +app_update 2857200 validate +quit - 2
Choose world, ports, and player ceiling
Start with Cascade, UDP 7777/27015, and no more than the developer-recommended six players.
- 3
Set platform and protected credentials
Omit -PlatformLimited for current all-platform crossplay, or choose exactly one documented group; set unique join and admin passwords.
Do not publish a command line containing the real passwords.
- 4
Prove persistence
Join, use Force World Save, close normally, restart, and confirm the same world before opening WAN access.
- The current developer guide no longer recommends historical async-loading workaround flags; do not cargo-cult them into the default command.
Crossplay
Match the platform limiter to the audience
A platform limiter changes which clients discover and join the server; it is not a performance preset.
- 1
Use no limiter for the shared crossplay server
This is the documented all-platform path for current Steam, Xbox/Windows Store, and PlayStation clients.
- 2
Use PC only for Steam
-PlatformLimited=PC excludes console and Windows Store group discovery.
- 3
Understand the Xbox grouping
-PlatformLimited=Xbox covers Xbox and Windows Store clients; PlayStation is a separate value.
Supported migration
Move a Steam local world into the dedicated server
The official migration path applies to Steam local/player-hosted worlds, not local saves from Xbox, PlayStation, or Windows Game Pass.
- 1
Copy the complete Steam world
After stopping the source session, copy its folder from %LocalAppData%/AbioticFactor/Saved/SaveGames/<SteamID>/Worlds.
- 2
Place it under the server Worlds directory
Restore into AbioticFactor/Saved/SaveGames/Server/Worlds without flattening the world folder.
- 3
Resolve the world name
Rename the imported folder to Cascade or preserve its name and pass the same -WorldSaveName value.
Stop if a fresh world opens; correct the path/name before the new state is saved repeatedly.
Keep every layer consistent
Ports, firewall, and router setup
Open only the services your Abiotic Factor server actually uses. The game process, Windows Firewall rule, router forward, and player join address must all agree on the same port and protocol.
| Port | Protocol | Purpose | Exposure | Notes |
|---|---|---|---|---|
| 7777 | UDP | Default player/game traffic selected with -PORT= | Internet playersRequired for this use | Match the launch argument, Windows Firewall, and router forwarding.[official-quickstart][official-launch] |
| 27015 | UDP | Default Steam query/listing traffic selected with -QueryPort= | Internet playersRequired for this use | A running process can still be undiscoverable when this path is blocked.[official-quickstart][official-launch] |
| 14001 | UDP | Local discovery when -LANOnly is active | LAN onlyOptional | Do not use -LANOnly for an Internet-listed server.[official-launch] |
Never expose an administration or RCON port merely so players can join. Keep remote administration private whenever possible, use a strong unique credential, and confirm the game's own security model before forwarding it.
Know what must survive a reinstall
Files, worlds, and configuration
| File or folder | Purpose | Backup | Notes |
|---|---|---|---|
| AbioticFactor/Saved/SaveGames/Server/Worlds/<world> | Selected dedicated world and player state | Critical | The default world folder is Cascade.[official-migration] |
| AbioticFactor/Saved/SaveGames/Server/Admin.ini | Native administrator identities | Critical | An alternate location can be selected with -AdminIniPath=; protect platform identifiers.[official-launch] |
| AbioticFactor/Saved/SaveGames/Server/Worlds/<world>/SandboxSettings.ini | Native per-world sandbox settings | Critical | An app can select another Saved-relative file with -SandboxIniPath=; inspect the real launch line.[sandbox-reference][official-launch] |
| AbioticFactor/Saved/Logs | Startup, configuration, save, and connection diagnosis | Recommended | Redact passwords, addresses, and platform identifiers before sharing.[official-quickstart] |
| Setting or file | Location | What it controls | Restart? |
|---|---|---|---|
-WorldSaveName=Cascade | Server launch arguments | Selects the world folder; Cascade is the native default[official-launch][official-migration] | Yes |
-MaxServerPlayers=6 | Server launch arguments | Sets the accepted player ceiling from 1 to 24[official-launch] | Yes |
-PlatformLimited=PC | Server launch arguments | Restricts discovery to PC, Playstation, or Xbox/Windows Store[official-launch] | Yes |
| -AdminPassword= | Protected server launch configuration | Lets supported users authenticate to Player Management[official-launch][official-quickstart] | Yes |
-SandboxIniPath=SaveGames/Server/Worlds/Cascade/SandboxSettings.ini | Server launch arguments; path relative to AbioticFactor/Saved | Selects a managed sandbox INI instead of the per-world default[official-launch][sandbox-reference] | Yes |
Avoid incompatible clients and unsafe shortcuts
Players, mods, and administration
Cross-play and editions
Omitting -PlatformLimited enables the current all-platform crossplay path; explicit PC, Playstation, and Xbox values intentionally split discovery groups.
- PC means Steam clients.
- Xbox includes Xbox and Windows Store clients.
- Playstation selects the PlayStation group.
- Use an admin password for console administration because SteamID-only lists cannot identify every platform.
Mods and extensions
The reviewed developer server wiki documents sandbox customization but does not establish a first-party Workshop-style dedicated-server mod deployment workflow.
- Treat SandboxSettings.ini and documented launch arguments as the supported customization surface.
- Do not promise automated Workshop synchronization without a current publisher source and release test.
- Back up the world before changing progression, loot, durability, time, or spawn behavior.
Administration
Use -AdminPassword, Admin.ini, and the in-game Player Management interface; the reviewed official wiki does not document RCON.
- Use Force World Save before planned maintenance.
- Protect Admin.ini and command lines that contain passwords.
- Do not invent or forward an RCON port for this game.
Preserve a return path before maintenance
Updates, backups, and rollback
Update without gambling the world
Update only after a normal close and complete Server-tree snapshot; Steam validation installs current official files but does not promise arbitrary historic rollback.
- 1
Capture runtime identity
Record Steam build, world name, sandbox path, launch arguments, ports, and platform mode.
- 2
Force-save and close
Use Player Management's Force World Save, close normally, and copy the complete Server tree.
- 3
Install the update
Validate App ID 2857200, then remove obsolete historical flags and verify the intended world before public joins.
steamcmd +login anonymous +app_update 2857200 validate +quit - 4
Restore only a compatible set
If rollback is required, use a publisher-exposed compatible branch plus the matching full world/config snapshot.
Back up and prove the restore path
The reliable recovery unit is Saved/SaveGames/Server plus the active sandbox/admin files and the launch arguments that select them.
- 1
Force-save and stop
Warn players, force the world save, close normally, and wait for the process to exit.
- 2
Copy the full Server data
Capture Worlds, Admin.ini, sandbox settings, and a redacted launch record in one dated snapshot.
- 3
Quarantine before restore
Preserve the current unexpected state, then restore one complete known-good snapshot while stopped.
- 4
Verify world identity
Start privately, confirm the expected world and players, force-save, restart, and test every advertised platform group.
Diagnose before reinstalling
Common Abiotic Factor server problems
A platform group cannot see the server
What players see
Steam sees the server but Xbox, Windows Store, or PlayStation users do not, or the reverse.
Likely cause
-PlatformLimited selects a different discovery group, or game/query UDP paths and builds do not match.
- 1.Preserve the launch line and identify whether a platform limiter is present.
- 2.Choose the documented audience mode, restart, and test UDP 7777/27015 from that platform.
A migrated Steam world starts as a fresh Cascade
What players see
The dedicated server loads a new world instead of the copied local world.
Likely cause
The folder is outside Server/Worlds or its name does not match -WorldSaveName.
- 1.Stop and quarantine the newly created world.
- 2.Restore the complete source folder and select its exact name or rename it to Cascade.
The management app cannot complete a clean remote stop
What players see
The world is online, but an automated save/stop action reports that no remote service is available.
Likely cause
Abiotic Factor documents in-game Force World Save but no official RCON/native remote shutdown channel.
- 1.Use Player Management to Force World Save and confirm completion.
- 2.Close the server normally and wait for exit before backup; do not repeatedly kill the process.
Every focused Abiotic Factor troubleshooting guide
Evidence stays visible
Sources and verification
Technical behavior changes with server builds. These are the references reviewed for this guide. Official documentation wins if a later patch changes a path, port, command, or compatibility rule.
[official-quickstart] DFJacob / Abiotic Factor Dedicated Server wiki
Abiotic Factor Dedicated Server wiki quickstart ↗Reviewed 2026-08-30 · Community or project reference
[official-launch] DFJacob / Abiotic Factor Dedicated Server wiki
Dedicated server launch parameters ↗Reviewed 2026-08-30 · Community or project reference
[official-migration] DFJacob / Abiotic Factor Dedicated Server wiki
Migrating saves to a dedicated server ↗Reviewed 2026-08-30 · Community or project reference
[sandbox-reference] Official Abiotic Factor Wiki
Abiotic Factor sandbox settings ↗Reviewed 2026-08-30 · Community or project reference
[steam-store] Deep Field Games / Steam
Abiotic Factor Steam requirements ↗Reviewed 2026-08-30 · Official documentation
Keep learning
Related guides
Fix crossplay discovery
Choose the correct platform limiter and test the game/query path without changing the world.
Open guide →
Reconnect an imported Steam world
Place the world under Server/Worlds and align Cascade or WorldSaveName safely.
Open guide →
Save and stop without RCON
Use Player Management's native save and a normal close while remote shutdown remains unavailable.
Open guide →