Updates
AUTO_UPDATE=1 (default) checks Steam on every start. After a Palworld patch, restart from the panel; version mismatch on join means the server has not restarted since the patch.
The memory leak
The Palworld server's memory grows for as long as it runs (a known issue since launch, slower now but not gone). A server that starts at 6 GB can be at 12 GB two days later and get killed. Schedule a daily restart: Schedules → cron 0 5 * * * → task Send command Broadcast Server_restart_in_60_seconds, second task Send command Save with 50 s offset, third task Power action: restart with 60 s offset.
Performance
- Pals in bases are the main tick cost.
BaseCampWorkerMaxNumand the number of bases per guild (BaseCampMaxNumInGuild) cap it. - Dropped items and eggs pile up; the game clears some, a restart clears the rest.
- RAM: when the resource bar sits at the limit, lag is not a settings problem, so upgrade.
- CPU: Palworld likes a fast core; our plans with 2+ cores (200 %+) are the right fit.
Backups
Level.sav is rewritten every 30 seconds by default (AutoSaveSpan in the settings). A panel backup schedule once a night protects you from the rare corrupted save.