keepcalculator

06 Numbers and Powers

Upload Sons of the Forest World to Server

Card No. 06·12090 · Updated · Standard formula, shown below

Uploading a Sons of the Forest world to your dedicated server lets you continue a single-player or co-op save with friends, or move a world to a more powerful machine. This guide covers the exact steps for both Windows and Linux servers, what files you need, and how to fix common issues.

What You’ll Need

  • Access to your server’s file system (FTP, SFTP, or a file manager in your hosting panel).
  • The save files from your local game (located in %LOCALAPPDATA%\..\LocalLow\Endnight\SonsOfTheForest\Saves on Windows).
  • Your server must have already been started at least once so it creates the necessary folder structure.
  • If your server is on a different platform (e.g., Linux) than your local machine, you may need to convert the save (see Tips).

Step-by-Step

  1. Locate your local save files. On Windows, press Win+R, type %LOCALAPPDATA%\..\LocalLow\Endnight\SonsOfTheForest\Saves, and press Enter. You’ll see folders named by Steam64ID (a long number). Inside, there’s a folder for each save slot (e.g., Slot1, Slot2). Each slot folder contains files like SaveData.json and a GameState folder.
  2. Identify the world you want to upload. Open each slot folder and check the SaveData.json file (or the world name in the game’s load menu) to find the one you want. Note the exact slot number.
  3. Stop your server. Before uploading, shut down the server completely. This prevents file conflicts and ensures the server doesn’t overwrite your upload.
  4. Access your server’s save directory. Connect to your server via FTP or a file manager. The typical path on a Linux server is ~/.config/unity3d/Endnight/SonsOfTheForest/Saves. On Windows servers, it’s usually C:\Users\[user]\AppData\LocalLow\Endnight\SonsOfTheForest\Saves. If you’re using a hosting panel, there may be a dedicated “Save Files” section.
  5. Find the correct slot folder on the server. Inside the server’s Saves folder, you’ll see a folder named after your server’s Steam64ID (or a random number). Inside that, you’ll see Slot1, Slot2, etc. If you’re not sure which slot to use, create a new world on the server first, then note the slot it created.
  6. Upload your local save files. Replace the contents of the server’s slot folder with the contents of your local slot folder. You can upload the entire slot folder (e.g., Slot1) and overwrite, or just the files inside. Make sure SaveData.json and the GameState folder are included.
  7. Set correct permissions (Linux only). If your server runs on Linux, ensure the uploaded files have the same ownership and permissions as the other files in the Saves directory. Usually, chown -R steam:steam /path/to/Saves and chmod -R 755 /path/to/Saves will work, but check your server’s user.
  8. Start your server. Boot up the server. It should load the uploaded world. If it doesn’t, check the server logs for errors.
  9. Verify the upload. Join the server and check that your world is loaded correctly. If you see a new world instead, the save wasn’t read properly.

Common Mistakes

  • Uploading the wrong folder. Make sure you’re uploading the contents of the slot folder, not the Steam64ID folder. The server expects the slot folder to contain SaveData.json directly.
  • Not stopping the server. Uploading while the server is running can cause the server to overwrite your files or crash.
  • Mismatched slot numbers. If you upload to Slot1 but the server expects Slot2, it won’t show up. Always match the slot number.
  • Missing files. If you forget the GameState folder, the save will be incomplete and may not load.
  • Wrong file permissions. On Linux, if the server can’t read the files, it will ignore them. This is a common issue.
  • Using a save from a different game version. If your local game is updated and the server is not (or vice versa), the save may fail to load. Update both to the same version.

Tips

  • Backup your server’s current save. Before replacing anything, copy the existing slot folder to a safe location. This way, if something goes wrong, you can restore it.
  • Use a unique slot. If you’re not sure which slot to use, create a new world on the server, note the slot number, then replace its contents. This avoids overwriting an existing world you might want.
  • Check the server logs. After starting, look for lines like “Loading world” or “Save loaded”. If there’s an error, it will often point to the problem.
  • Convert saves between platforms. If you’re moving from Windows to Linux, you might need to convert the save. Tools like “SOTF Save Converter” can help, but they’re third-party and may not always work. The safest way is to use the same platform.
  • Consider using a dedicated save manager. Some hosting panels have a built-in save manager that simplifies the process. Check your host’s documentation.

Troubleshooting

  • The server starts but shows a new world. This means the server didn’t read your save. Check that the slot folder is correct and contains SaveData.json. Also, verify the server is looking at the right path. Restart the server after uploading.
  • The server crashes on startup. This often happens if the save is corrupted or from a different game version. Try loading the save locally to see if it works. If it does, the issue might be with the server’s configuration or permissions.
  • You get a “Save not found” error. The server can’t find the save in the expected slot. Double-check the folder structure. On Linux, the path is case-sensitive, so make sure it’s exactly Saves and Slot1.
  • Players can’t join or see the world. If the server loads correctly but players can’t join, it might be a network issue, not a save issue. Check your server’s firewall and port forwarding.
  • The world loads but is missing items or progress. This could be due to an incomplete upload. Make sure you uploaded the entire GameState folder. Also, if you used a converter, it might have lost some data.

Frequently Asked Questions

Can I upload a save from a friend’s game?

Yes, as long as you have access to their save files. The process is the same—copy their slot folder to your server.

Do I need to convert the save if my server is on Linux?

Not always, but it’s recommended. Saves are platform-specific due to file paths and serialization. If you upload a Windows save to a Linux server, it might not load. Use a converter tool or start a new world on the server.

Will my dedicated server automatically use the uploaded save?

Yes, if you place it in the correct slot and the server is configured to load that slot. The server loads the save from the slot specified in its configuration (usually Slot1).

Can I upload a save while the server is running?

Technically, you can, but it’s not recommended. The server may overwrite your changes or crash. Always stop the server first.

How do I know which slot to use?

If you’re starting fresh, create a new world on the server and see which slot it creates. Then replace that slot’s contents with your local save. Alternatively, you can rename the slot folder on the server to match your local one.

What if my save is too large to upload via FTP?

Compress the save folder into a ZIP file, upload that, then extract it on the server. Most hosting panels have a file manager that can extract ZIPs.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →