The primary goal for Palworld server optimization is Entity and AI Management. Every dropped item on the ground and every pathing calculation for a base worker consumes CPU cycles and RAM. By reducing the “trash” on the map and disabling high-stress events like raids (invaders), you can significantly extend the time between required server restarts.
Hardware Compatibility & Expectations
- RAM is King: Palworld dedicated servers have a persistent memory leak. Even with a perfect config, a server with 16GB RAM will eventually crash if not restarted every 6–12 hours.
- Linux vs. Windows: Performance is significantly more stable on Linux (Ubuntu/Debian). If you are hosting on Windows, expect about 20% more overhead.
- The “Worker” Bottleneck: Each Pal working at a base is a pathing agent. If you have 4 bases with 15 Pals each, that is 60 agents the server must track in real-time.
File Locations
- PalWorldSettings.ini:
\Pal\Saved\Config\LinuxServer\PalWorldSettings.ini(orWindowsServer) - Engine.ini:
\Pal\Saved\Config\LinuxServer\Engine.ini
Best PalWorldSettings.ini for Lag Reduction
Open your PalWorldSettings.ini. Ensure all settings are inside the OptionSettings=(...) parentheses.
; Recommended settings for high-performance dedicated servers
bEnableInvaderEnemy=False, ; DISABLING RAIDS IS THE #1 LAG FIX
DropItemMaxNum=500, ; Default is 3000; reducing this saves massive RAM
DropItemAliveMaxHours=0.5, ; Items disappear faster, clearing clutter
PalSpawnNumRate=0.8, ; Slightly reducing wild spawns improves server FPS
BaseCampWorkerMaxNum=10, ; Reducing base workers from 15 to 10 prevents AI "jitter"
bIsUseBackupSaveData=True ; Keeps your data safe during the inevitable OOM crashEssential Engine.ini Tweaks (Network Fix)
The default Palworld tick rate is often too low for high-speed combat. Add this to your Engine.ini to fix “teleporting” Pals:
[/Script/OnlineSubsystemUtils.IpNetDriver]
NetServerMaxTickRate=60 ; Forces the server to communicate 60 times per second
MaxClientRate=100000
MaxInternetClientRate=100000
[/Script/Engine.Engine]
bUseFixedFrameRate=True
FixedFrameRate=60.000000Pro Tip: Disabling
bEnableInvaderEnemy(Raids) isn’t just about difficulty. When a raid triggers, the server spawns 10–20 high-level AI agents with complex pathing and physics. On a busy server, this is usually what triggers the “Connection Timed Out” error for other players.
Key Parameters Explained
| Parameter | Recommended Value | Impact |
| bEnableInvaderEnemy | False | Stops AI raid spawns, the primary cause of sudden server lag spikes. |
| DropItemMaxNum | 500 | Limits the amount of wood/stone/loot on the ground. Prevents memory bloat. |
| NetServerMaxTickRate | 60 | Fixes “rubberbanding” by increasing the frequency of server-to-client updates. |
| BaseCampWorkerMaxNum | 10 | Reduces the number of active AI pathing agents per base. |
Automation: The “Restart” Strategy
Since Palworld cannot currently fix its own memory leak, the best “config” is a scheduled task:
- Restart Interval: Every 4 to 6 hours for servers with 10+ players.
- Launch Flags: Use
-USEALLAVAILABLECORESin your startup script to ensure the server isn’t artificially limited to a single CPU core.
Troubleshooting & Common Fixes
- Server Stuck on Startup: This usually means you have a syntax error in your
PalWorldSettings.ini(like a missing comma). Delete the file and let the server regenerate a fresh one. - High Ping/Desync: This is often the
NetServerMaxTickRatebeing too high for your bandwidth. If players lag at 60, try lowering it to 30. - Pals Standing Still: This is a symptom of “Server FPS” dropping below 20. Check your CPU usage; if it’s at 100%, you must lower the
PalSpawnNumRate.
Frequently Asked Questions (FAQ)
Does decreasing “PalSpawnNumRate” make the world feel empty?
At 0.8, the world still feels full. You will only notice fewer groups of 4-5 Pals, which is a small price to pay for a lag-free experience.
Can I use these settings on a local co-op game?
Yes, but the host’s PC will still act as the server. If the host has a weak CPU, these settings are even more important.
Why is Linux better for hosting?
Linux handles memory allocation and “Garbage Collection” much more efficiently than Windows for Unreal Engine 4 titles, meaning the memory leak takes longer to reach critical levels.
Conclusion and Expected Results
By manually refining your PalWorldSettings.ini and Engine.ini, you are addressing the core simulation bottlenecks of the game. You can expect the elimination of most rubberbanding, a much longer server uptime between crashes, and a significantly more responsive combat experience against bosses.