Windrose guide

Windrose Dedicated Server Guide: Install, Invite Code and Direct IP

By the ChicagoServers team · Updated · 7 min read

A Windrose dedicated server is a free Steam tool, Windrose Dedicated Server (app ID 4129620), that runs a world without anyone having the game open. Players normally join with an invite code through Play, then Connect to Server. If you switch on direct connection, they can use an IP and port instead.

Windrose has been in early access since April 14, 2026, so the server tooling is still moving. This guide was checked against the developers' official dedicated server guide (last updated 18 May 2026, game version 0.10.0.5.120) and the Steam listing. Where a detail is likely to change we say so, and anything we could not confirm is left out.

Quick answer
  • Install Windrose Dedicated Server from the Tools section of your Steam library, or with SteamCMD (app_update 4129620 validate). The official guide covers Windows; it also publishes a Docker image.
  • Run StartServerForeground.bat. The invite code is printed in the console and stored as InviteCode in R5\ServerDescription.json.
  • Players join with Play, then Connect to Server, then the invite code. The code is case-sensitive.
  • Direct IP only works if UseDirectConnection is true. Invite-code play (the default) uses NAT punch-through instead of a fixed port.
  • Client and server versions must match, so update the server after every game patch, and only edit config files while the server is stopped.
On this page
  1. What the Windrose dedicated server actually is
  2. How to install the Windrose dedicated server
  3. How to start the server and find your invite code
  4. How players join: invite code or direct IP
  5. Hardware requirements from the official FAQ
  6. Windrose server not connecting: what to check
  7. Skipping the home-hosting setup
  8. Frequently asked questions
  9. References

What the Windrose dedicated server actually is

The dedicated server is a separate download from the game. On Steam it is listed as a free Tool, not a game, and it has its own app ID (4129620; the game itself is 3041230). It keeps a world running on a machine of your choice so your crew can log in at any time, instead of everyone depending on one player's PC being online.

The Steam store page describes Windrose as playable solo offline or in co-op, with up to 8 players and both self-hosted and dedicated servers available. The developers recommend parties of up to 4 for the best experience, especially in the late game. The server's own cap is the MaxPlayerCount setting in its config file.

How to install the Windrose dedicated server

There are three supported routes in the official guide. Pick the one that matches where you bought the game and how you plan to run the server.

  1. Steam (simplest)

    Open your Steam library, set the filter to Tools, and install Windrose Dedicated Server. Right-click it, choose Manage, then Browse Local Files to open the folder.

  2. SteamCMD (for a VPS or dedicated box)

    Set an install directory, log in anonymously, and pull app 4129620. Re-run the same app_update line whenever the game updates.

    force_install_dir C:\WindroseServer
    login anonymous
    app_update 4129620 validate
    quit
  3. Epic Games Store or Stove

    Copy the server folder from your in-game files (the guide points to R5\Builds) to a location outside the game folder.

  4. Docker (optional)

    The guide documents the image windroseserver/windroseserver:latest, with port 7777 mapped for both TCP and UDP and your Saved folder and ServerDescription.json mounted into the container. In that setup UseDirectConnection is set to true.

How to start the server and find your invite code

Two launchers ship in the server folder. StartServerForeground.bat is the recommended one because it opens a console window that shows the logs; closing the window stops the server. WindroseServer.exe runs as a background process, and you stop it from Task Manager.

On first launch the server creates its default config files. The official guide suggests starting it once, stopping it, and then editing. When it is running you can read the invite code two ways:

  • In the console output printed at startup.
  • In R5\ServerDescription.json, in the InviteCode field.

The invite code is letters and digits only, at least 6 characters, and case-sensitive. A wrong capital letter is enough to make the lookup fail, so copy it rather than retyping.

How players join: invite code or direct IP

Windrose has two connection modes, selected by one key in ServerDescription.json.

ModeSettingWhat players doNetworking
Invite code (default)UseDirectConnection: falsePlay, Connect to Server, enter the codeICE peer-to-peer with NAT punch-through. The guide says ports are assigned dynamically and recommends a router with UPnP.
Direct IPUseDirectConnection: trueConnect with the server's IP and port, such as 192.168.1.100:7777Uses DirectConnectionServerPort (7777 in the example). Open the port for both TCP and UDP.

For a LAN game you only need the machine's local IP (run ipconfig to find it) and the port. Over the internet, the host needs a public IP and must forward the chosen port, TCP and UDP, to the server machine. If direct IP will not connect, the guide suggests trying a different port, for example 17777 or 27890, and keeping it below 65000.

If you are on the Docker setup and testing from the same machine, the guide says to connect to 127.0.0.1:7777.

Hardware requirements from the official FAQ

The developers list requirements by player count. They are written for the dedicated server running on its own machine.

PlayersCPURAMStorage
2Intel Xeon Scalable (Sapphire Rapids), 2 cores at 3.2 GHz8 GB35 GB SSD
4Same12 GB35 GB SSD
10Same16 GB35 GB SSD

If you host from the same PC you play on, the guide says the game client wants at least 16 GB of RAM and the server needs roughly 8 GB on top (24 GB total is recommended), with an SSD strongly advised. That requirement is the main practical reason people move to a dedicated machine once a group grows.

Windrose server not connecting: what to check

Work through these in order. They come from the official guide's warnings and troubleshooting notes.

  1. Match versions. Update the server with the same Steam or SteamCMD route you used to install it, and make sure the client is on the same build.
  2. Wait for full startup. Do not try to connect until the server has fully started.
  3. Check the code. It is case-sensitive. Copy it from ServerDescription.json rather than retyping it.
  4. Allow the executable. Add a firewall or antivirus exception for WindroseServer.exe if it fails to start or crashes on launch.
  5. Rule out VPNs and proxies. Temporarily disable them; the guide lists them as a cause of failed connections.
  6. For direct IP, confirm UseDirectConnection is true, the port is open for TCP and UDP, and the server was restarted after you changed the file.

Skipping the home-hosting setup

Everything above assumes you are running the server on a PC you manage, including router and firewall rules. Hosting with ChicagoServers? The Windrose server hosting page lists what is included, such as free server backups and SFTP file access.

Frequently asked questions

Does a Windrose dedicated server use an IP address or an invite code?

By default players join with an invite code under Play, then Connect to Server. If you set UseDirectConnection to true in ServerDescription.json, players can connect with an IP and port instead, and that port must be open for TCP and UDP.

Where do I find the Windrose invite code?

It is printed in the server console at startup and stored as the InviteCode field in R5\ServerDescription.json. It is case-sensitive, letters and digits only, and at least 6 characters.

Can I run a Windrose dedicated server on Linux?

The official guide covers Windows and says Linux and headless setups are not currently supported, though it also documents a Docker image. This is early access software, so check the current guide before relying on either point.

Why can my friends not join after a Windrose update?

The server and client versions must match. Update the dedicated server through Steam or SteamCMD (app 4129620) and restart it so it runs the same build as the players.

References