Lag spikes? Lost progress? Can't join after a patch? This is the fix-it list our support crew reaches for. Most of these take under five minutes.
Players can't join after a game update
Steam updated the clients but the server is still on the old version. Update your server and everyone gets back in.
Lag and rubberbanding
Palworld's biggest performance eaters are Pal counts and base complexity:
- Restart regularly. Palworld servers famously accumulate memory over time; a daily scheduled restart keeps things smooth. You can set one up in the panel.
- Lower PalSpawnNumRate slightly in the Server Properties tab if the world is saturated with wild Pals.
- Very large bases with dozens of working Pals hit hard: spreading production across smaller bases helps.
- If the server sits at its RAM limit in the panel graphs, it's genuinely outgrowing the plan: upgrade or trim settings.
Progress lost after a crash or restart
Palworld saves on an interval, not continuously.
- Run
/Save(console or in-game as admin) before every planned restart. - Encourage a
/Saveafter big captures or boss kills. - If progress was lost, restore a backup.
Server crashes on startup after installing mods
Almost always a mod that doesn't support the current game version. Remove the most recently added mod and start again; repeat until it boots. Keep mods updated in lockstep with game patches.
"Password is incorrect" when joining
The server has a Server Password set in the Startup tab. Share it, or clear the value and restart.
World feels wiped after a restart
Usually the server started pointing at a different world folder. Check DedicatedServerName in GameUserSettings.ini matches your world folder in SaveGames/0/. The old world is still there; fixing the name and restarting brings it back.
Still stuck? Submit a ticket and we'll dig into your server directly.
Did this solve it?
If you are still stuck, our team can look at your server directly.