Windrose is a pirate survival game with dedicated server support. This guide covers how to configure the server and which admin commands are available to manage your world and players.
Server Configuration File
The server generates a configuration file on first launch. This file controls the server's identity, network, and gameplay settings.
Core settings you should change before going live:
Server Name: what players see in the server browser. Pick something descriptive that includes your region and play style, so players browsing the list know what to expect before clicking.
Password: leave empty for public servers. Set a password if you want a private game for your group.
Max Players: the maximum number of concurrent players. Set this based on your hardware. A server with 4 GB of RAM should keep the count modest. With 8 GB or more you have room for a larger crew.
Server Port: the main game traffic port. Default works for most setups. Change it if you run multiple game servers on one machine and need to avoid port conflicts.
Admin Access
Admin privileges let you moderate the server from inside the game. You typically set admin access by adding player identifiers (Steam ID or in-game ID) to the server config or an admin list file.
Once you have admin access, you can use the in-game console to manage the server. Open the console with the tilde key (~) or whatever key the game assigns.
Common Admin Commands
Windrose's command set is still expanding as the game develops. The commands available as of mid-2026:
Player Management
- Kick a player from the server
- Ban a player permanently or for a set duration
- Unban a previously banned player
- View connected players with their IDs
World Management
- Save the world manually (useful before risky changes)
- Set time of day
- Adjust weather conditions
Server Control
- Broadcast a message to all connected players
- Shut down the server gracefully with a countdown
Check the game's documentation or community wiki for the exact command syntax, as these can change between patches.
World Settings
Windrose worlds are persistent. When you stop the server and start it again, the world picks up where it left off. Structures, ships, inventories, and terrain changes all persist.
Key things to configure for your world:
PvP or PvE: whether players can damage each other. Some groups want the tension of pirate-on-pirate combat, others prefer cooperative play against the environment and NPC enemies.
Day/Night Cycle: adjustable length. Shorter nights are more comfortable for casual groups. Longer nights add atmosphere but slow down building and exploration.
Resource Respawn Rate: how quickly resources regenerate after harvesting. Faster rates suit smaller groups where resources per player matter. Slower rates create scarcity and more territorial gameplay.
Port Forwarding
If you self-host, forward the game's required ports on your router. Both TCP and UDP, pointed at the local IP of the machine running the server. The default port is documented in the server config file.
On a VPS or dedicated hosting, ports are already accessible and no forwarding is needed.
Running on Linux
Windrose's server binary is a Windows executable. On Linux, it runs through Wine. Setting up Wine, prefix management, and dependency installation is a chore to do yourself. Managed game hosting handles this automatically.
At Space-Node, the Wine runtime is pre-configured on our Linux servers. The server binary installs and starts through the panel without manual Wine setup.
Backups
Back up the save directory regularly. The world data is the result of hours of collective effort from your players. A corrupted save with no backup is a community-ending event.
Automate it:
- Schedule a daily copy of the save directory to a separate location
- Keep at least three rolling backups so you can go back a few days if needed
- Test a backup restore at least once so you know the process works before you actually need it
Troubleshooting
Players cannot find the server in the browser: verify the query port is open and the server is set to visible. Check that your firewall is not blocking UDP traffic on the query port.
Server crashes on world load: usually a corrupted save file or insufficient RAM. Check the server logs for error messages. If the save is corrupt, restore from backup.
High latency for players far from the server: this is a physics issue, not a configuration one. Players on a different continent from the server will always have higher latency. Host in a region close to where most of your players are.
Wine errors on Linux: missing dependencies or wrong Wine version. If self-hosting on Linux, use a recent Wine version and install the dependencies the server binary needs. Or use managed hosting where this is handled.
FAQ
Does Windrose have official dedicated server documentation? The developers have published basic setup instructions. The community wiki tends to be more comprehensive and up to date, especially for configuration details that change between patches.
Can I run mods on a Windrose server? Mod support depends on what the developers have enabled. Check the game's community channels for the current state of modding. Server-side mods that do not require client changes are the easiest to deploy.
How much RAM does a Windrose server need? For a small group (2-4 players), 2-4 GB is enough. For a larger group with extensive building and exploration, 8-16 GB. World size and structure count are the main factors.
Related: Windrose dedicated server setup guide | Windrose hosting plans