Installing and Starting a Windrose Dedicated Server
Deploy a Windrose dedicated server on a Pterodactyl panel using SteamCMD and the official egg.
Overview
Windrose dedicated servers run on Windows binaries executed through Wine on Linux hosts. The server is distributed via Steam and installed automatically by the Pterodactyl egg using SteamCMD. The server supports a maximum of 8 players.
Prerequisites
- A Pterodactyl or WISP panel with a node that has at least 8 GB RAM and 32 GB SSD storage
- The official Windrose egg imported from
https://eggs.pterodactyl.io/egg/games-windrose - SteamCMD access (handled automatically by the egg)
Importing the Egg
- In your panel, navigate to Admin > Nests and create a new nest called
Windrose(or use an existing games nest). - Click Import Egg and paste the URL
https://eggs.pterodactyl.io/egg/games-windrose, or download the JSON and upload it directly. - Save the egg before creating any servers.
Creating the Server
- Navigate to Admin > Servers > Create New.
- Select the Windrose egg.
- Set RAM to at least
8192 MBfor a 2-player server. For larger player counts, allocate16384 MBor more. - Set disk space to at least
32768 MB. - Configure the startup variables (see below).
Startup Variables
The egg exposes the following variables:
| Variable | Description | Notes |
|---|---|---|
SERVER_NAME |
Public server name | Max 40 characters |
MAX_PLAYERS |
Player slot limit | Max 8 |
SERVER_PASSWORD |
Join password | Max 30 characters |
SERVER_PASSWORD_PROTECTED |
Enable password gate | true or false |
USE_DIRECT_CONNECTION |
Direct IP vs invite code mode | true enables direct IP |
AUTO_UPDATE |
Auto-update on restart | true or false |
Set SERVER_NAME, MAX_PLAYERS, and your preferred connection mode before first start.
First Start and Installation
Start the server from the panel console. SteamCMD will download the Windrose dedicated server files using AppID 4129620. This is the dedicated server AppID — it is different from the client AppID (3041230). The download is typically 10–20 GB depending on build size.
Once installation completes, the server launches via:
wine /home/container/R5/Binaries/Win64/WindroseServer-Win64-Shipping.exe -log
Watch the console for the line indicating the server is ready to accept connections. Logs are also written to:
R5/Saved/Logs/R5.log
Verifying the Server is Running
After startup, confirm the server is listed in the in-game server browser or connect via invite code or direct IP depending on your USE_DIRECT_CONNECTION setting. Check R5.log if the server does not appear — look for Error, Warning, or Fatal lines near the end of the file.
Post-Install Configuration
After confirming the server starts successfully, stop it and edit ServerDescription.json in the root container directory to finalize your configuration. Do not edit this file while the server is running — the file is rewritten on graceful shutdown and any changes made while it is live will be overwritten.