Windrose Updated April 27, 2026

Updating Your Windrose Server

Update Windrose server files using SteamCMD through the panel, and handle post-update steps safely.

WindroseupdateSteamCMD

Overview

Windrose server updates are delivered through Steam. The Pterodactyl egg handles updates via SteamCMD using AppID 4129620. Updates should be applied carefully — always back up your world data before updating in case the new version introduces breaking changes to save formats or configuration files.

Automatic Updates

If the AUTO_UPDATE startup variable is set to true, the server will run SteamCMD to check for and apply updates each time it starts. This is convenient but means a restart can trigger a lengthy update download unexpectedly. For production servers, consider setting AUTO_UPDATE = false and managing updates manually to control timing.

Manual Update Process

  1. Back up your world. Before any update, back up the world folder and ServerDescription.json. See the backup article for procedure.

  2. Stop the server from the panel console. Wait for a clean shutdown so world state is written to disk.

  3. Trigger the update. In WISP or Pterodactyl, use the Reinstall button or run the update command from the console if your egg supports an update-only trigger. Alternatively, set AUTO_UPDATE = true, restart once to pull the update, then set it back to false.

  4. Wait for SteamCMD to complete. SteamCMD will validate existing files and download only changed content. Watch the console output for the completion message.

  5. Verify configuration files. After an update, check that ServerDescription.json is intact. Game updates do not normally overwrite this file, but verify it has not been reset. If the egg reinstall process was used, this file may have been reset to defaults.

  6. Check mod compatibility. If you have UE4SS or WindrosePlus installed, check the mod's GitHub page to confirm it is compatible with the new game version. A game update may require a corresponding mod update.

  7. Start the server and check R5.log for any errors introduced by the update.

SteamCMD AppID Reference

The dedicated server AppID is:

4129620

This is different from the Windrose game client AppID (3041230). Ensure the egg and any manual SteamCMD commands reference the correct AppID.

Post-Update Mod Checks

After a game update:

  1. Check R5/Binaries/Win64/ue4ss/UE4SS.log for mod load errors.
  2. If WindrosePlus fails to load, check for an updated release at https://github.com/humangenome/WindrosePlus.
  3. If a mod is incompatible, disable it (remove enabled.txt) before starting the server to avoid crashes.

Handling Save Format Changes

Occasionally a game update may change the world save format. If the server fails to load your world after an update:

  1. Check R5.log for save format or version mismatch errors.
  2. If a migration is required, the game may handle it automatically on first load. Allow the server time to process before assuming it has crashed.
  3. If the world becomes corrupt after an update, restore from your pre-update backup.

Rollback

SteamCMD does not natively support rollback to previous game versions outside of using Steam beta branches. If a specific version is available as a Steam beta, you can target it in the egg configuration. Otherwise, protect yourself with good pre-update backups.

Back to Knowledgebase
Need help? Submit a Ticket →