Palworld: Best WorldOption.sav for Dedicated Server FPS

The primary goal for Palworld server optimization is Logical Throughput Stability. When a server’s FPS drops, players experience “rubber-banding” and delayed Pal AI responses. This configuration focuses on aggressive item de-spawning, balancing Pal spawn density, and limiting the “Drop Item Max Num” to ensure the server remains at a stable 60-tick (or the engine-cap) even with multiple players exploring different biomes.

Hardware Compatibility & Expectations

• The RAM Threshold: Palworld dedicated servers are notorious for memory leaks. A minimum of 16GB RAM is recommended for 4–8 players, and 32GB+ for larger communities.
• NVMe SSD: The WorldOption.sav frequently updates the world state. Using an NVMe drive prevents “Disk IO” lag during auto-saves.
• CPU Clock Speed: Palworld’s server logic is mostly single-threaded. Higher per-core clock speeds are more beneficial than high core counts.

File Location

The server settings are stored in a binary .sav file, which is often difficult to edit directly. Most admins edit the PalWorldSettings.ini first, and then use a converter to generate the WorldOption.sav.

[ServerPath]\Pal\Saved\Config\LinuxServer\PalWorldSettings.ini (Or WindowsServer depending on your OS).

Technical Configuration (Code Block)

Modify the following parameters in your PalWorldSettings.ini to maximize server-side FPS before converting to .sav:

[/Script/Pal.PalGameWorldSettings]
# Performance and Stability
# Reduces the number of dropped items to prevent physics lag
DropItemMaxNum=2000              ; Default 3000 (Lower = Higher FPS)
# Shortens the time items stay on the ground
DropItemAliveMaxHours=0.500000   
# Limits how many Pals exist at once
PalSpawnNumRate=1.000000         ; Avoid setting above 1.5 on dedicated servers

# Base Management
# Limits the "Worker Pal" count per base to reduce pathfinding lag
BaseCampWorkerMaxNum=15          ; Lowering to 15 significantly boosts stability
# Faster auto-saves can cause lag spikes; balance accordingly
AutoSaveSpan=600.000000          ; Save every 10 minutes

# Decay and Cleanup
# Higher values clean up abandoned structures faster
BuildObjectDeteriorationDamageRate=1.000000
# Essential for large servers
bEnableNonLoginPenalty=True

Strategy for Dedicated Server FPS

To ensure the smoothest multiplayer experience for your players:

• Item Density Control: The DropItemMaxNum is the silent killer of server FPS. Every dropped item (Stone, Wood, Pal Spheres) requires a physics calculation. Reducing this to 2000 ensures the server doesn’t choke on “Loot Clutter” left by players.
• Pal Work Force: Pathfinding is the most CPU-intensive task in Palworld. While 20 Pals per base is a fun feature, it doubles the AI calculation load compared to 10 or 15. Limiting BaseCampWorkerMaxNum to 15 is the sweet spot for performance vs. automation.
• The WorldOption.sav Converter: Because the game often ignores the .ini file on dedicated servers, you must use a Python script (like the Palworld-Save-Tools) to inject these settings into the WorldOption.sav. This ensures the server “hard-reads” your performance tweaks on boot.

Key Performance Parameters

Parameter	Recommended Value	Impact
DropItemMaxNum	2000	Reduces the “Physics Buffer” load on the CPU.
PalSpawnNumRate	1.0	Prevents over-populating the world with AI actors.
BaseCampWorkerMaxNum	15	Cuts down on pathfinding “stuck” loops.
DropItemAliveMaxHours	0.5	Cleans the world of trash loot more frequently.

Frequently Asked Questions (FAQ)

Conclusion and Expected Results

By manually refining your WorldOption.sav to prioritize efficient item cleanup and limited AI pathfinding, you are maximizing the Tick Rate of your Palworld Dedicated Server. You can expect less player rubber-banding, faster-acting Pal AI, and a significantly more stable environment for long-term survival play.