Running into problems with your Windrose server? Since the Early Access launch, a handful of issues keep coming up, and most of them are simple to fix once you know where to look. Start with the sections below.
The tutorial requirement (most common issue)
This is by far the most frequent cause of connection problems.
Windrose requires every player to complete the singleplayer tutorial before joining multiplayer. If they haven't, the game doesn't show a clear error: it may fail to connect or send them back to the menu.
To fix it, have the player:
- Launch Windrose in singleplayer.
- Complete the full tutorial (about 15 to 30 minutes).
- Exit and connect to your server again.
Connection issues
If the tutorial isn't the problem, check the following.
Server still starting
Your server must fully start before players can join. After starting or restarting, give it a minute or two to load its world. You can watch it load on the Console tab of your server in the control panel.
If your invite code shows as unavailable, the server likely hasn't finished its first start.
Invite code problems
Players join with your server's invite code: Play, then Connect to Server, and enter the code exactly. Codes are case-sensitive, and characters like O and 0 or l and 1 are easy to mix up, so copy and paste it.
You'll find the current code on the Configs tab (Server description, Current invite code), by clicking Install next to Show the join code on the Updates tab, or in the server's output on the Console tab. See How do I connect to my Windrose Server?.
Version mismatch
The server and all players must be on the same Windrose version. If they aren't, connections fail without much explanation. To fix it:
- Click Update now on the Steam update bar at the top of your server's page. To also check every game file, click Validate.
- Have players update their game.
- Start the server once the update is done, if it isn't running.
Network or DNS issues
If a player can connect on one network but not another, DNS or routing may be the issue. The player can try:
- Switching to Google DNS (8.8.8.8 and 8.8.4.4).
- Turning off VPNs or proxies for a while.
- Making sure Windows Firewall allows Windrose.
Configuration file issues
Windrose uses two main configuration files:
ServerDescription.json: the server's settings. It's on the Configs tab (Server description). The server name, password, region and invite code are set on the Startup tab, which writes them to this file for you.WorldDescription.json: the world's settings, in the world's folder on the Files tab. Windrose's own guide applies changes to this file with a tool that comes with the server, so if your world setting changes don't take effect, open a ticket and we'll help.
Editing while the server is running
Windrose can rewrite its configuration files while it runs and when it stops, so changes made while it's running can be lost. Always:
- Stop the server.
- Make your changes.
- Save the files.
- Start the server again.
Preset switching to Custom
If you change individual world settings, the world preset switches to Custom (also called Captain's Choice). This is intended. To keep a preset, don't edit individual settings.
WorldIslandId mismatch
The WorldIslandId in ServerDescription.json must match the IslandId in WorldDescription.json (which is also the world's folder name). If they don't match, the world won't load. Check both carefully, or restore a backup from the Backups tab.
Performance notes
Windrose is still in Early Access, so performance can vary, especially with larger groups.
- Around four players tends to be the most stable.
- Larger groups may see lag or slowdowns.
- ChicagoServers plans include enough memory, so performance issues are usually down to the game itself.
Keeping groups smaller is the best option until the game gets further optimization.
Save and world loading problems
If your server starts but the world doesn't load, check the Console tab for errors. Common causes:
- A WorldIslandId mismatch.
- Save data damaged by a crash: restore a backup from the Backups tab.
- Invalid JSON in a configuration file: use an online JSON validator to find missing commas or brackets.
Moving a world from your PC? See Transfer a Local Save to a Windrose Dedicated Server.
No console commands (yet)
Windrose has no admin console commands in Early Access. You manage the server with:
- The Startup and Configs tabs in the control panel.
- Start, Stop and Restart at the top of your server's page.
General troubleshooting checklist
- Check the Console tab for errors.
- Click Validate on the Steam update bar to check the server's files.
- Restart the server.
- Confirm the game and server versions match.
- Check the server's CPU and memory on the Analytics tab.
The tutorial requirement alone accounts for many connection problems. Once players have done it, most other issues are quick to sort out.
Need help? Open a support ticket and we'll take a look.