Skip to content

Windrose: Manage Worlds

Learn how to manage multiple Windrose worlds, switch between world saves, and configure your world settings on a Dedicated Server using the right world structure. -> Learn more

10 November 20266 min read0 Views0 helpful

Introduction

Windrose supports multiple worlds on a single Dedicated Server, with each world using its own save data and a WorldDescription.json configuration. In this guide, you'll learn how to create new worlds, switch between existing worlds, create backups, and safely delete worlds.

Understand the Windrose world structure

Windrose stores all world data in the save profile directory. The first world is created automatically when you start the server for the first time.

The relevant structure looks like this:

text
R5/Saved/SaveProfiles/Default
ServerDescription.json
RocksDB
<game_version>
Worlds
World_1_ID
WorldDescription.json
World_2_ID

In practice, the world folders are located here:

text
R5/Saved/SaveProfiles/Default/RocksDB/[deine_spielversion]/Worlds/

Each world folder is named after its unique IslandId. The server uses this ID internally to determine which world to load.

File or folderPurpose
ServerDescription.jsonDefines the active server configuration, including the world currently loaded
RocksDB/[deine_spielversion]/Worlds/Stores all available world save folders
[deine_welt_id]/WorldDescription.jsonStores the configuration for a specific world
WorldIslandIdThe value in ServerDescription.json that tells the server which world to load
Warning

Do not rename world folders Never manually rename a world folder. Windrose uses the folder name as the internal IslandId in the RocksDB database. Renaming it can corrupt the world or make it unusable.

Back up a world

Before switching worlds, deleting data, or testing new settings, you should create a backup of your world.

Use the ZAP-Hosting backup feature

First, stop your server.

We back up your server automatically every day. With the ZapX Pass, you can also open the Backups section in the panel and create a backup of your own with a single click. This is the safest way to restore the complete server state later. Learn more in Backups.

Download world files manually

If you only want a direct copy of the save data, open the Files tab and download the entire RocksDB/ folder using the zip or download option.

Relevant path:

text
R5/Saved/SaveProfiles/Default/RocksDB/
Backup methodRecommended use
Panel backupBest option for a complete server restore
Manual RocksDB/ downloadBest option for directly archiving world saves
Both methodsIdeal for important worlds or before a wipe
Info

Backup recommendation If you manage multiple worlds, keeping both a panel backup and a manual copy of RocksDB/ gives you the most flexibility to restore individual worlds later.

Manage world settings

Each world has its own WorldDescription.json, so you can maintain separate settings for different worlds on the same server.

Example world configuration

json
{
  "Version": 1,
  "WorldDescription": {
    "IslandId": "MeineZweiteWelt",
    "WorldName": "Meine zweite Welt",
    "WorldPresetType": "Medium",
    "WorldSettings": {}
  }
}

Important values

KeyDescription
VersionThe configuration version used by the file
IslandIdInternal world ID; must match the folder name
WorldNameDisplay name of the world
WorldPresetTypePreset type used to generate the world
WorldSettingsAdditional world-specific settings, if supported
Info

Manage configuration in the panel You can edit Windrose configuration files in the Configuration tab (raw text view). If a file isn't available there, use the Files tab to edit it directly.

FAQ

Frequently asked questions

In R5/Saved/SaveProfiles/Default/RocksDB/[game version]/Worlds/—each world folder is named after its unique IslandId.
Open ServerDescription.json and look for the WorldIslandId entry. This value determines which world the server loads at startup.
Stop the server, change the WorldIslandId value in ServerDescription.json to the target world's IslandId (from its WorldDescription.json), save the file, and restart the server.

Feedback

Was this article helpful?

Your feedback helps us prioritize and improve content.

0 of 0 Users found this article helpful.

Personal support

Need more help than the guide provides?

Our ZAP support team knows your product — briefly describe your issue and we'll help you personally.