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
- Set a clear ServerName for the crew.
- Use a valid InviteCode of at least six supported characters if your workflow uses an invite code.
- If a password is configured, keep the password-protection flag consistent with it.
- Do not edit PersistentServerId; it is generated server identity data.
- Keep provider-managed networking unchanged unless the Runic panel exposes a validated setting.
World settings and save migration
- Back up the current server and world files before changing a live world.
- Stop the server before replacing save data or editing file-level world settings.
- Apply world-specific changes in the matching WorldDescription.json rather than mixing them into the server-wide file.
- Start the server and verify the expected world, invite/password behavior and console output.