Skip to main content

Known Issues with Palworld

Palworld is an early access game, and as a result has a few bugs that need ironed out. This page has a few of the bugs that WinterNode is aware of, and potential workarounds.

There have been reports of save corruption

We've had reports of save corruption, so it's even more important than normal to take regular and frequent backups of your server. You can take manual backups or create a backup script that incorporates a backup into your regular restarts.

Deleting a player's data

You can find the player save data files in your server's File Manager under the /Pal/Saved/SaveGames/0/<WorldUUID>/Players directory, where <WorldUUID> is a hashed string representing your world. You'll find one .sav file for every player that has joined your world and you can identify which file belongs to the player you're looking for using these steps.

After you've located the corrupted player's data file, you'll need to stop the server and then you can either delete the file or restore the file from your most recent backup.

My server isn't in the server list

There is a known issue with the in-game server list where it's only able to display and search the first 200 servers it's sent. This makes it effectively useless to search the thousands of public servers that are currently live. You'll need to share your server IP with your players for them to use the Direct Connect feature.

You can find your server's IP in the Server List or when Viewing your server.

Server resource usage is high

The predicted server resource usage provided by the developers (Pocketpair) was under the real-world values and has been adjusted since launch as seen here. They've also communicated that memory leaks are expected at this stage, especially for servers running with under 16gb of RAM.
You can try to prevent out of memory crashes by periodically restarting your server using this guide.

Memory leaks

There's been at least one identified memory leak in the spawning of invaders. Your server can be configured using the bEnableInvaderEnemy to disable invader enemy spawning by setting the value to false in your PalWorldSettings.ini file.

File configurations get reset when the server restarts

If you modify the file configuration while the server is online and then restart or stop the server, your file configurations will be reset. The solution to this is to stop the server before you modify any files.

Reach Out!

Have Questions? Need Help? Feel free to reach out!

Join our Discord