GuidesConfiguration
ConfigurationLaunch-required workflow

Set up your Windrose dedicated server

Use Windrose’s official ServerDescription.json and per-world WorldDescription.json files to control server access and world rules without editing generated identity values.

Generate the official configuration files

Windrose creates default ServerDescription.json and WorldDescription.json files after the dedicated server is started and stopped cleanly. ServerDescription.json contains server-wide settings; each world has its own WorldDescription.json.

Configure server identity and access

  1. Set a clear ServerName for the crew.
  2. Use a valid InviteCode of at least six supported characters if your workflow uses an invite code.
  3. If a password is configured, keep the password-protection flag consistent with it.
  4. Do not edit PersistentServerId; it is generated server identity data.
  5. Keep provider-managed networking unchanged unless the Runic panel exposes a validated setting.

World settings and save migration

  1. Back up the current server and world files before changing a live world.
  2. Stop the server before replacing save data or editing file-level world settings.
  3. Apply world-specific changes in the matching WorldDescription.json rather than mixing them into the server-wide file.
  4. Start the server and verify the expected world, invite/password behavior and console output.
KEEP READING

Related guides