Windrose Server Settings Explained: ServerDescription and World Files
Windrose splits its dedicated server settings across two JSON files. ServerDescription.json controls the server itself (name, password, invite code, player cap, world to load). Each world has its own WorldDescription.json that controls difficulty and gameplay multipliers.
Everything here is taken from the developers' official dedicated server guide (last updated May 18, 2026, game version 0.10.0.5.120). The game is in early access and the guide itself says parameter names and ranges may change, so recheck after big patches.
- On ChicagoServers, Server name, Invite code, Join password and Region are fields on the Startup tab. The rest of
ServerDescription.jsonis the Server description file on the Configs tab. - Server-level settings live in
R5\ServerDescription.json:ServerName,Password,IsPasswordProtected,InviteCode,MaxPlayerCount,WorldIslandIdand more. - If you edit the password in the file yourself, you must also set
IsPasswordProtectedtotrue. The simplest route is the Join password field on the Startup tab. - World difficulty lives in each world's
WorldDescription.json: presets Easy, Medium, Hard, or a Custom set of multipliers. - Stop the server before editing.
WorldDescription.jsonis edited on the Files tab. The game'sR5WorldDescriptionUpdater.exestep cannot be run from the panel, so contact support for it. - Never edit
PersistentServerIdand never rename world folders.
On this page
Where the Windrose server settings files are
Both files are plain JSON, so any text editor works. On ChicagoServers, open ServerDescription.json on the Configs tab (Server description) and WorldDescription.json on the Files tab. Their locations in the official guide:
| File | Location | Controls |
|---|---|---|
ServerDescription.json | R5\ServerDescription.json under the server folder (Configs tab, Server description) | The server: name, password, code, player cap, region, connection mode, active world |
WorldDescription.json | R5\Saved\SaveProfiles\Default\RocksDB_v2\<game version>\Worlds\<world id>\ (open it on the Files tab) | One world: display name, difficulty preset, custom multipliers |
Neither file exists until the server has run once. Click Start once, then Stop, then edit; the Configs tab tells you when a file does not exist yet. The save folder name (RocksDB_v2, previously RocksDB) changed with update 0.10.0.5.120, so if you find older guides pointing at a different folder, trust the folder that actually exists on your server.
ServerDescription.json: every key
This is the key list from the official guide's example file. The values shown are the guide's examples, not guaranteed defaults.
| Key | What it does | Example / default |
|---|---|---|
PersistentServerId | Unique server ID | Do not edit |
InviteCode | Code players enter to find the server. Letters and digits, 6+ characters, case-sensitive | d6221bb7 |
IsPasswordProtected | Must be true if a password is set, false if the password is empty | false |
Password | Server password | empty |
ServerName | Display name, useful for telling servers apart | empty |
WorldIslandId | ID of the world to load; must match a world's IslandId | a 32-character hex ID |
MaxPlayerCount | Maximum simultaneous players | 4 in the example |
UserSelectedRegion | SEA, CIS or EU (EU covers EU and NA). Empty means auto-select by latency | EU |
P2pProxyAddress | IP address used for listening sockets | a LAN IP in the example |
UseDirectConnection | true for direct IP play, false for ICE peer-to-peer (invite code) | false |
DirectConnectionServerAddress | Reserved for future use; currently unused | empty |
DirectConnectionServerPort | Port for direct connections; open TCP and UDP when direct connection is on | Port for direct connections; on your own machine, open TCP and UDP when direct connection is on. On ChicagoServers the panel assigns the port (Startup tab, Network) |
DirectConnectionProxyAddress | Selects a network interface on the host | 0.0.0.0 |
AutoLoadLatestBackupIfHasBroken | On launch, restores a broken save from backup when true | true |
CanLaunchMultipleServerInstances | Prevents more than one server instance on a PC, protecting against save corruption | false |
On ChicagoServers, the Server name, Invite code, Join password and Region fields on the Startup tab cover ServerName, InviteCode, Password and UserSelectedRegion. Names, passwords, ports and player slots are written from the Startup tab and your plan at every start, so editing ServerName, Password, InviteCode, the port keys or MaxPlayerCount in the file does not stick. Everything else in the table can be edited on the Configs tab.
In the official example file these keys sit inside a ServerDescription_Persistent object, next to top-level Version and DeploymentId fields that the guide does not explain. Leave those alone.
The player cap deserves a note. The guide does not state a hard maximum for MaxPlayerCount. The Steam page says the game supports up to 8 players and that parties of 4 give the best experience, so treat 8 as the practical ceiling and 4 as the comfortable number, and check the current patch notes before going higher.
Setting a password the right way
On ChicagoServers, type the password into Join password on the Startup tab, click Save startup, then Restart. If you edit the file yourself (server stopped), a password needs two edits that must agree. Put the password in Password and set IsPasswordProtected to true. To remove the password, empty the field and set the flag back to false. The official guide is explicit that the flag must match whether the field is empty.
"IsPasswordProtected": true,
"Password": "your-password-here",
"ServerName": "Our Crew",
"MaxPlayerCount": 4,The password is an extra requirement on top of the invite code, so players need both.
World difficulty: presets in WorldDescription.json
Each world file has a WorldPresetType of Easy, Medium or Hard, plus a WorldSettings block that is empty for presets and filled in for a Custom world. Open the file on the Files tab with the server stopped. The preset values in the guide:
| Preset | Mob health | Mob damage | Ship health | Ship damage | Boarding | Combat difficulty |
|---|---|---|---|---|---|---|
| Easy | 0.7 | 0.6 | 0.7 | 0.6 | 0.7 | Easy |
| Medium | 1.0 | 1.0 | 1.0 | 1.0 | 1.0 | Normal |
| Hard | 1.5 | 1.25 | 1.5 | 1.25 | 1.5 | Hard |
All three presets use Coop.StatsCorrectionModifier of 1 and Coop.ShipStatsCorrectionModifier of 0. The guide notes that custom values force the type to "Custom" on the next launch, so do not expect to nudge one number and still be labeled Medium.
Custom world parameters and their ranges
A Custom world stores its values as tags. The full tag is WDS.Parameter.<name>, and the JSON key is that tag wrapped in a small JSON string, as the guide's Medium example shows. Booleans go under BoolParameters, numbers under FloatParameters, and combat difficulty under TagParameters.
| Parameter | Default | Range / notes |
|---|---|---|
Coop.SharedQuests | true | Co-op quests complete for all active players when one finishes them |
EasyExplore | false | Legacy name; shown in-game as "Immersive exploration". Enabling it removes point-of-interest markers |
MobHealthMultiplier | 1.0 | 0.2 to 5.0 |
MobDamageMultiplier | 1.0 | 0.2 to 5.0 |
ShipsHealthMultiplier | 1.0 | 0.4 to 5.0 |
ShipsDamageMultiplier | 1.0 | 0.2 to 2.5 |
BoardingDifficultyMultiplier | 1.0 | 0.2 to 5.0 |
Coop.StatsCorrectionModifier | 1.0 | 0.0 to 2.0; scales enemy health and posture loss with player count |
Coop.ShipStatsCorrectionModifier | 0.0 | 0.0 to 2.0; scales enemy ship health with player count |
CombatDifficulty | Normal | Easy, Normal or Hard (tag value, for example WDS.Parameter.CombatDifficulty.Normal) |
"FloatParameters": {
"{\"TagName\": \"WDS.Parameter.MobHealthMultiplier\"}": 1.5
}Applying a world change and switching worlds
- Back up and stop the server
On the Backups tab, choose World and settings and click Back up now. Then click Stop at the top of the server page so nothing is writing to the save.
- Edit WorldDescription.json
Open the Files tab, go to the world's folder (the path is in the table above) and click
WorldDescription.jsonto open it in the editor. Change the preset or the custom parameters, then click Save. - Run the updater
The official guide runs the command below against that world's file before the server starts. There is no panel button for it, so contact support to have it run, then click Start.
R5WorldDescriptionUpdater.exe <path_to_world>\WorldDescription.json
To load a different world, change WorldIslandId in the Server description file on the Configs tab (server stopped) to that world's ID, click Save, then Restart. The ID must match the world's IslandId and its folder name. Do not rename world folders, because the save database relies on those IDs.
Frequently asked questions
Where is the Windrose server name set?
On ChicagoServers, in the Server name field on the Startup tab (Save startup, then Restart). In the file it is the ServerName key of ServerDescription.json, inside the ServerDescription_Persistent object, and the panel writes it from the Startup tab at every start. It is empty by default and only affects how the server is displayed, so it helps when you run several worlds.
Why is my Windrose server password not working?
Set it in the Join password field on the Startup tab. If you edit the file yourself, the password needs IsPasswordProtected set to true in addition to a value in Password, and if the flag and the field disagree the official guide says to fix the flag. Edit with the server stopped and restart afterwards.
How do I change Windrose difficulty on a dedicated server?
Stop the server, then edit the world's WorldDescription.json on the Files tab, setting WorldPresetType to Easy, Medium or Hard or filling in custom parameters. The official guide then runs R5WorldDescriptionUpdater.exe against that file; contact support to have that step run on ChicagoServers.
Can I change MaxPlayerCount above 4?
The key accepts a value you choose and the official guide gives no hard cap. On ChicagoServers player slots are set by the panel and your plan, so an edit in the file may not stick. The Steam page says up to 8 players are supported with 4 recommended, so stay within that unless a newer patch note says otherwise.