Windrose, developed by Kraken Express and published in partnership with Pocketpair Publishing, launched into Early Access on April 14, 2026, and quickly surged to a peak concurrent player count of 97,981 on Steam. Built on Unreal Engine, the game delivers a sprawling pirate-themed open world with PvE survival mechanics, ship construction, base building, and deep crafting systems. One of its most compelling features is the multiplayer experience — sailing the open seas with a crew of friends transforms Windrose from a competent solo survival game into something truly memorable.
This guide covers every aspect of Windrose multiplayer: the three available modes, step-by-step instructions for hosting private sessions, a complete dedicated server setup walkthrough, configuration tuning, performance optimization, and troubleshooting for the most common issues. Whether you want a casual co-op session with two friends or a fully configured dedicated server running 24/7 for your guild, this guide has you covered.
Windrose supports up to 8 players in multiplayer, though the developer recommends 4 players for the best balance of performance and experience. You can play through official public matchmaking, host a private session from within the game client, or set up a dedicated server that runs independently of any player's machine.
Multiplayer Modes Overview
Windrose offers three distinct multiplayer modes, each designed for different playstyles and group sizes. Understanding the differences between them helps you choose the right option for your crew.
Public Matches
Public matchmaking pairs you with random players on official servers. You queue up from the main menu, select your preferred region and difficulty, and the system places you in an available session. Public matches are ideal for meeting other players, trying out the multiplayer experience without organizing a group, or filling empty slots when you have fewer than four friends online. The downside is less control over who you play with, and server persistence is limited — public matches reset on a regular cycle.
Private Sessions
Private sessions let you create a password-protected room from within the game client. Only players with the room code or password can join. The session host's machine runs the game world, which means the host needs a reasonably powerful PC and a stable internet connection. Private sessions persist as long as the host remains online. This is the most accessible multiplayer option for small groups who want to play together without the complexity of server administration.
Dedicated Servers
A dedicated server runs the game world on a separate machine — either a home server, a rented VPS, or a cloud gaming server — independent of any player's client. The server stays online 24/7, world progress persists across restarts, and players can join or leave at any time without disrupting the session. Dedicated servers offer the most control over the game experience through extensive configuration options, admin commands, and mod support. This is the recommended approach for communities, large groups, or anyone who wants a persistent pirate world that survives logouts.
Mode Comparison
| Feature | Public Match | Private Session | Dedicated Server |
|---|---|---|---|
| Max Players | 8 | 8 | 8 |
| Host Machine Required | No (official server) | Yes (host's PC) | No (separate server) |
| Recommended Players | 4 | 4 | 4 |
| Latency Sensitivity | Medium | High (host dependent) | Low (server-grade) |
| World Persistence | Limited (reset cycle) | While host is online | Full (24/7) |
| Password Protection | No | Yes | Yes |
| Admin Commands | No | Basic | Full |
| Config Customization | No | In-game options only | Full config files |
| Best For | Casual play, meeting players | Small friend groups | Communities, persistent worlds |
How to Host a Private Session
Hosting a private session is the simplest way to play Windrose with friends. No external tools, no command-line setup, no server hardware — just the game client and a decent internet connection.
Step 1: Create a Private Room
Launch Windrose and navigate to the main menu. Select Multiplayer, then choose Create Private Session. You will be prompted to set a session name and password. The session name helps your friends identify the correct room if they have multiple options, and the password prevents strangers from joining.
After creating the room, you will enter the game world. As the host, your machine is now running the game server, so your PC's performance will be under heavier load than during solo play.
Step 2: Invite Steam Friends
Once your private session is running, open the in-game social menu (default key: O or the friends icon in the HUD). From here you can:
- Send direct invites to players on your Steam friends list — they will receive a notification and can join with one click.
- Copy the Room Code — share this alphanumeric code with friends via Discord or any messaging app. They paste it into the Join menu to connect.
- Share the Session Password — friends can also find your session by searching for your username in the Join menu and entering the password.
Step 3: Room Settings
As the host, you can configure several game parameters before or during the session. Open the Session Settings panel from the pause menu:
| Setting | Options | Default |
|---|---|---|
| PvE Toggle | On / Off | On |
| PvP Toggle | On / Off | Off |
| Difficulty | Normal, Hard, Nightmare | Normal |
| Resource Multiplier | 0.5x, 1x, 2x, 3x, 5x | 1x |
| XP Multiplier | 0.5x, 1x, 1.5x, 2x | 1x |
| Enemy Spawn Rate | Low, Normal, High | Normal |
| Day/Night Cycle Length | 20min, 30min, 45min, 60min | 30min |
| Player Damage | 0.5x, 1x, 2x | 1x |
| Max Players | 2, 4, 6, 8 | 4 |
If you are hosting on a mid-range PC, set the max player count to 4 instead of 8. The difference in performance is significant, especially during ship combat when multiple players, NPC enemies, and physics objects are all active at the same time.
Dedicated Server Setup
Setting up a dedicated server requires more effort than hosting a private session, but the payoff is enormous: a persistent world that runs around the clock, full configuration control, and the ability for players to join and leave freely. This section walks you through every step.
Hardware Requirements
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 4 cores @ 3.0 GHz | 8 cores @ 3.5+ GHz (Ryzen 7 / Core i7) |
| RAM | 8 GB | 16 GB |
| Storage | 20 GB SSD | 40 GB NVMe SSD |
| Network | 20 Mbps upload | 50+ Mbps upload, low-latency connection |
| OS | Windows Server 2019+ / Ubuntu 22.04+ | Windows Server 2022 / Ubuntu 22.04 LTS |
Windrose is built on Unreal Engine, which is CPU-intensive for dedicated servers. The server process does not use a GPU — all physics, AI, and world simulation run on the CPU. Investing in a high-clock-speed CPU matters more than core count for 4 to 8 player servers.
Step 1: Install SteamCMD
SteamCMD is Valve's command-line tool for downloading and updating Steam game server files. It is free and required for setting up a Windrose dedicated server.
Windows:
- Download SteamCMD from Valve's official wiki.
- Extract the archive to a permanent folder, for example
C:\windrose-server\.
Linux (Ubuntu):
sudo apt update sudo apt install steamcmd mkdir -p ~/windrose-server cd ~/windrose-server
Step 2: Download Server Files
Use SteamCMD to download the Windrose dedicated server application. Create a batch script (Windows) or shell script (Linux) to automate the process.
Windows — create update.bat:
steamcmd +force_install_dir C:\windrose-server +login anonymous +app_update [APPID] validate +quit
Linux — create update.sh:
#!/bin/bash steamcmd +force_install_dir ~/windrose-server +login anonymous +app_update [APPID] validate +quit
Replace [APPID] with the Windrose dedicated server application ID (check the official Windrose server documentation on Steam for the exact ID). The initial download is approximately 15–20 GB depending on the build version.
Set up a scheduled task (Windows) or cron job (Linux) to run the update script automatically every day at off-peak hours. This ensures your server stays on the latest version without manual intervention.
Step 3: Configuration Files
After the server files download, navigate to the server directory and locate the configuration folder. The main configuration file is server.cfg (or GameUserSettings.ini depending on the build). This file controls all server behavior.
Key configuration parameters in server.cfg:
# Server Identity ServerName="My Windrose Server" ServerPassword="your_password_here" AdminPassword="your_admin_password" # Network Port=7777 # Game port (default) QueryPort=27015 # Steam query port MaxPlayers=4 # Recommended: 4 (max: 8) # Gameplay Difficulty=Normal # Normal, Hard, Nightmare ResourceMultiplier=1.0 XPMultiplier=1.0 EnemySpawnRate=Normal DayNightCycle=30 # Minutes per full cycle # PvP Settings PvPEnabled=false PlayerDamageMultiplier=1.0 FriendlyFire=false # Persistence AutoSaveInterval=300 # Seconds between auto-saves (5 min) MaxBackupCount=5 # Number of save backups to keep # Performance TickRate=30 # Server tick rate (20-60) NetServerMaxTickRate=30 MaxNPCs=50
Each parameter is self-explanatory, but a few deserve extra attention. The TickRate controls how often the server updates game state — higher values improve responsiveness but increase CPU load. The AutoSaveInterval determines how frequently the world is saved to disk; shorter intervals mean less data loss on crashes but more disk I/O.
Step 4: Port Forwarding
If your dedicated server is behind a router (most home setups), you must forward the following ports to the server machine's local IP address:
| Port | Protocol | Purpose |
|---|---|---|
| 7777 | UDP | Game port (primary connection) |
| 7778 | UDP | Game port (secondary/backup) |
| 27015 | UDP + TCP | Steam query port (server browser visibility) |
| 8777 | UDP | Beacon port (server discovery) |
To configure port forwarding, log into your router's admin panel (usually accessible at 192.168.1.1 or 192.168.0.1), find the Port Forwarding or Virtual Server section, and create entries for each port listed above pointing to your server's local IP (e.g., 192.168.1.100).
If you are renting a VPS or cloud server, ports are typically open by default and you do not need to forward them. However, ensure your hosting provider's firewall allows inbound UDP traffic on the ports above. Many cloud providers block all inbound ports by default — check your security group or firewall rules.
Step 5: Starting the Server
Windows:
cd C:\windrose-server start.bat
The start.bat file should contain a command similar to:
WindroseServer.exe -log -PORT=7777 -QueryPort=27015
Linux:
cd ~/windrose-server ./WindroseServer.sh -log -PORT=7777 -QueryPort=27015
After launching, the server console will display initialization messages. Wait for the line that confirms the server is running and listening on the configured ports. Players can now connect by searching for your server name in the in-game browser or connecting directly via console:
open 123.456.789.012:7777
Step 6: Common Admin Commands
Dedicated server administrators have access to a range of console commands for managing the server and its players. These are entered in the server console or via the in-game admin chat (prefix with /):
| Command | Description |
|---|---|
listplayers | Lists all connected players with their Steam IDs |
kick <playername> | Kicks a player from the server |
ban <playername> | Bans a player (Steam ID) from the server |
unban <steamid> | Removes a player from the ban list |
say <message> | Broadcasts a message to all players |
save | Forces an immediate world save |
shutdown | Gracefully shuts down the server (saves first) |
restart | Restarts the server after a brief warning to players |
settime <hour> | Changes the in-game time (0–24) |
teleport <player> <x> <y> <z> | Teleports a player to coordinates |
give <player> <itemid> <qty> | Gives items to a player |
god | Toggles invincibility on the admin character |
Server Configuration Tips
Beyond the basic parameters, several configuration options can significantly reshape the multiplayer experience. These are the settings that server administrators tweak most frequently.
Resource Output Multipliers
Adjusting ResourceMultiplier changes how many materials players harvest from nodes, trees, rocks, and other gatherable sources. A 2x multiplier is popular for private servers with 2 to 4 players because it accelerates progression without making the game trivial. For larger groups of 6 to 8 players, the default 1x multiplier is usually appropriate since more players means more gathering efficiency by default.
You can also set category-specific multipliers in the advanced configuration. For example, increase wood yield but keep rare ores at default to speed up base building without trivializing endgame crafting:
ResourceMultiplier_Wood=2.0 ResourceMultiplier_Stone=1.5 ResourceMultiplier_Ore=1.0 ResourceMultiplier_Fiber=2.0
Ship Blueprint Restrictions
By default, all players can build any ship blueprint once they have unlocked it. On a dedicated server, you can restrict ship tiers to prevent new players from immediately constructing endgame vessels. This is controlled in the server configuration:
ShipRestrictions=true MaxShipTier=2 # 1=Dhow, 2=Ketch, 3=Brigantine, 4=Frigate
This setting prevents players from building ships above the specified tier, encouraging progression through the shipbuilding tree rather than rushing to the strongest vessel. It is particularly useful for servers that want to maintain a sense of progression across multiple play sessions.
PvP Rules Configuration
While Windrose is primarily a PvE game, the PvP toggle enables player-versus-player combat. The server configuration offers fine-grained control over PvP behavior:
PvPEnabled=true FriendlyFire=false PvPZoneRestriction=coastal # Options: global, coastal, none PvPDamageMultiplier=0.75 # Reduce PvP damage to avoid griefing BaseRaidingAllowed=false # Prevents destruction of player bases ShipBoardingAllowed=true # Allows boarding enemy ships in PvP
The PvPZoneRestriction setting is especially useful — setting it to coastal means PvP is only enabled near shorelines and island perimeters, while the open sea remains a safe zone. This creates interesting territorial dynamics without enabling full-map griefing.
Auto-Save and Backup Strategy
World saves are critical for dedicated servers. Configure these parameters carefully:
AutoSaveInterval=300 # Save every 5 minutes MaxBackupCount=10 # Keep last 10 saves CompressBackups=true # Reduce disk usage BackupDirectory="./backups/"
Set up an external backup script that copies the backups/ directory to a separate location — ideally a different drive or cloud storage — every few hours. If the server's storage fails, your world data survives. On Linux, use rsync in a cron job; on Windows, use Task Scheduler with robocopy.
Performance Tips for Multiplayer
Multiplayer performance is the single most common challenge in Windrose. The game world is dense with physics objects, AI entities, weather systems, and ship simulations — all of which must be synchronized across every connected client. Understanding why performance degrades and how to mitigate it will save you and your players enormous frustration.
Why 8-Player Sessions Strain Performance
Windrose's Unreal Engine architecture handles multiplayer through a client-server model with a state replication system. Every player action — swinging a sword, placing a building piece, firing a cannon — must be transmitted to the server, processed, and replicated to all other clients. With 8 players actively exploring, building, and fighting simultaneously, the volume of network traffic and server-side computations increases dramatically.
Ship combat is the most demanding scenario. Each ship has dozens of physics-enabled components (planks, masts, railings, cargo), and combat involves projectile physics, destruction calculations, and particle effects. A single ship battle with 4 players on each side can generate more network traffic than the rest of a play session combined. This is why the developer officially recommends 4 players — it is the sweet spot where the multiplayer experience is fully enjoyable without consistent performance hiccups.
Optimizing Server Tick Rate
The server tick rate determines how many times per second the server updates the game state. Default is 30 Hz, which is adequate for most PvE gameplay. However, you can tune this based on your server hardware and player count:
| Player Count | Recommended Tick Rate | CPU Impact |
|---|---|---|
| 2–4 players (PvE) | 30 Hz | Low |
| 4–6 players (PvE) | 30 Hz | Moderate |
| 6–8 players (PvE) | 20 Hz (reduce if CPU spikes) | High |
| Any count (PvP combat) | 40–60 Hz | High |
# In server.cfg TickRate=30 NetServerMaxTickRate=30 MaxClientUpdateRate=30
For PvP servers where responsiveness is critical, a higher tick rate (40–60 Hz) improves hit registration and movement accuracy. However, this significantly increases CPU usage. Monitor your server's CPU utilization during peak hours — if it regularly exceeds 85%, lower the tick rate to prevent server-side lag spikes.
Network Optimization
Network performance directly impacts player experience. High latency causes rubber-banding (players teleporting), delayed hit registration, and desynchronized interactions. Apply these optimizations:
- Use wired Ethernet instead of Wi-Fi for the server machine. Wi-Fi introduces jitter and packet loss that compound in multiplayer scenarios.
- Choose a server location geographically central to your player base. If most players are on the US East Coast, do not host the server in Europe.
- Enable QoS (Quality of Service) on your router to prioritize game traffic over other network activity on the same connection.
- Limit background downloads on the server machine — Steam auto-updates, system updates, and other services can saturate your upload bandwidth.
- Monitor server latency with tools like
pingandtraceroutefrom player locations. A consistent ping under 100ms is acceptable; above 150ms will cause noticeable issues.
If you are hosting a dedicated server on the same machine you play on, expect degraded performance for both the server and your client. The server process and the game client compete for CPU cores and memory. For the best experience, run the dedicated server on a separate machine entirely.
Common Issues & Troubleshooting
Even with careful setup, multiplayer issues will arise. This section covers the most frequently reported problems and their solutions.
Friends Cannot Join Your Room
This is the most common issue in Windrose multiplayer. If your friends receive a "Connection Timed Out" or "Server Not Found" error when trying to join, work through these checks in order:
- Verify the room password. The most common cause is a typo in the password. Copy and paste the room code or password directly from the host to avoid transcription errors.
- Check your NAT type. Open the game's network settings and verify your NAT type is Open or Moderate. A Strict NAT type means your router is blocking inbound connections. Enable UPnP in your router settings, or manually forward port 7777 (UDP) to your local IP.
- Disable VPNs and firewalls temporarily. VPN software, aggressive antivirus firewalls, and Windows Defender's default rules can all block game traffic. Temporarily disable them and test the connection.
- Restart the session. Sometimes the host's connection state becomes corrupted. Close the session, wait 30 seconds, and create a new one.
- Verify game version. All players must be on the same game version. If one player has auto-updated and the host has not (or vice versa), connections will fail. Check the build number in the game's main menu or Steam properties.
If UPnP does not work on your router (common with older ISP-provided hardware), manually port forwarding is the most reliable fix. Forward UDP 7777 and UDP 27015 to your PC's local IP address. You can find your local IP by running ipconfig in Command Prompt and looking for the IPv4 Address under your active network adapter.
Server Crashes and Instability
Dedicated server crashes are usually caused by hardware limitations, configuration errors, or corrupt save data. Follow this diagnostic process:
1. Check the server log file. After a crash, open the latest log file in the Logs/ directory. The log will contain an error trace near the bottom that identifies the crash cause. Common error messages include:
- Out of Memory — Increase server RAM or reduce
MaxNPCsandEnemySpawnRate. - Assertion Failed (physics) — Often caused by too many physics objects in one area. Reduce player density or ship concentration.
- NetConnection Timeout — Network instability between server and clients. Check the server's network connection quality.
2. Reduce server load. If crashes happen during peak player activity, lower the tick rate, reduce NPC count, or limit max players temporarily. Stability is more important than maximum settings.
3. Verify file integrity. Run the SteamCMD update command with validate to check all server files for corruption:
steamcmd +force_install_dir C:\windrose-server +login anonymous +app_update [APPID] validate +quit
Data Loss and World Rollbacks
World rollbacks occur when the server crashes before the latest auto-save completes. Players may lose progress from the last few minutes to the last auto-save interval, depending on when the crash occurred relative to the save cycle.
To minimize data loss:
- Shorten the auto-save interval. Reducing
AutoSaveIntervalfrom 300 seconds (5 minutes) to 120 seconds (2 minutes) means a maximum of 2 minutes of lost progress on crash, compared to 5 minutes at the default setting. - Use the
savecommand manually. Before performing risky actions (large ship battles, major building projects), an admin can force a manual save through the console. - Keep backups. The
MaxBackupCountsetting preserves multiple save snapshots. If a save file becomes corrupted, you can restore from a previous backup rather than losing everything. - Never kill the server process forcefully. Use the
shutdowncommand instead of terminating the process. The shutdown command ensures the world is saved before the server exits. Force-killing (via Task Manager orkill -9) skips the save sequence entirely.
If your server crashes and the latest save file is corrupted (the server refuses to start or immediately crashes on load), do not panic. Navigate to the saves/ directory and look for the most recent .bak file. Rename it to replace the corrupted save file. This restores the world to the previous auto-save point, which is typically only minutes before the corruption occurred.
Additional Common Issues
| Issue | Likely Cause | Solution |
|---|---|---|
| Desync — players see different enemy positions | High server tick rate on low-end hardware | Lower TickRate to 20 or upgrade CPU |
| Buildings not appearing for other players | Network packet loss | Check NAT type, reduce network congestion |
| Ships disappearing after server restart | Ship position saved outside world bounds | Teleport the ship to valid coordinates before restart |
| Inventory items lost on death | Grave marker timed out or failed to spawn | Check corpse despawn timer in config; increase if needed |
| Server not showing in browser | Query port blocked or Steam services down | Forward port 27015, verify Steam is running on server |
Windrose is in Early Access, and many of these issues will be addressed in future patches as Kraken Express continues to optimize the multiplayer infrastructure. Keep your server updated, monitor the official Windrose Discord for patch notes, and participate in bug reports — community feedback directly shapes the development roadmap for multiplayer stability.