Deranged HostingDeranged Hosting

Sandbox / Building Guide

Windrose

Detailed Windrose dedicated server setup, config, admin, mods, backups, and troubleshooting guide.

Order / ManageGet Help

Connect & First Checks

Before editing files

  • Use the in-game server list or direct connect with the panel IP and port.
  • Windrose supports self-hosted and dedicated servers. The Steam page lists up to 8 players, with up to 4 recommended for the best performance.
  • Confirm the server password and build/version before inviting players.

Files & Folders

Stop server before edits

DedicatedServer.mdDedicated server instructions included in the dedicated server root folder. Use this as the first reference for the current build.
WorldDescription.jsonWorld/server settings file mentioned by current Windrose patch notes. Use panel fields first when available.
SaveWorkflow.mdDedicated server root-folder document describing save workflow/backups in current builds.
Save data folderWorld/character/server state. Back up before wipes or updates.
Startup variablesSome settings may be generated at launch by panel fields.

Common Settings

High-use values

Server namePublic name.
PasswordPrivate access.
Slots/max playersSteam lists support up to 8 players; 4 is recommended by the developer for optimal performance. Match purchased slots.
WorldDescription.json settingsWorld/server settings. Stop the server and back up before editing.
World/save identityChanging can start a new world.

Admin Setup

Staff access

  • Follow DedicatedServer.md in the server root for the current build-specific admin workflow.
  • Use panel controls when the same setting is exposed there, because startup variables can overwrite manual file edits.
  • Open a support ticket before editing player ownership or save internals.

Mods & Plugins

Install carefully

  • Use only mod functionality supported by the current dedicated server build.
  • Back up save data before adding or removing mods.

Backups, Wipes, Rollbacks

Protect player data

  • Back up WorldDescription.json and save data together before updates or rule changes.
  • Read SaveWorkflow.md in the dedicated server root before manual save moves/restores.
  • Archive saves before wiping instead of deleting permanently.

Troubleshooting

Common tickets

Settings ignoredPanel startup variables may overwrite WorldDescription.json or other manual files.
Players cannot joinPassword, version, port, player cap, or server not fully started.
World changedSave identity/path changed. Restore matching save/config.
Performance issuesReduce player count toward the developer-recommended 4-player range and check server load.