Editing and applying WorldOption.sav

Know what each file is for

1. Identify the active world before editing

SaveGames directories are created after the server has run. If you operate multiple worlds, do not guess from folder names: compare modification times and backup records.

Back up the complete WorldID directory, not only WorldOption.sav. Keeping the related save files together gives you a reliable recovery point.

• Ask players to disconnect and stop the server process.
• Copy files only after shutdown is complete.
• Label the backup with date, server, and purpose.
• Keep the original untouched and edit a copy.

2. Locate WorldOption.sav

The usual relative path is Pal/Saved/SaveGames/<ServerID>/<WorldID>/WorldOption.sav. The root depends on Steam, SteamCMD, Docker, or your hosting panel.

If it is missing, run and cleanly stop the server once. On managed hosting, check the active-world selection and backup slots. SaveForge cannot connect to your host; you must download the file from the active world.

3. Change a small set of values at a time

After upload, confirm the filename and compare decoded values with what you expect from the current server. Start with clearly understood settings and leave unknown properties unchanged.

Do not assume every larger multiplier is beneficial. Yield rates, depletion rates, and respawn intervals describe different directions. Zero, negative, or extreme values may be rejected or behave differently across versions.

• Progression: adjust ExpRate and PalCaptureRate conservatively.
• Performance: spawn, worker, building, and dropped-item limits can increase load.
• Security: use distinct strong values for AdminPassword and ServerPassword.
• Operations: enable RCON or REST API only when required and protect exposed ports.

4. Replace the file while the server is stopped

Confirm the download is named WorldOption.sav. Preserve the existing file as WorldOption.sav.before-edit or move it into the backup, then place the edited file in the same directory.

A running server can write its in-memory settings during shutdown. Replace the file only after a complete stop, then inspect startup logs for save-loading errors.

5. Verify connection, admin access, then each change

First join normally, test admin authentication, and check edited options one by one. If a value did not apply, confirm the active WorldID, host control-panel precedence, and whether another configuration source regenerated the file.

If startup fails or reports a save error, stop immediately and restore the pre-edit file. After recovery, retry with one or two changes so the cause remains identifiable.

Frequently asked questions