The fastest way to a well-tuned Palworld server: pick one of the four presets below, paste it into PalWorldSettings.ini as a single line, and restart. Casual for relaxed co-op, Balanced to keep vanilla feel with less grind, Hardcore for permadeath, PvP for the official 1.0 player-versus-player mode. Real key names, real defaults, and the reasons your edits sometimes don't stick.
Where is PalWorldSettings.ini and how is it formatted?
On a Linux dedicated server the file lives at:
Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
Every option sits inside one long OptionSettings=(...) line under a section header. That one-line rule is non-negotiable — a newline in the middle silently voids the parse:
[/Script/Pal.PalGameWorldSettings] OptionSettings=(Difficulty=None,DayTimeSpeedRate=1.000000,NightTimeSpeedRate=1.000000,ExpRate=1.000000,PalCaptureRate=1.000000,PalSpawnNumRate=1.000000,DeathPenalty=All,bEnableInvaderEnemy=True,ServerPlayerMaxNum=32)
Two things people forget: set Difficulty=None so your individual rate settings actually take effect (a named difficulty overrides them), and raise ServerPlayerMaxNum from its default of 4 to 32.
What do the main PalWorldSettings.ini keys do?
The settings worth touching, with exact key names and defaults:
| Key | Default | What it does |
|---|---|---|
Difficulty | None | Use None so the rates below apply; Casual/Normal/Hard override them |
ExpRate | 1.0 | XP multiplier. 1.5–3.0 is the usual "less grind" range |
PalCaptureRate | 1.0 | Catch-chance multiplier (max 2.0) |
PalSpawnNumRate | 1.0 | How many Pals spawn — raising this raises server load |
DayTimeSpeedRate / NightTimeSpeedRate | 1.0 | Higher = shorter days/nights |
WorkSpeedRate | 1.0 | Base-work speed |
DeathPenalty | All | None / Item / ItemAndEquipment / All |
bEnableInvaderEnemy | True | Base-raid invaders. Set False to roughly halve the memory-leak growth rate |
bIsPvP | False | Turns on the official PvP mode |
bEnablePlayerToPlayerDamage | False | Direct player-vs-player damage |
PalEggDefaultHatchingTime | 72.0 | Huge-egg hatch time in hours (0 = instant) |
GuildPlayerMaxNum | 20 | Max players per guild (up to 100) |
BaseCampWorkerMaxNum | 15 | Working Pals per base — higher = more load (max 50) |
ServerPlayerMaxNum | 4 | Player cap — set to 32 |
bEnableInvaderEnemy and PalSpawnNumRate | — | The two settings with the biggest performance cost |
Full parameter reference: Palworld official docs and the community wiki.
What's the best config for casual co-op?
Relaxed progression, no punishing death, keep the world lively. Paste this as your OptionSettings line:
OptionSettings=(Difficulty=None,ExpRate=2.000000,PalCaptureRate=1.500000,PalSpawnNumRate=1.000000,WorkSpeedRate=1.500000,DeathPenalty=None,PalEggDefaultHatchingTime=24.000000,bEnableInvaderEnemy=True,bIsPvP=False,bEnablePlayerToPlayerDamage=False,ServerPlayerMaxNum=32)
Double XP, easier catches, faster base work, and you drop nothing on death — the setup most friend groups actually want.
What's the best balanced config?
Close to vanilla, but with the grind sanded off and the leak slowed. A good default for a public-ish community server:
OptionSettings=(Difficulty=None,ExpRate=1.500000,PalCaptureRate=1.000000,PalSpawnNumRate=1.000000,WorkSpeedRate=1.000000,DeathPenalty=Item,PalEggDefaultHatchingTime=48.000000,bEnableInvaderEnemy=False,bIsPvP=False,ServerPlayerMaxNum=32)
Note bEnableInvaderEnemy=False — on a long-running community server, halving the memory-leak growth is worth more than the raid events for most groups. Drop-items-only on death keeps stakes without the misery of losing gear.
What's the best hardcore config?
Hard difficulty with real consequences — permadeath and losing your party Pals:
OptionSettings=(Difficulty=Hard,ExpRate=1.000000,PalCaptureRate=1.000000,PalSpawnNumRate=1.000000,DeathPenalty=All,bHardcore=True,bPalLost=True,bEnableInvaderEnemy=True,bIsPvP=False,ServerPlayerMaxNum=32)
bHardcore=True makes player death permanent; bPalLost=True means the Pals in your party are gone too. Only run this if your group has agreed to it.
What's the best PvP config?
For 1.0's official PvP mode with guild raids:
OptionSettings=(Difficulty=Normal,ExpRate=1.500000,DeathPenalty=Item,PalEggDefaultHatchingTime=24.000000,bIsPvP=True,bEnablePlayerToPlayerDamage=True,bEnableDefenseOtherGuildPlayer=True,bEnableInvaderEnemy=True,ServerPlayerMaxNum=32)
bIsPvP plus bEnablePlayerToPlayerDamage turns players hostile; bEnableDefenseOtherGuildPlayer lets guilds raid each other's bases. Faster egg hatching keeps the combat roster fresh.
Why won't my Palworld server settings save?
If your edits keep reverting, it's almost always one of these — and the config guides that skip them are why people go in circles. Full checklist in why Palworld server settings won't save, but the short version:
- Stop the server before editing. A running server rewrites the file on shutdown and wipes your changes.
- Edit
PalWorldSettings.ini, notDefaultPalWorldSettings.ini. The default file is a template; the game copies from it. - Keep everything on one line. A newline inside
OptionSettings=(...)voids the parse. - Set
Difficulty=Noneor a named difficulty silently overrides your rate settings. - On a migrated world, delete
WorldOption.sav— while present it overrides the ini completely.
On our panel none of this can bite you: you set values in the UI and the parser writes a valid file on restart. If you'd rather configure with sliders than a text file, our Palworld hosting does exactly that, with the same four presets built in.
Frequently Asked Questions
What is the best ExpRate for a Palworld server?
For a group that wants to see content without grinding, 1.5x to 3x is the sweet spot. 2x is the most common choice. Anything above ~5x trivialises early progression. Set Difficulty=None first, or your ExpRate won't apply.
Do PalWorldSettings.ini changes need a restart?
Yes. Stop the server, edit the file, then start it. Editing while the server runs means your changes get overwritten when it next shuts down.
Does PalSpawnNumRate affect server performance?
Yes — it's one of the two heaviest settings (with BaseCampWorkerMaxNum). More spawned Pals means more AI the server tracks. Keep it at 1.0 unless you have RAM and CPU headroom to spare.
How do I reduce lag from settings alone?
Set bEnableInvaderEnemy=False (roughly halves memory-leak growth), keep PalSpawnNumRate and BaseCampWorkerMaxNum near default, and schedule a daily restart. Settings help, but the memory leak is the real cause of creeping lag.
Where do I find all the Palworld settings?
The full list is in the official configuration docs. This guide covers the ones worth changing; the docs list every key without recommended values.
Want presets without the text file? Configure a Palworld server — Casual, Balanced, Hardcore and PvP are one click on our panel, all 32 slots included.


