中文
Back Server setup guides
Windrose server hosting8 min

Windrose Dedicated Server Setup and Persistent Ocean Warships Guide

Deploy the official Windrose Dedicated Server (AppID 4129620): UDP/TCP 7777 forwarding, ServerDescription.json tuning, and automated LGSM operations.

Windrose combines open-sea exploration, cooperative sail handling, warship physics, and island fortress battles. Its official Dedicated Server architecture simulates ocean currents, storms, and docked fleets continuously, independently of player clients. This article covers deployment standards and network tuning for the latest version's dedicated server.

1. Server hardware baseline

Configuration Minimum requirement Recommended production configuration
CPU architecture 4 cores / above 3.0 GHz 8 cores / high clock speed of 3.6 GHz+ (for fluid dynamics across multiple warships)
Physical RAM 8 GB physical RAM 16 GB+ physical RAM (allowing for ocean chunks and complex harbor buildings)
Disk space 20 GB reserved space Fast NVMe SSD (frequent fleet data writes)
Network bandwidth 15 Mbps upload 30 Mbps+ upload (frequent naval artillery trajectories and network synchronization)

2. Deploy with SteamCMD

The official Windrose Dedicated Server tool supports anonymous SteamCMD downloads:

  • Server AppID: 4129620
  • Executable: WindroseServer.exe
Shell
# Download/update the Windrose dedicated server anonymously
steamcmd +login anonymous +app_update 4129620 validate +quit

On first run, WindroseServer.exe initializes identity and world files in R5/.

3. Network port planning

Windrose coordinates two transport protocols:

Port Transport protocol Purpose Firewall and forwarding requirements
7777 UDP Frequent warship physics, heading, wind, and naval combat synchronization Core port; allow it in the firewall and forward on the router
7777 TCP Connection handshake, session creation, and lobby status Forwarding required for initial client handshakes

Allow both protocols in Windows PowerShell:

PowerShell
New-NetFirewallRule -DisplayName "Windrose Server UDP" -Direction Inbound -LocalPort 7777 -Protocol UDP -Action Allow
New-NetFirewallRule -DisplayName "Windrose Server TCP" -Direction Inbound -LocalPort 7777 -Protocol TCP -Action Allow

4. Main configuration: ServerDescription.json

The file is located at R5/ServerDescription.json:

JSON
{
  "ServerName": "Windrose LanGame Armada",
  "ServerPassword": "",
  "MaxPlayers": 16,
  "Port": 7777,
  "SaveIntervalMinutes": 10,
  "EnablePVP": true,
  "WorldSeed": ""
}
  • SaveIntervalMinutes: 10~15 minutes recommended to save fleet supplies and docking state frequently.
  • EnablePVP: Set to false for friends exploring together to create a purely cooperative sailing world.

5. Open-source LGSM management

We recommend the official open-source LanGame Server Manager (LGSM) (repository: GitHub - SZSLGJCOM/LanGame-Server-Manager).

  1. One-click download and startup: LGSM's built-in Windrose preset downloads and initializes R5 worlds and settings automatically.
  2. Port conflict prevention: Detects occupancy of 7777 and redirects smoothly.
  3. Automatic fleet snapshots: Backs up R5/Saves to protect against save damage from sinking warships or unexpected power loss.

6. Remote multiplayer and network optimization

  • Public internet: After forwarding UDP/TCP 7777 on the router, crew members enter public IP:7777 in the game lobby to board.
  • Networking without a public IP: For rented accommodation or campus networks, use LINK in LanGame OS Orbit to establish an encrypted P2P tunnel. Enter the virtual adapter IP to enjoy zero-latency naval battles!