If you've played on a Palworld dedicated server before, you know crashes seem to be part of the game. However, they don't have to be. With the right settings and maintenance routines, you can significantly reduce server crashes and improve overall performance. If you're looking for a hosting provider, check out our guide to Palworld server hosting.
This guide will help you identify common issues we've encountered while assisting other server owners and provide solutions to keep your Palworld server running smoothly.
OOM Errors: Running Out of RAM
One of the most common reasons for server crashes is running out of RAM, resulting in Out of Memory (OOM) errors. Ensuring your server has enough RAM allocated is crucial. Monitor your server's memory usage and upgrade if necessary. We suggest your server has a MINIMUM of 16GB of RAM. If you're playing with 10+ active players, you will need at least 32GB of RAM.
Disabling Invader Enemies
One significant factor contributing to server instability in Palworld is the presence of invader enemies. These enemies can create a substantial load on your server, especially if their numbers grow unchecked. Disabling the "Enable Invader Enemies" setting can help improve server performance and reduce crashes.
-
Stop your server and navigate to /Pal/Saved/Config/WindowsServer/PalWorldSettings.ini
-
Locate the
bEnableInvaderEnemy
setting and set it toFalse
. -
Start your server.
This simple change can reduce the strain on your server and help prevent crashes. If your server is still not showing up in the community list, you might want to check our guide on Palworld server not showing in community server list.
Build Object Deterioration Damage Rate
The BuildObjectDeteriorationDamageRate
setting is crucial for maintaining server stability in Palworld. This setting controls the rate at which built objects deteriorate and are cleaned up by the server. If this setting is set to 0, the server cannot clean up entities properly, leading to a buildup of unused objects that can cause server crashes.
-
Stop your server and navigate to /Pal/Saved/Config/WindowsServer/PalWorldSettings.ini
-
Find the
BuildObjectDeteriorationDamageRate
setting. -
Ensure it is set to a value greater than 0.
-
Start your server.
This setting helps manage and clean up entities, preventing server overload.
Auto-Reset for Inactive Player Bases
Over time, players may leave the game or take extended breaks, leaving their bases behind. These inactive bases consume server resources, occupying memory (RAM) and processing power that could be better utilized for active players.
To clean up inactive player bases, set bAutoResetGuildNoOnlinePlayers
to False
. Be mindful of the time specified under AutoResetGuildTimeNoOnlinePlayers
:
-
Stop your server and navigate to /Pal/Saved/Config/WindowsServer/PalWorldSettings.ini
-
Set
bAutoResetGuildNoOnlinePlayers
toFalse
. -
Check and adjust
AutoResetGuildTimeNoOnlinePlayers
as needed. -
Start your server.
This setting ensures that inactive bases are cleaned up, which can help maintain server performance.
Keeping Mods Updated
Always ensure that any mods you're using are up-to-date with the latest versions. Mod developers frequently release updates to fix bugs, improve compatibility with the latest game patches, and add new features. By regularly checking for updates and applying them, you can avoid compatibility issues that arise from using outdated mods. Keeping your mods current ensures they work seamlessly with the current version of the game.
It's also worthwhile checking the comments section of any mod to see if there are other users experiencing crashes like you.
Leave Engine.ini Default
It's tempting to tweak the Engine.ini
file based on fixes shared on Reddit and Discord, but these often cause more harm than good. While community-driven suggestions can sometimes provide quick fixes, they can also introduce unforeseen issues and conflicts. Many of these "fixes" are not thoroughly tested and can lead to instability, crashes, or even degrade server performance over time.
Keeping your Engine.ini
file at its default settings is the best practice to maintain server stability. The default configuration is designed by the developers to provide a balanced performance across different hardware setups. It ensures compatibility and stability, minimizing the risk of crashes and performance issues.
Schedule Regular Restarts
Regularly restarting your Palworld server can help prevent crashes. Schedule restarts during off-peak hours to minimize disruption:
-
Decide on a regular restart schedule, we suggest at least once per day at least.
-
Inform your community about the restart schedule so they don't think the server is crashing.
-
Implement automated restarts using server management tools.
Regular restarts help clear memory and refresh server processes, contributing to overall stability.
By following these guidelines, you can significantly reduce the likelihood of your Palworld dedicated server crashing, ensuring a smoother and more enjoyable experience for your players.
Have you done all the above, but your Palworld server is still crashing? Come and join our Discord and brainstorm with other members on what can be done to fix your server.