Valheim: Public Test & Version Switching

Iron Gate Studio frequently releases "Public Test" builds for upcoming biomes (like Ashlands or Deep North). Running these allows you to see content early, but it comes with risks.

How to Switch Server Version

Option A: Using the One-Click Switcher

1. Go to the **Update / Switch Version** tab in your Supercraft Panel.
2. Select **Public Test** (or `default-beta`) from the dropdown.
3. Click **Apply & Restart**.
4. Wait 2-5 minutes for SteamCMD to download the new files.

Option B: Manual SteamCMD

If you are self-hosting, you need to add the `-beta` flag to your update script:

app_update 896660 -beta "public-test" -betapassword "yesimadebackups" validate

Reverting to an Older Version

Sometimes, a new update breaks all your mods (BepInEx errors). You might want to stay on the "Previous Stable" version.

1. Select **default_old** or **previous_stable** in the version switcher.
2. Note: Valheim does not keep a long history of old versions. Usually, only the immediately preceding version is available.

Client-Side Instructions (For Players)

Your players must match your server. Tell them to:

1. Right-Click Valheim in Steam Library -> Properties.
2. Go to **Betas**.
3. Enter code: yesimadebackups.
4. Select `public-test` from the dropdown.
5. Allow Steam to update.

Test the future. Host your Valheim server with Supercraft and easily toggle between Live and Public Test branches to try the Ashlands update today.

Troubleshooting Version Issues

Connection Errors After Version Change

• Symptom: Players cannot connect after switching versions.
• Cause: Client and server version mismatch.
• Solution:
  1. Verify all players have switched to the same branch (Public Test or Stable).
  2. Check Steam is fully updated on all client machines.
  3. Restart both server and client applications.
  4. Clear Steam download cache: Steam -> Settings -> Downloads -> Clear Download Cache.

"Update Failed" Error

• Symptom: Version switch fails with update error.
• Cause: SteamCMD network issues or corrupted files.
• Solution:
  1. Stop the server completely.
  2. Delete app_update_info_896660.txt in the server directory.
  3. Delete the steamapps folder to force fresh download.
  4. Attempt version switch again.
  5. If issues persist, contact support for manual intervention.

World Corruption on Version Switch

• Symptom: World won't load after changing versions.
• Cause: Newer version incompatible with old world format.
• Solution:
  1. Immediate: Restore from backup before version switch.
  2. If No Backup: Try using .old files (see our Restore Backup guide).
  3. Last Resort: Try using Valheim's built-in "previous_stable" branch.
  4. Warning: Never switch to newer version without backup first.

Mods Not Working on New Version

• Symptom: Server crashes or mods don't load after version change.
• Cause: Mods not compatible with new game version.
• Solution:
  1. Check mod pages for updates supporting the new version.
  2. Update BepInEx to the latest version first.
  3. Disable all mods, test vanilla, then enable one-by-one.
  4. Use Thunderstore to check for mod compatibility lists.
  5. Consider staying on older version until mods are updated.

Slow or Failed Downloads

• Symptom: Version switch takes very long or hangs.
• Cause: SteamCMD bandwidth throttling or server issues.
• Solution:
  1. Be patient - full downloads can take 10-30 minutes depending on version.
  2. Check server bandwidth usage during download.
  3. Try switching during off-peak hours.
  4. If download fails, retry the version switch process.

"Branch Not Available" Error

• Symptom: Requested branch not found in dropdown.
• Cause: Beta branch temporarily unavailable or removed.
• Solution:
  1. Check official Valheim Discord or Steam updates for branch status.
  2. Some beta branches are only available during specific testing periods.
  3. Use default-beta for experimental features if available.
  4. Contact support to verify branch availability on our servers.

Password Issues After Version Switch

• Symptom: Password not working after changing versions.
• Cause: Server config reset or password policy changes.
• Solution:
  1. Check server settings in your control panel.
  2. Reset server password to a new value.
  3. Ensure password meets minimum requirements (5 characters).
  4. Restart server after changing password.

Best Practices for Version Management

Before Switching

• Always Backup: Create a full backup before any version change.
• Notify Players: Inform your community about planned version changes.
• Check Mod Compatibility: Research if your mods support the target version.
• Schedule Downtime: Plan for 15-30 minutes of server unavailability.
• Document Current State: Note which mods and configurations you're running.

During Version Switch

• Monitor Progress: Watch the update logs for errors or issues.
• Patience: Don't interrupt the download process.
• Test Thoroughly: After switch, test all major features before inviting players back.
• Verify Mods: Confirm mods are loading correctly.
• Check Player Access: Have at least one player test connection.

After Version Switch

• Monitor Stability: Watch server performance for the first few hours.
• Collect Feedback: Ask players about any issues they encounter.
• Update Documentation: Note any new features or changed mechanics.
• Prepare Rollback: Keep backups accessible in case of major issues.

When to Switch Versions

• New Content: Switch to Public Test for early access to new biomes.
• Bug Testing: Help developers test fixes on beta branches.
• Mod Issues: Switch to previous_stable if mods break on update.
• Stability Focus: Stay on stable branch for production servers.
• Tournament Events: Keep consistent versions for competitive play.