If you want to play Windrose with friends without relying on one person to host every session, setting up a dedicated server at home is the best way to do it. A proper Windrose dedicated server setup keeps your world online separately from the game client, gives you more control over the server, and makes it easier for friends to join when everything is working correctly. The official Windrose server guide recommends using the separate dedicated server tool and starting it with StartServerForeground.bat so you can actually see the logs while setting it up.
The part that catches most people off guard is that Windrose home hosting is still a little rough around the edges. Right now, the most common issues are invite-code connection failures, same-network connection problems, firewall or VPN interference, and startup issues on unsupported systems. The official FAQ also says Direct IP support was added specifically because same-network and some self-hosted server setups were having trouble with the normal invite-code method.
What this guide is for #
This guide is for people who want to run a Windrose dedicated server setup from their own PC at home and may be completely new to game server hosting. That means the goal here is not to overcomplicate things. We are going to focus on the easiest supported path first, get the server running, make sure you can join it yourself, and only then worry about fixing connection problems for everyone else.
What you need before you start #
For beginners, the simplest and most reliable option right now is a Windows PC. The official Windrose dedicated server guide currently treats Windows as the supported path for the dedicated server tool, and recent reporting has also described the server as effectively Windows-focused right now. The official guide also recommends at least 24 GB of RAM if you plan to host and play on the same machine, and it strongly recommends SSD storage.
There is also a practical player-count warning that is easy to miss. Even though some hosts may advertise higher player counts, the official Windrose FAQ says the developers generally recommend groups of up to 4 players for the best experience right now. That is less about installation and more about keeping expectations realistic once your Windrose dedicated server setup is live.
Step 1: Install the Windrose Dedicated Server #
The easiest way to begin a Windrose dedicated server setup is through Steam.
Open Steam, switch your library filter to Tools, search for Windrose Dedicated Server, and install it. That is the official beginner path and the cleanest way to get the server files onto your PC. The official guide also says you can copy the dedicated server files from the game install, but if you do that, they need to be copied out of the main game folder before you run them.
For most people, the Steam Tools version is the better choice because it is simpler to update and less likely to cause folder confusion later.
Step 2: Start the server once before editing anything #
This is one of the most important beginner steps.
Before you start editing files, run the server once using:
StartServerForeground.bat
The official guide recommends this startup option because it opens a visible console window and shows live logs. That makes it much easier to spot problems while you are still learning. The first launch also creates the config files the server needs, so if you skip this step and go looking for the JSON files right away, you may not find them yet.
If you later want the server to run quietly in the background, you can use WindroseServer.exe, but for first setup, stick with the foreground launcher.
Step 3: Find your invite code and test that the server actually works #
Once the server finishes loading, look in the console window for an invite code. The official guide says this is the normal way players join a Windrose dedicated server. If the code scrolls by too quickly, you can also find it inside the R5 folder in:
ServerDescription.json
Then, in Windrose itself, go to Play → Connect to Server and paste the invite code in. Your friends would use the same code the same way.
This is the first real checkpoint in your Windrose dedicated server setup. Before you invite anyone else, make sure you can connect to the server successfully. If you cannot join your own server, there is no point troubleshooting your friends’ connections yet.
Step 4: Understand the two files that matter most #
Windrose keeps its server settings in two main JSON files. The official guide and current server references both point to these:
ServerDescription.jsonWorldDescription.json
Here is the easy way to think about them:
ServerDescription.json #
This is the main server settings file. It controls things like:
- your server name
- whether the server uses a password
- the invite code
- player count
- region and connection settings
This is the file you will usually edit first in a basic Windrose dedicated server setup.
WorldDescription.json #
This file controls settings for the specific world itself, such as the world name, preset, and related world values. Think of this as the file that describes the island or save you are actually playing on.
For beginners, the main takeaway is simple: server file = server settings, world file = world settings.
Step 5: Keep your first configuration simple #
A lot of new server owners get into trouble because they try to customize everything at once. For your first Windrose dedicated server setup, keep it simple.
Start by editing only the basics in ServerDescription.json:
- set a clear server name
- choose whether you want a password
- keep the player count low
- leave advanced network settings alone unless something is broken
That approach makes troubleshooting much easier because if something stops working, you will know which change probably caused it.
Step 6: Know the difference between invite-code joining and Direct IP #
This is where a lot of home-hosting confusion starts.
By default, Windrose is built around the invite-code system. That is the normal and easiest way to join if everything is working. The official dedicated server guide says the server uses NAT punch-through and recommends making sure your router supports UPnP. It also suggests disabling VPNs or proxies if connections fail.
But the official FAQ and recent patch notes also say that Windrose had known problems with same-network connections and certain self-hosted setups, which is why Direct IP support was added. If you are trying to connect from another PC on the same home network and invite codes are not working, Direct IP is the official fallback. The catch is that Direct IP may require router configuration and manual networking work.
For beginners, the easiest rule is:
- try the invite code first
- if that fails, especially on the same network, test Direct IP next
The biggest problems people are having with home hosting #
If you want this guide to actually help “noobs,” this part matters as much as the setup steps.
1. “My invite code doesn’t work” #
This is one of the biggest current issues. The official FAQ says some players cannot find or join servers by invite code, and the developers have also said some ISPs may be interfering with backend connectivity. They specifically mention checking whether traffic related to windrose.support is blocked and trying a different region if needed.
2. “I can join my server, but my friend can’t” #
This usually points to a network or ISP issue, not a bad server name. Current troubleshooting sources and community reports show this is very common with home-hosted Windrose servers. In plain English, your server may be running fine, but outside players still cannot reach it correctly.
3. “Two PCs on the same network can’t connect” #
This is a known issue right now. The official FAQ explicitly says Windrose has had same-network connection problems with invite codes and recommends Direct IP as the workaround.
4. “The server won’t start” #
If your server crashes immediately or the window closes, the official guide recommends the usual checks: verify files, update drivers, update Windows, and add firewall or antivirus exceptions for WindroseServer.exe. There is also at least one confirmed case where a low-end Intel Celeron system failed because the server required AVX support, which is the kind of hardware issue many beginners would never think to check.
5. “Where are the admin commands?” #
Right now, there really are not many. Recent reporting notes that Windrose currently lacks the usual mature admin tools people expect, such as proper player booting, forced saves, and cleaner live server controls. That means a lot of server management is still done through files instead of easy in-game commands.
A beginner-friendly way to troubleshoot #
If your Windrose dedicated server setup is not working, do not try ten random fixes at once. Use this order instead:
- Make sure the server starts with
StartServerForeground.bat - Confirm the invite code appears
- Try joining the server yourself first
- Disable VPNs or proxies temporarily
- Check Windows Firewall and antivirus exceptions
- Restart Steam, your PC, and your router
- If invite code fails on the same network, test Direct IP
- If outside players still cannot join, consider ISP or routing issues
That order matches the current official and community troubleshooting pattern much better than guessing.
Backups matter more than you think #
Windrose saves and backups are worth taking seriously right away. The official FAQ includes restore guidance from the dedicated server backup location and warns that save problems have happened, especially when Steam Cloud sync gets involved across multiple machines. The developers currently recommend disabling Cloud Saves while playing.
That means even on a small home server, one of the smartest things you can do is regularly back up your save folder before making big changes or updates.
The best way to approach your first Windrose server #
If you are brand new to home hosting, the goal should not be to build the perfect server on day one. The goal should be to get a basic Windrose dedicated server setup working with as few moving parts as possible.
That means:
- use the Steam Tools server
- launch it in the foreground
- change only the basic settings first
- test joining yourself
- then invite one friend
- only move on to advanced networking if the simple method fails
That approach is slower, but it saves a huge amount of frustration.
When home hosting stops being worth it #
A home-hosted Windrose server can be great for testing, casual sessions, and small groups. But if you find yourself fighting connectivity issues, same-network bugs, ISP problems, or constant restarts, that is usually the point where hosted infrastructure starts making more sense.
For a lot of players, the best use of home hosting is learning how the server works first. Once you outgrow that, moving to proper hosting becomes much easier because you already understand the basics.
