Dedicated Server Guide

Windrose — Documentation

Dedicated Server Guide

Published: 14 Apr 2026 · Updated: 18 May 2026 · Game Version: 0.10.0.5.120-073042fb

This guide explains how to set up a dedicated server for Windrose.

The same guide is included within the in-game files of the Windrose Dedicated Server app available for free on Steam, in the file DedicatedServer.md. Both sets of instructions are valid and almost identical.

If you happen to have any questions, please visit our Windrose Support for troubleshooting.

Why run a dedicated server?

A dedicated server lets you have a world that’s always running. You and your friends can join anytime — no need for the host to be online. Great for co-op when schedules don’t match, like building ships alone then sailing together later.

Dedicated servers support all the world’s game settings (and a few extras), letting you fully customize your swashbuckling adventures. Win-win for tailoring co-op chaos to your crew!


Initial setup and hosting

There are two ways to get the Windrose Dedicated Server, depending on your platform of choice: Steam, EGS, or Stove.

When you download the game, go to the in-game files and open the R5\Builds folder. There, you will find the WindroseServer folder. That is the dedicated server. If you want to deploy it, copy the folder to any other location on your PC. It will not work inside the game folder; please read more about that in the FAQ. This is important. Once it has been copied anywhere on your PC, you can proceed with the instructions.

Alternatively, you can download the Windrose Dedicated Server application on Steam, which is available for free to everyone. Open the internal folder of this application and proceed with the instructions.

Both of these methods ensure that the build is up to date and free from harmful third-party modifications that could put your data or device at risk.

⚠ Our team will never ask for your login details or passwords on any platform. If you notice anything suspicious, please contact us immediately at support@playwindrose.com.

If you play through EGS/Stove

Copy the R5\Builds\WindowsServer folder from the in-game files and place it anywhere on your PC where you prefer. Then proceed with the instructions.

From here, pick how you want to set up your dedicated server:

Simple — run with defaults for a quick start.
Advanced — edit configs for full customization.

If you play through Steam

  1. Install from Steam
    Navigate to the Tools section in your Steam Library. Click the dropdown filter above your game list and select “Tools.” Search for “Windrose Dedicated Server” or browse the list, then install it like any game or tool.
  2. Access files
    Steam lets you launch directly, but for setup you’ll need the local files. Right-click “Windrose Dedicated Server” → ManageBrowse Local Files.
  3. Choose preferred setup
    Simple — run with defaults for a quick start.
    Advanced — edit configs for full customization.

Simple setup

Perfect if you just want to start the server quickly on your PC! There are two ways to launch:

StartServerForeground.batrecommended. The server runs in a separate command-line window where you can see game logs. To shut down, just close the window.

WindroseServer.exe — use this if you want the server to run as a background process. To close it, open Task Manager and end the process there.

  1. Launch using your preferred method (bat file recommended).
  2. A console window will appear if you use StartServerForeground.bat.
  3. Once loaded, look for an invite code in the console like f1014dc1.
  4. If it scrolled away too fast, open your server folder → R5 folder → find ServerDescription.json.
  5. Open it with any text editor (Notepad will do).
  6. Find the invite code inside, e.g. f1014dc1.
  7. Launch the game: Play → Connect to Server → paste the invite code.
  8. Send the invite code to friends — they connect the same way.

YARR! That’s it. Happy Windrose!


Advanced setup

Server settings are split into two .json files:

ServerDescription.json — common server settings (one file, root folder).
WorldDescription.json — one per world, for world-specific tweaks.

ℹ The server auto-creates default versions on first launch. Start and stop the server once to generate them, then edit as needed.

ServerDescription.json

Single file in the root folder of the application.

FieldDescription
PersistentServerIdUnique identifier of your server. Do not edit this value.
Note: This will be changed in upcoming builds.
InviteCodeInvite code used to find your server. Allowed characters: 0–9, a–z, A–Z. Must contain at least 6 characters. Case-sensitive.
IsPasswordProtectedSpecifies whether a password is required.
Set to true if a password is specified.
Set to false if the password field is empty.
Incorrect configuration may cause unexpected behavior.
PasswordServer password.
ServerNameName of your server. Useful for distinguishing servers with similar invite codes.
WorldIslandIdID of the selected world. Must match the corresponding value in one of the server's WorldDescription.json files. This world will be loaded when the server starts.
MaxPlayerCountMaximum number of simultaneous players allowed on the server.
UserSelectedRegionSpecifies the region for the Connection Service. Supported values: SEA, CIS, EU (EU covers both EU and NA).
If left empty, the server will automatically select the optimal region based on latency.
If specified, the server will use only that region.
P2pProxyAddressIP address used for listening sockets.
UseDirectConnectiontrue: the server creates sockets for direct client connections.
false: the server uses the ICE protocol for P2P connection.
DirectConnectionServerAddressAddress for direct connection. Reserved for future use (currently not used).
DirectConnectionServerPortPort for direct connection. Must be available for both TCP and UDP if UseDirectConnection is set to true.
DirectConnectionProxyAddressCan be used to select a specific network interface on the host machine. Default value: 0.0.0.0
AutoLoadLatestBackupIfHasBrokenIf set to true, on launch the server will try to restore broken save files from backups, as described in SaveWorkflow.md.
CanLaunchMultipleServerInstancesfalse by default, to prevent launching multiple instances of the game server on the same PC. This is an additional safeguard against data corruption when multiple copies of the application work with the same database.
Important: This file should only be modified while the server is shut down. Some fields may be automatically adjusted by the server if issues are detected.
Example JSON
{
  "Version": 1,
  "DeploymentId": "0.10.0.0.251-master-9f800c33",
  "ServerDescription_Persistent": {
    "PersistentServerId": "1B80182E460F727CEA080C8EEBB1EA0A",
    "InviteCode": "d6221bb7",
    "IsPasswordProtected": false,
    "Password": "",
    "ServerName": "",
    "WorldIslandId": "DB57768A8A7746899683D0EEE91F97BF",
    "MaxPlayerCount": 4,
    "UserSelectedRegion": "EU",
    "P2pProxyAddress": "192.168.31.49",
    "UseDirectConnection": false,
    "DirectConnectionServerAddress": "",
    "DirectConnectionServerPort": 7777,
    "DirectConnectionProxyAddress": "0.0.0.0",
    "AutoLoadLatestBackupIfHasBroken": true,
    "CanLaunchMultipleServerInstances": false
  }
}

WorldDescription.json

You can create as many worlds as you need. All worlds are located in:

<root>/R5/Saved/SaveProfiles/Default/RocksDB_v2/<game version>/Worlds/<world id>/WorldDescription.json

The first one is created automatically on server start.

⚠ The WorldIslandId must match the same field in WorldDescription.json in this folder.
FieldDescription
IslandIdUnique world ID. Must match the folder name.
WorldNameName of the world.
CreationTimeCreation time in internal format.
WorldPresetTypeEasy, Medium, or Hard. Custom values force “Custom” on next launch.
WorldSettingsParameters grouped by bool, float, and tag. Empty for presets except “Custom”.
Example: WorldPresetType "Medium"
{
  "Version": 1,
  "WorldDescription": {
    "IslandId": "E24A22C9C8D3448951AFD002162576D5",
    "WorldName": "The Archipelago",
    "CreationTime": 6.3910902400911002e+17,
    "WorldPresetType": "Medium",
    "WorldSettings": {
      "BoolParameters": {
        "{\"TagName\": \"WDS.Parameter.Coop.SharedQuests\"}": true,
        "{\"TagName\": \"WDS.Parameter.EasyExplore\"}": false
      },
      "FloatParameters": {
        "{\"TagName\": \"WDS.Parameter.MobHealthMultiplier\"}": 1,
        "{\"TagName\": \"WDS.Parameter.MobDamageMultiplier\"}": 1,
        "{\"TagName\": \"WDS.Parameter.ShipsHealthMultiplier\"}": 1,
        "{\"TagName\": \"WDS.Parameter.ShipsDamageMultiplier\"}": 1,
        "{\"TagName\": \"WDS.Parameter.BoardingDifficultyMultiplier\"}": 1,
        "{\"TagName\": \"WDS.Parameter.Coop.StatsCorrectionModifier\"}": 1,
        "{\"TagName\": \"WDS.Parameter.Coop.ShipStatsCorrectionModifier\"}": 0
      },
      "TagParameters": {
        "{\"TagName\": \"WDS.Parameter.CombatDifficulty\"}": {
          "TagName": "WDS.Parameter.CombatDifficulty.Normal"
        }
      }
    }
  }
}
Example: WorldPresetType "Easy"
{
  "Version": 1,
  "WorldDescription": {
    "IslandId": "26C14DC8A78D4AF69E9C77527C934CF3",
    "WorldName": "The Archipelago",
    "CreationTime": 6.3911887576664998e+17,
    "WorldPresetType": "Easy",
    "WorldSettings": {
      "BoolParameters": {
        "{\"TagName\": \"WDS.Parameter.Coop.SharedQuests\"}": true,
        "{\"TagName\": \"WDS.Parameter.EasyExplore\"}": false
      },
      "FloatParameters": {
        "{\"TagName\": \"WDS.Parameter.MobHealthMultiplier\"}": 0.7,
        "{\"TagName\": \"WDS.Parameter.MobDamageMultiplier\"}": 0.6,
        "{\"TagName\": \"WDS.Parameter.ShipsHealthMultiplier\"}": 0.7,
        "{\"TagName\": \"WDS.Parameter.ShipsDamageMultiplier\"}": 0.6,
        "{\"TagName\": \"WDS.Parameter.BoardingDifficultyMultiplier\"}": 0.7,
        "{\"TagName\": \"WDS.Parameter.Coop.StatsCorrectionModifier\"}": 1,
        "{\"TagName\": \"WDS.Parameter.Coop.ShipStatsCorrectionModifier\"}": 0
      },
      "TagParameters": {
        "{\"TagName\": \"WDS.Parameter.CombatDifficulty\"}": {
          "TagName": "WDS.Parameter.CombatDifficulty.Easy"
        }
      }
    }
  }
}
Example: WorldPresetType "Hard"
{
  "Version": 1,
  "WorldDescription": {
    "IslandId": "26C14DC8A78D4AF69E9C77527C934CF3",
    "WorldName": "The Archipelago",
    "CreationTime": 6.3911887576664998e+17,
    "WorldPresetType": "Hard",
    "WorldSettings": {
      "BoolParameters": {
        "{\"TagName\": \"WDS.Parameter.Coop.SharedQuests\"}": true,
        "{\"TagName\": \"WDS.Parameter.EasyExplore\"}": false
      },
      "FloatParameters": {
        "{\"TagName\": \"WDS.Parameter.MobHealthMultiplier\"}": 1.5,
        "{\"TagName\": \"WDS.Parameter.MobDamageMultiplier\"}": 1.25,
        "{\"TagName\": \"WDS.Parameter.ShipsHealthMultiplier\"}": 1.5,
        "{\"TagName\": \"WDS.Parameter.ShipsDamageMultiplier\"}": 1.25,
        "{\"TagName\": \"WDS.Parameter.BoardingDifficultyMultiplier\"}": 1.5,
        "{\"TagName\": \"WDS.Parameter.Coop.StatsCorrectionModifier\"}": 1,
        "{\"TagName\": \"WDS.Parameter.Coop.ShipStatsCorrectionModifier\"}": 0
      },
      "TagParameters": {
        "{\"TagName\": \"WDS.Parameter.CombatDifficulty\"}": {
          "TagName": "WDS.Parameter.CombatDifficulty.Hard"
        }
      }
    }
  }
}

Custom preset parameters

ℹ It may be easier to set up a custom preset in the game and then copy the resulting values to the dedicated server file manually. The parameter list and its value ranges may change in upcoming builds.

Each parameter name below shows the friendly label followed by the actual tag suffix used in JSON (the full tag is WDS.Parameter.<suffix>).

Parameter (tag suffix)DefaultDetails
CoopQuests (Coop.SharedQuests)trueIf any player on the server completes a quest marked as a co-op quest, it auto-completes for all players who currently have it active.
EasyExplore (EasyExplore)falseWhen set to true, disables map markers that highlight points of interest, making them harder to find. Note: “EasyExplore” is the legacy name; in-game it is called “Immersive exploration” and, in effect, makes exploration harder.
MobHealthMultiplier (MobHealthMultiplier)1.0Defines how much Health enemies have. Range: [0.2; 5.0]
MobDamageMultiplier (MobDamageMultiplier)1.0Defines how hard enemies hit. Range: [0.2; 5.0]
ShipHealthMultiplier (ShipsHealthMultiplier)1.0Defines how much Ship Health enemy ships have. Range: [0.4; 5.0]
ShipDamageMultiplier (ShipsDamageMultiplier)1.0Defines how much Damage enemy ships deal. Range: [0.2; 2.5]
BoardingDifficultyMultiplier (BoardingDifficultyMultiplier)1.0Defines how many enemy sailors must be defeated to win a boarding action. Range: [0.2; 5.0]
CoopStatsCorrectionModifier (Coop.StatsCorrectionModifier)1.0Adjusts enemy Health and how fast enemies lose Posture, based on the number of players on the server. Range: [0.0; 2.0]
CoopShipStatsCorrectionModifier (Coop.ShipStatsCorrectionModifier)0.0Adjusts enemy Ship Health based on the number of players on the server. Range: [0.0; 2.0]
CombatDifficulty (CombatDifficulty)NormalDefines how difficult boss encounters are and how aggressive enemies are in general. Allowed values: Easy / Normal / Hard

Updating World Settings in WorldDescription.json

To change WorldDescription.json settings on a Dedicated Server, follow these steps:

  1. Stop the WindroseServer application.
  2. Make the necessary changes to the WorldDescription.json file of the selected world inside the Saved\SaveProfile\Default\RocksDB_v2 folder.
  3. Locate the R5WorldDescriptionUpdater.exe file in the server root folder.
  4. Open Command Prompt and navigate to that folder.
  5. Run the updater with the path to the selected world's WorldDescription.json file:
R5WorldDescriptionUpdater.exe <path_to_world>\WorldDescription.json

For example:

R5WorldDescriptionUpdater.exe R5\Saved\SaveProfiles\Default\RocksDB_v2\0.10.0\Worlds\796AE3C6113C451DE5BD791D70E4A52B\WorldDescription.json

Direct IP Connection Scenarios

There are two common setups for Direct IP connections, depending on whether the players are on the same local network or connecting over the internet.

Players on Different Networks (Different Routers / Different Homes)

Example: each player connects from their own home internet connection.

In this scenario, the person hosting the server must have a public external IP address assigned to their router. Some internet providers offer this as a paid service.

The host must configure port forwarding on their router using the following mapping:

external_ip:external_port (TCP + UDP)
internal_ip:gameserver_port (TCP + UDP)

Both TCP and UDP forwarding are required.

Definitions:

TermDescription
external_ipPublic IP address assigned to the router by the ISP.
external_portPort configured in the router's port forwarding settings.
internal_ipLocal IP address of the computer running the dedicated server.
gameserver_portPort selected in the server UI when launching the server.

How it works

Connections made to the router's public IP and forwarded port are redirected to the local machine running the server.

Example:

203.0.113.25:17777  →  192.168.1.100:7777

The host then shares:

  1. Their public IP address.
  2. The forwarded port.

The second player connects using that IP and port in the game client.

Players on the Same Local Network (LAN)

Example: two players in the same house using the same router.

In this case:

  1. No public IP is required.
  2. No port forwarding is required.

The host simply launches the server and selects a port in the server UI, then shares:

  1. The local IP address of the server machine.
  2. The selected server port.

The second player connects using the local IP and port. Example:

192.168.1.100:7777
Troubleshooting Direct IP Connections

If connection problems occur, try the following:

  1. Verify the server IP address using ipconfig. Run this on the machine hosting the server.
  2. Try changing the port from 7777 to a higher alternative, such as:
    17777, 27890, or any unused port below 65000.
  3. Temporarily disable Windows Firewall.
  4. Ensure the game client has permission to access the network.
  5. Temporarily disable antivirus software.
  6. Confirm that both TCP and UDP traffic are allowed for the selected port.
  7. Make sure the server is fully started before attempting to connect.

F.A.Q.

System requirements for dedicated server?
2 players
CPU: Intel Xeon Scalable (Sapphire Rapids), 2 cores, 3.2 GHz
RAM: 8 GB
Storage: 35 GB SSD
4 players
CPU: Intel Xeon Scalable (Sapphire Rapids), 2 cores, 3.2 GHz
RAM: 12 GB
Storage: 35 GB SSD
10 players
CPU: Intel Xeon Scalable (Sapphire Rapids), 2 cores, 3.2 GHz
RAM: 16 GB
Storage: 35 GB SSD

For self-hosting (game client + server on same machine): min 16 GB RAM for the client, plus 8 GB more (24 GB total recommended). SSD strongly recommended. Share your experience on Windrose Support

Server won’t start or crashes on launch

Verify game files in Steam. Update GPU drivers. Update your OS. Add firewall/antivirus exceptions for WindroseServer.exe. Restart PC and router.

Can I run on Linux / headless?

Currently Windows-only, unfortunately.

How to install the Dedicated Server via SteamCMD?

You can install and update the Windrose Dedicated Server using SteamCMD, which is the recommended method for headless environments, remote servers, and automation setups.

Step-by-step setup

  1. Install SteamCMD on your system (available for Windows and Linux from Valve’s official resources)
  2. Launch SteamCMD
  3. Run the following commands:
force_install_dir "C:\Game_Servers\Windrose_Server"
login anonymous
app_update 4129620 validate
quit

Explanation of commands

force_install_dir — Specifies the directory where the server files will be installed. You can replace this with any valid path.

login anonymous — Logs into Steam anonymously. The dedicated server does not require a purchased copy of the game to install.

app_update 4129620 validate — Downloads and installs the latest version of the Windrose Dedicated Server. The validate flag ensures all files are correctly downloaded and not corrupted.

quit — Exits SteamCMD once the installation is complete.

Updating the server

To update the server later, simply rerun:

app_update 4129620 validate

This will download only the changed files and keep your server up to date.

Important: Make sure your dedicated server version always matches the game client version. If the versions differ, players may experience connection issues, unexpected behavior, or be unable to join the server at all. In some cases, version mismatches can also lead to subtle bugs that are difficult to diagnose. For this reason, we strongly recommend updating your server regularly, especially after game patches or hotfixes — to ensure full compatibility and a stable gameplay experience.
What ports does the server use?

Ports are dynamically assigned via NAT punch-through. Ensure your router supports UPnP. Disable proxy/VPN temporarily if connections fail.

Where are my saves stored?

If you are self-hosting from the game client, your saves are stored inside your AppData folder.

To access it:

  1. Press Win + R
  2. Paste the following path:
    %localappdata%\R5\Saved\
  3. Press Enter

You should now see the SaveProfiles folder. Inside, open your %YOUR_STEAM_ID% folder. Depending on your game version and migration state, you may see the following folders:

  • RocksDB — old main saves before update 0.10.0.5.120
  • %YOUR_STEAM_ID%_Backups — old backups before update 0.10.0.5.120
  • RocksDB_v2 — new runtime folder used while the game is running to store required runtime files after update 0.10.0.5.120. DO NOT TOUCH IT.
  • RocksDB_v2_Backups — new backups after update 0.10.0.5.120

Because of the various situations currently possible, you first need to determine where your actual saves are located:

  • Whether the game was updated
  • Whether the world was launched after the update
  • Whether migration already happened
  • Whether backups were already created

In most cases, if you updated the game and launched it at least once, migration should happen automatically and your saves should appear inside RocksDB_v2_Backups. If not, they should be stored in RocksDB.

If you experience any issues with this process, refer to the Save Issues FAQ section.

Dedicated Server Saves

If you are using a dedicated server, save files are stored inside the dedicated server directory:

Windrose Dedicated Server\R5\Saved\SaveProfiles\Default\

The same folder logic applies here as well. However, dedicated servers only use the Worlds folder, since they store only world-related data and do not store player character data here.

How do I transfer saves between the game client and a dedicated server?
⚠ Always back up your saves first. Before proceeding, completely shut down the dedicated server and the game client.

Transferring Saves From Client → Dedicated Server

STEP 1 — Locate Your World Save

Depending on your platform and migration state, your saves may be located in either:

  • RocksDB (old main saves before update 0.10.0.5.120)
  • RocksDB_v2_Backups (usually contains migrated backups, new backup folder after update 0.10.0.5.120)

Refer to Where Are My Saves Stored? if you are unsure which folder contains your actual saves.

Steam:

C:\Users\{UserName}\AppData\Local\R5\Saved\SaveProfiles\{YourProfile}\RocksDB\{GameVersion}\Worlds\{WorldID}

OR

C:\Users\{UserName}\AppData\Local\R5\Saved\SaveProfiles\{YourProfile}\RocksDB_v2_Backups\{GameVersion}\Worlds\{WorldID}

(look for the _Latest backup if applicable)

Epic Games Store:

C:\Users\{UserName}\AppData\Local\R5\Saved\SaveProfiles\{YourProfile}\RocksDB\{GameVersion}\Worlds\{WorldID}

OR

C:\Users\{UserName}\AppData\Local\R5\Saved\SaveProfiles\{YourProfile}\RocksDB_v2_Backups\{GameVersion}\Worlds\{WorldID}

(look for the _Latest backup if applicable)

Stove:

C:\Users\{UserName}\AppData\Local\R5\Saved\SaveProfiles\StoveDefault\RocksDB\{GameVersion}\Worlds\{WorldID}

OR

C:\Users\{UserName}\AppData\Local\R5\Saved\SaveProfiles\StoveDefault\RocksDB_v2_Backups\{GameVersion}\Worlds\{WorldID}

(look for the _Latest backup if applicable)

STEP 2 — Copy the World Folder

Example (or similarly inside RocksDB_v2_Backups\{GameVersion}\Worlds\):

C:\Users\YarrHarrPirate\AppData\Local\R5\Saved\SaveProfiles\76561199699067790\RocksDB\0.10.0\Worlds\EC10598E83A14ED04D9C44CBFBF3F4B1

Copy the entire WorldID folder.

STEP 3 — Paste It Into the Dedicated Server

Paste the copied folder into (or similarly inside RocksDB_v2_Backups\{GameVersion}\Worlds\):

Windrose Dedicated Server\R5\Saved\SaveProfiles\Default\RocksDB\{GameVersion}\Worlds\

STEP 4 — Set Correct WorldIslandID

Open ServerDescription.json, find "WorldIslandID", and set its value to the exact name of the copied world folder. Example:

"WorldIslandID": "EC10598E83A14ED04D9C44CBFBF3F4B1"

Save the file.

STEP 5 — Launch the Dedicated Server

Start the server and verify that the world loads correctly.

Transferring Saves From Dedicated Server → Client

The process is essentially the same, but reversed.

STEP 1 — Locate the Dedicated Server World Save

Navigate to:

Windrose Dedicated Server\R5\Saved\SaveProfiles\Default\RocksDB\{GameVersion}\Worlds\

Locate the correct WorldID folder. You may also need to check RocksDB_v2_Backups depending on the server version and migration state.

STEP 2 — Copy the World Folder

Copy the entire WorldID folder from the dedicated server.

STEP 3 — Paste It Into the Client Save Folder

Steam / EGS:

C:\Users\{UserName}\AppData\Local\R5\Saved\SaveProfiles\{YourProfile}\RocksDB\{GameVersion}\Worlds\

Stove:

C:\Users\{UserName}\AppData\Local\R5\Saved\SaveProfiles\StoveDefault\RocksDB\{GameVersion}\Worlds\

You may also choose to place it inside RocksDB_v2_Backups\{GameVersion}\Worlds if you are working with migrated saves.

STEP 4 — Launch the Game

Start Windrose normally through Steam / EGS / Stove. If prompted about save conflicts, choose local saves. This prevents cloud data from overwriting the transferred save.

Why is there a WindroseServer folder in the main game?

You cannot launch the dedicated server from the main game folder. The WindowsServer folder there serves a different role — it’s a complementary part of the client. If you launch it from the game folder, the client will shut it down. However, if you copy that folder to any other location, it works as a proper dedicated server.

How do I store multiple worlds on my server?

In ServerDescription.json, change the WorldIslandId field to the ID of the world you want to load, then save the file and launch the server.

Depending on whether you updated to 0.10.0.5.120 or not, world folders may be located in:

R5\Saved\SaveProfiles\Default\RocksDB\{GameVersion}\Worlds

or

R5\Saved\SaveProfiles\Default\RocksDB_v2_Backups\{GameVersion}\Worlds
⚠ Do not rename world folders — the database relies on those IDs.
My game has been updated. Should I update my dedicated server, too?

Absolutely! The game version and the dedicated server version should match; otherwise, bugs may occur. So when your game client has been updated, make sure to update the dedicated server files, too. To do so:

  1. Download and install the latest game update.
  2. Take the files from the WindroseServer folder inside the game files and move them to wherever you want to store your new dedicated server.
  3. Take your old saves from the previous dedicated server’s R5\Saved folder and place them in the new dedicated server’s R5\Saved folder.
  4. Launch the new dedicated server as usual.
I have useful info to add to this guide

We appreciate it! Visit Windrose Support


← Back to playwindrose.com