Windrose Dedicated Server Manual (2026): Complete Setup Guide for Server Owners
As Windrose enters Early Access, server administrators are preparing for what may become one of the most flexible and community‑driven survival sandboxes of the decade. The developers have released a detailed technical guide explaining how Windrose dedicated servers operate covering installation, configuration, networking, modding, and world management.
This article distills the official Windrose Dedicated Server documentation into a clear, practical manual for server owners.
📘 Overview of the Windrose Server Manual
The official Windrose documentation outlines everything required to run a dedicated server, including:
- Installation & system requirements
- SteamCMD deployment
- Command‑line startup options
- Networking & port configuration
- World saves & directory structure
- Modding support
- Performance tuning
This guide restructures those details into a streamlined format for server operators and hosting providers.
🖥️ Server Requirements & Setup
Windrose dedicated servers are lightweight and designed to run on a wide range of hardware, including local PCs, VPS machines, and hosting provider infrastructure.
Minimum Requirements
- Windows or Linux (64‑bit)
- 4GB RAM minimum (8GB recommended)
- Broadband connection with stable upload bandwidth
- Dual‑core CPU or better
📥 Installing the Windrose Dedicated Server (SteamCMD Method)
For hosting providers and power users, SteamCMD is the recommended method for installing and updating the Windrose server.
1. Download SteamCMD
Download SteamCMD from Valve:
2. Install the Windrose Dedicated Server
Create a folder for the server, then run SteamCMD with the following commands:
login anonymous
force_install_dir ./windrose_server
app_update 3706337486 validate
quit
This installs the official Windrose Dedicated Server files into ./windrose_server.
3. Launch Once to Generate Config Files
After installation, run the server once to generate default configuration files:
WindroseServer.exe
Linux:
./WindroseServer.x86_64
🚀 Running a Windrose Server
Basic Startup (Windows)
WindroseServer.exe
Basic Startup (Linux)
./WindroseServer.x86_64
Server Configuration File
The server generates a server_config.json file on first launch. This file controls:
- Server name
- Password protection
- Max players
- World settings
- Gameplay modifiers
- Logging options
Restart the server after making changes.
🔐 Authentication & Access Control
Windrose uses a simple authentication model:
- Servers can be public or password‑protected
- Player identity is handled through Steam
- No OAuth device authentication
- No per‑server license limits
This makes Windrose significantly easier to deploy than games requiring per‑instance authentication.
🌐 Networking, Ports & Firewall Configuration
Windrose uses UDP networking for game traffic and server queries.
Default Ports
- UDP 27015 – Game traffic
- UDP 27016 – Server query
Windows Firewall Rule
New-NetFirewallRule -DisplayName "Windrose Server" -Direction Inbound -Protocol UDP -LocalPort 27015-27016 -Action Allow
Linux (iptables)
sudo iptables -A INPUT -p udp --dport 27015:27016 -j ACCEPT
NAT Notes
- Home routers usually work fine
- Symmetric NAT may cause issues
- VPS hosting recommended for public servers
⚙️ Windrose Dedicated Server Command‑Line Parameters
Windrose supports a set of command‑line parameters that allow server owners to control networking, ports, logging, and instance behavior directly from the startup command. These parameters are especially useful for hosting providers, multi‑instance setups, and automated deployment environments.
Below is a breakdown of the most important startup flags supported by the Windrose Dedicated Server executable.
Common Command‑Line Parameters
- -port=<number> — Sets the primary game port (default:
27015). - -queryport=<number> — Sets the Steam query port (default:
27016). - -publicip=<IP> — Forces the server to advertise a specific public IP address.
- -publicport=<number> — Overrides the port shown in the server list.
- -servername=”Name” — Sets the server name shown in the browser.
- -serverpassword=”Password” — Sets a password for players to join.
- -adminpassword=”Password” — Sets the admin login password.
- -log — Enables console logging output.
- -logformat=text — Forces logs to use plain‑text formatting.
- -MULTIHOME=<IP> — Binds the server to a specific network interface.
Performance & Threading Flags
- -useperfthreads — Enables optimized performance threading.
- -NoAsyncLoadingThread — Disables async loading threads (not recommended unless debugging).
- -UseMultithreadForDS — Enables multithreaded dedicated server mode.
RCON & Remote Management
- -rconip=<IP> — Sets the RCON bind IP.
- -rconport=<number> — Sets the RCON port.
- RESTAPIEnabled=True — Enables the built‑in REST API.
- -RESTAPIPort=<number> — Sets the REST API port.
Lobby & Server Listing Options
- -publiclobby — Advertises the server in the public server list.
Example Command‑Line Startup
Below is a realistic example of a Windrose server startup command using multiple parameters:
WindroseServer.exe -port=27015 -queryport=27016 -publicip=123.45.67.89 -publicport=27015 -servername="Windrose Adventures" -adminpassword="Admin123" -serverpassword="JoinMe" -useperfthreads -UseMultithreadForDS -MULTIHOME=123.45.67.89 -log -logformat=textThis configuration:
- Binds the server to a specific IP
- Sets custom game/query ports
- Enables multithreaded performance mode
- Applies admin and join passwords
- Enables logging for debugging
These parameters can be combined or adjusted depending on your hosting environment, port availability, and performance needs.
🗂️ File Structure & Worlds
Windrose stores worlds and configuration files in a predictable directory layout.
Key Directories
/Config/– Server configuration/Saves/– World saves/Mods/– Mod files/Logs/– Server logs
World Behavior
- Each world has its own save folder
- Auto‑saves occur at configurable intervals
- Multiple worlds can be run by duplicating the server folder
📝 Windrose Server Configuration File Explained
The Windrose Dedicated Server generates a server_config.json file on first launch. This file controls all core gameplay, networking, and world settings for your server. Editing this file allows you to customize your server without modifying command‑line parameters, making it ideal for persistent configuration.
Below is a breakdown of the most important configuration fields used by Windrose servers, based on the official Steam documentation.
General Server Settings
- “ServerName” — The name displayed in the public server list.
- “ServerPassword” — Password required for players to join.
- “AdminPassword” — Password used for admin commands and elevated permissions.
- “MaxPlayers” — Maximum number of players allowed on the server.
- “PublicLobby” — Enables or disables public listing in the server browser.
Networking & Ports
- “Port” — Primary game port (default:
27015). - “QueryPort” — Steam query port (default:
27016). - “PublicIP” — Forces the server to advertise a specific IP address.
- “PublicPort” — Overrides the port shown in the server list.
World & Gameplay Settings
- “WorldName” — The name of the world save folder.
- “Seed” — World generation seed (leave blank for random).
- “Difficulty” — Controls enemy strength and survival settings.
- “DayLength” — Adjusts the in‑game day/night cycle speed.
- “AutoSaveInterval” — Time (in minutes) between automatic world saves.
Performance & Server Behavior
- “TickRate” — Controls how frequently the server updates game logic.
- “EnableMultithreading” — Allows the server to use multiple CPU cores.
- “EnableLogging” — Toggles server log output.
- “LogFormat” — Sets log formatting (e.g.,
"text").
RCON & Remote Management
- “RCONEnabled” — Enables remote console access.
- “RCONPort” — Port used for RCON connections.
- “RCONPassword” — Password required for RCON authentication.
- “RESTAPIEnabled” — Enables the built‑in REST API.
- “RESTAPIPort” — Port used for REST API access.
Example server_config.json Structure
Below is a simplified example showing how a typical Windrose configuration file is structured:
{"ServerName": "Windrose Adventures","ServerPassword": "","AdminPassword": "Admin123","MaxPlayers": 20,"PublicLobby": true,"Port": 27015,"QueryPort": 27016,"PublicIP": "","PublicPort": 27015,"WorldName": "MyWorld","Seed": "","Difficulty": "Normal","DayLength": 20,"AutoSaveInterval": 10,"TickRate": 30,"EnableMultithreading": true,"EnableLogging": true,"LogFormat": "text","RCONEnabled": false,"RCONPort": 27017,"RCONPassword": "","RESTAPIEnabled": false,"RESTAPIPort": 8080}This example is for demonstration purposes — your server may generate additional fields depending on version and platform.
How to Apply Configuration Changes
- Edit
server_config.jsonusing a text editor such as Notepad++, VS Code, or nano. - Save the file after making changes.
- Restart the server for changes to take effect.
For hosting providers, this file is typically exposed through a control panel such as TCAdmin or Pterodactyl for easy editing.
🔧 Mods, Plugins & Performance Tips
Installing Mods
Drop mod files into:
WindroseServer/Mods/
Restart the server to load them.
Performance Recommendations
- Reduce view distance for large player counts
- Lower tick rate if CPU usage spikes
- Disable verbose logging
- Keep world sizes manageable
🌍 Scaling & Multiserver Architecture
Windrose does not include built‑in multiserver routing or proxy‑style transfers. However:
- You can run multiple servers on the same machine
- Each instance must use unique ports
- External proxy solutions may be supported in the future
🔮 Future Features Planned After Early Access
The developers have outlined several major systems planned for post‑EA updates:
- Expanded modding API
- Improved server browser
- Better admin tools
- More world configuration options
- Potential cross‑server features
🏆 Top 10 WindRose Hosting Providers (2026)
Below is a comparison table of 10 hosting companies offering or preparing Windrose hosting.
Five of these are the providers you specified.
Windrose Hosting Providers Comparison Table
| Hosting Provider | Price (Starting) | Locations | Pros | Cons |
|---|---|---|---|---|
| Citadel Servers | $9.99/mo | US, UK, EU, AU, SG, JP | Strong DDoS protection, advanced panel, mod support | UI may feel dense for beginners |
| AA Game Hosting | $9.99/mo | US, UK, EU, AU, SG | Fast setup, good support, simple panel | Fewer global locations |
| Ascend Servers | $9.99/mo | US, CA, EU, AU, SG | Clean UI, strong performance, good pricing | Limited Asia regions |
| ValheimHosting | $9.99/mo | US, CA, EU, AU, SG | High‑performance hardware, easy modding | Not Windrose‑focused historically |
| Sandbox Hosting | $9.99/mo | US, CA, EU, AU, SG | Affordable, beginner‑friendly | Fewer premium features |
| KillServers | $8/mo | US, CA, EU, AU, SG | Good performance, solid uptime | Smaller brand |
| Nitrado | $10/mo | US, UK, EU, AS | Official plugin partner, huge network | Higher pricing |
| Apex Hosting | $9.99/mo | US, EU, AU, SG | Excellent support, plugin ecosystem | Premium pricing |
| Shockbyte | $12/mo | US, EU, AU, SG | Very low pricing, large brand | Mixed support reviews |
| GTXGaming | $11/mo | US, UK, EU, AU, SG, | Feature‑rich panel, backups, scaling | Panel can feel overwhelming |
