How to Host an Icarus Dedicated Server: Complete Setup Guide

Why Host a Dedicated Icarus Server

Icarus was designed around session-based missions called Prospects, where players drop onto a planet, complete objectives, and extract before a timer runs out. A dedicated server removes the dependency on any single player hosting the session. The server stays online 24/7, so team members can log in at different times, contribute to objectives, and build persistent bases in Open World mode without needing the host to be present.

Since the Great Hunts DLC and Dangerous Horizons expansion added extensive endgame content, having a reliable always-on server has become increasingly important for groups tackling multi-session campaigns and boss encounters.

Hardware Requirements

Icarus runs on Unreal Engine 4, which makes it resource-intensive on both client and server. The dedicated server needs substantial resources, especially for the larger maps and higher player counts.

Component	Minimum (4 players)	Recommended (8 players)
CPU	Quad-core 3.0 GHz	Quad-core 3.5 GHz+
RAM	8 GB	16 GB
Storage	15 GB SSD	30 GB NVMe SSD
Network	10 Mbps upload	25 Mbps+ upload
OS	Windows Server 64-bit	Windows Server 64-bit

Icarus’s UE4 engine is memory-hungry. The game uses Wine on Linux, which adds overhead. For stability, 16 GB of RAM is strongly recommended even for smaller groups.

Installation via SteamCMD

RocketWerkz distributes the Icarus dedicated server through SteamCMD with App ID 2089300.

Step 1: Install SteamCMD

Download SteamCMD from Valve’s developer site and extract it to a working directory.

Step 2: Download the Server Files

Run SteamCMD with the following commands:

login anonymous
force_install_dir C:\IcarusServer
app_update 2089300 validate
quit

Step 3: Configure and Launch

The server executable and configuration files will be in your install directory. RocketWerkz maintains a detailed setup guide on their official GitHub repository covering launch parameters and configuration options.

Server Configuration

Icarus server configuration is handled through JSON files and launch parameters.

Key Launch Parameters

• -SteamServerName: The name displayed in the server browser
• -PORT: The game port (default 17777)
• -QueryPort: The Steam query port (default 27015)
• -MaxPlayers: Maximum concurrent players per session

Session Management

Icarus uses a Prospect-based system. Key concepts for server admins:

• Prospects: Timed missions where players drop in, complete objectives, and extract. If the timer expires, characters lose any items not extracted.
• Open World: Persistent sessions without timers, ideal for base building and long-term progression
• Outposts: Player-owned spaces for managing inventory between Prospects

On a dedicated server, multiple Prospects and Open World sessions can be available simultaneously. Players select which session to join from the server lobby.

Persistence and Saves

Server saves are stored locally and can be backed up manually or through automated scripts. Regular backups are essential because Icarus Prospects have real consequences. If a session corrupts or a server crashes during a critical moment, a recent backup can save hours of progress.

Corrupted Prospect files are a known issue. If players experience loading failures, check the Saved/PlayerData/DedicatedServer/Prospects/ directory for corrupt JSON files and remove them.

Port Configuration

Icarus requires specific ports to be open for players to connect:

Port	Protocol	Purpose
17777	UDP	Game traffic
27015	UDP	Steam query

Ensure these ports are forwarded through your router or firewall. On cloud hosting, add them as inbound rules to your security group.

Performance Considerations

Memory Management

Icarus’s UE4 engine consumes significant RAM, especially on larger maps like Elysium (from Dangerous Horizons). Monitor memory usage and plan for 16 GB minimum for a stable experience with 4-8 players.

CPU Utilization

The game’s physics, AI, and terrain generation are CPU-bound. A strong single-thread performance matters more than core count. Prioritize clock speed over additional cores when choosing hardware.

Restart Schedule

Unlike some survival games, Icarus does not require frequent restarts for stability. However, after extended uptime (24+ hours), a restart can clear accumulated memory and improve performance. Schedule restarts during low-activity periods to minimize disruption.

Updates

Icarus receives regular weekly or bi-weekly patches. Keep your server updated to match the client version, as version mismatches prevent players from connecting. Automated update scripts using SteamCMD can handle this:

app_update 2089300 validate

Run this before each server start to ensure you are on the latest version.

Linux Hosting

The Icarus dedicated server is built for Windows. Running it on Linux requires Wine or a containerized setup with Docker. While this works, it adds complexity and a performance overhead. For production servers, Windows hosting or a managed provider that handles the Wine layer is recommended.

Self-Hosted vs. Managed Hosting

Self-Hosted

Maximum control over every aspect of the server, but you handle all maintenance, updates, backups, and troubleshooting. Requires Windows Server or a working Wine setup on Linux.

Managed Hosting

A hosting provider handles infrastructure, automated updates, backup scheduling, and monitoring. You configure game settings and manage your community.

At Reactor, our Icarus hosting is built to handle the game’s demanding UE4 engine with dedicated resources, automatic updates, and scheduled backups. Servers deploy in minutes with full configuration access.

Launch your Icarus server on Reactor and give your group a persistent home on Icarus.