Configuring WindRose+

Windrose+ is an open-source community mod framework for Windrose dedicated servers. It adds gameplay multipliers beyond what WorldDescription.json exposes, plus a Lua scripting host for community mods (similar to how Oxide works for Rust).

As of the current Windrose build, the official game has no native admin console or scripting API. Windrose+ is the de facto extension layer.

What Windrose+ Adds

Out of the box, Windrose+ provides nine extra multipliers configured through windrose_plus.json:

• XP gain

• Loot drops

• Stack size

• Craft cost

• Crop growth speed

• Cooking speed

• Harvest yield

• Inventory size

• Weight (carry capacity)

These are independent of the multipliers in WorldDescription.json, which focus on combat and ship stats.

Beyond the multipliers, Windrose+ provides hooks for community-built Lua mods.

Installing Windrose+

The cleanest way is through your panel's Startup variables, if the egg exposes them.

Via Startup Variable (Recommended)

1. Stop the server.

2. Open the Startup tab.

3. Look for a Modding Framework or Windrose+ Version variable.

4. Set it to latest (or a specific version like 1.2.3 to pin).

5. Save.

6. Start the server. The egg downloads Windrose+ on boot.

After startup, look for a Windrose+ banner in the console with a version number.

Manual Install (Fallback)

If the Startup variable is not available:

1. Stop the server.

2. Download the latest Windrose+ release from its GitHub repository.

3. Connect via SFTP and upload the release contents to the server root, following the README's folder mapping. Typically this adds a few files alongside the Windrose binary and creates a WindrosePlus/ folder.

4. Start the server.

The first run creates windrose_plus.json with default multipliers (all 1.0).

Editing windrose_plus.json

Standard JSON, no tagged keys. Located at the server root. Example:

{
  "XPMultiplier": 2.0,
  "LootMultiplier": 1.5,
  "StackSizeMultiplier": 2.0,
  "CraftCostMultiplier": 0.75,
  "CropGrowthMultiplier": 2.0,
  "CookingSpeedMultiplier": 1.5,
  "HarvestYieldMultiplier": 1.5,
  "InventorySizeMultiplier": 1.0,
  "WeightMultiplier": 1.0
}

Restart the server after edits, since Windrose+ reads the file on boot.

Preset Configurations

Vanilla Feel

All values at 1.0. The default; use this if you only want Windrose+ for its mod hosting capability.

Casual

Friendly to weekend players who do not have time to grind:

{
  "XPMultiplier": 1.5,
  "LootMultiplier": 1.5,
  "StackSizeMultiplier": 2.0,
  "CraftCostMultiplier": 0.85,
  "CropGrowthMultiplier": 1.5,
  "CookingSpeedMultiplier": 1.5,
  "HarvestYieldMultiplier": 1.5,
  "InventorySizeMultiplier": 1.5,
  "WeightMultiplier": 1.25
}

Grind-Free

For players who want to focus on naval combat and exploration, not resource management:

{
  "XPMultiplier": 3.0,
  "LootMultiplier": 3.0,
  "StackSizeMultiplier": 5.0,
  "CraftCostMultiplier": 0.5,
  "CropGrowthMultiplier": 3.0,
  "CookingSpeedMultiplier": 2.0,
  "HarvestYieldMultiplier": 3.0,
  "InventorySizeMultiplier": 2.0,
  "WeightMultiplier": 2.0
}

Hardcore

Slower progression than vanilla, for crews who want the full grind:

{
  "XPMultiplier": 0.75,
  "LootMultiplier": 0.85,
  "StackSizeMultiplier": 1.0,
  "CraftCostMultiplier": 1.25,
  "CropGrowthMultiplier": 0.85,
  "CookingSpeedMultiplier": 1.0,
  "HarvestYieldMultiplier": 0.85,
  "InventorySizeMultiplier": 1.0,
  "WeightMultiplier": 1.0
}

Updating Windrose+

If you used the Startup variable approach with latest, Windrose+ updates on every server boot automatically. To update sooner, restart the server.

If you pinned to a specific version (e.g., 1.2.3), edit the Startup variable to the new version number, then restart.

Your existing windrose_plus.json and any installed Lua mods are preserved through updates. You will not lose your multipliers when upgrading.

Pak Mods (Most Community Mods)

Pak mods are .pak files compiled by mod creators that drop into a mods folder. As the Windrose modding scene matures, this is the install pattern most user-facing mods will use.

General procedure (varies by mod):

1. Stop the server.

2. Take a backup through the panel's Backups tab. Always.

3. Download the mod's .pak file.

4. Upload via SFTP to the location specified in the mod's README. Common targets: R5/Content/Paks/~mods/ or WindrosePlus/Mods/.

5. Start the server.

6. Check the Console for the mod's loading banner.

Some mods are server-side only (no client install required). Others require every player to install the same mod through the Windrose mod manager when one is available. Always read each mod's documentation.

UE4SS Mods (Advanced)

UE4SS (Unreal Engine 4 Scripting System) mods are advanced runtime mods that hook into the engine at a lower level. They can do more than Pak mods but are more fragile across game updates.

If you install UE4SS mods:

• Expect them to break on every Windrose patch until the mod author updates

• Test thoroughly on a sandbox world before deploying to your main server

• Keep backups of every successful working state so you can roll back fast

Most server owners will not need UE4SS mods. Stick with Windrose+ multipliers and Pak mods unless you have a specific reason to go deeper.

Backups Before Mod Changes

Always snapshot your server through the panel's Backups tab before:

• Installing any new mod (Pak or UE4SS)

• Updating Windrose+ to a new major version

• Removing a mod (especially one that modified saved game data)

A bad mod can corrupt the save. A backup is your only recovery.

Removing a Mod

To uninstall:

1. Stop the server.

2. Delete the mod's .pak file (or Lua files) from the mods folder.

3. Start the server.

If the mod modified persistent world data (custom items in player inventories, new structure types in the world), those references may now be invalid. Some mods include a cleanup script; check the mod's documentation. If not, restore a backup from before the mod was installed.

Common Issues

• Mod will not load: Check the Console for the failure reason. Most common causes: wrong folder path, missing dependency (another mod the new mod requires), or version mismatch with the current Windrose build.

• Server crashes after mod install: Stop, remove the mod, restart. Some mods are incompatible with each other or with the current Windrose patch.

• windrose_plus.json values reset themselves: Likely you edited while the server was running. Windrose+ writes the file back on shutdown. Always stop first, edit, save, then start.

• Mods worked yesterday, broke after restart: Windrose pushed a patch overnight. The auto-update pulled the new game version but the mod has not been updated for it yet. Either roll back to the previous game version (advanced) or wait for the mod author to ship an update.

What to Read Next

• Updates and Maintenance for backup workflows that protect mod installations

• World Settings for the combat and ship multipliers, which complement Windrose+'s economy multipliers

• The Windrose+ GitHub repository is the source of truth for the framework's current capabilities and Lua mod API

Made with 💜 by GameServerKings