Skip to content

Game servers

Palworld server settings explained

What every important line in PalWorldSettings.ini does, which values to change first, and how to keep RAM usage under control with scheduled restarts.

A Palworld dedicated server reads almost all of its gameplay rules from one file: PalWorldSettings.ini. That file controls how fast you level, how easy Pals are to catch, what you lose when you die, how long days last, how many bases each guild can build and who gets admin rights. This guide walks through where the file lives, how its unusual one-line format works, the settings worth changing first, and how to keep a server stable when its memory use creeps up over time.

Where the settings file lives

On a Linux dedicated server (which is what most hosts run), the file is here, relative to the server folder:

Pal/Saved/Config/LinuxServer/PalWorldSettings.ini

On a Windows server the folder is WindowsServer instead of LinuxServer. In the root of the server folder you will also find DefaultPalWorldSettings.ini. That file is only a template: the server never reads it, and it is overwritten by updates, so editing it does nothing.

On a fresh install, PalWorldSettings.ini is often empty. When it is, the server uses built-in defaults. To customise anything, copy the full contents of DefaultPalWorldSettings.ini into PalWorldSettings.ini and edit the copy.

How the OptionSettings line works

The file has a section header and one very long line:

[/Script/Pal.PalGameWorldSettings]
OptionSettings=(Difficulty=None,DayTimeSpeedRate=1.000000,NightTimeSpeedRate=1.000000,ExpRate=1.000000,PalCaptureRate=1.000000,DeathPenalty=All,ServerPlayerMaxNum=32,ServerName="My Server",AdminPassword="",ServerPassword="",...)

Everything sits inside the brackets of OptionSettings=( ... ), as Key=Value pairs separated by commas. A few rules save a lot of frustration:

  • Keep it on one line. Do not split the settings across several lines.
  • Watch the commas and brackets. A missing comma, an extra bracket or an unclosed quote usually makes the server ignore the whole line and fall back to defaults, with no clear error.
  • Put text in double quotes. Server name, description and passwords are strings: ServerName="Pal Paradise".
  • Stop the server before you edit. The server can write the file on shutdown, so changes made while it runs may be lost. Stop it, edit, save, then start it again.
  • Copy the exact key names. Some keys contain the game's own spelling mistakes, such as PlayerStomachDecreaceRate. Typing the "correct" spelling creates a key the server does not recognise.

Why your changes might be ignored

If you uploaded a world that was first created in single player or co-op, its save folder may contain a WorldOption.sav file. When that file exists, it overrides PalWorldSettings.ini. Stop the server, back up the save, delete WorldOption.sav from the world's save folder (under Pal/Saved/SaveGames/) and start it again. The ini file then takes effect.

Also note that the Difficulty key does not apply presets on a dedicated server. Leave it at None and set the individual rates instead.

Progression: ExpRate, capture and drops

These are the settings most groups change first, because they decide how much grinding the server asks of its players. All of them are multipliers where 1.000000 is the normal game.

SettingDefaultWhat it does
ExpRate1.0Experience gained by players and Pals. 2.0 doubles it.
PalCaptureRate1.0Chance of a Pal Sphere succeeding. Higher is easier.
PalSpawnNumRate1.0How many wild Pals spawn. Raising it costs CPU and RAM.
EnemyDropItemRate1.0Items dropped by defeated Pals and enemies.
CollectionDropRate1.0Resources from trees, rocks and ore.
CollectionObjectRespawnSpeedRate1.0How quickly gathered resources grow back.
PalEggDefaultHatchingTime72.0Hours for a Huge egg to hatch. Smaller eggs scale from this.
WorkSpeedRate1.0How fast Pals work at a base.

A good starting point for a friend group with limited play time is ExpRate=2.000000, PalCaptureRate=1.500000 and PalEggDefaultHatchingTime=2.000000. Egg hatching time is the setting players thank you for most: the default 72 hours is real time, so with a lower value people can breed Pals within one evening.

Be careful with PalSpawnNumRate. Each extra Pal in the world is simulated by the server, so a value of 2.0 or 3.0 noticeably increases CPU load and memory use, especially with many players spread across the map.

DeathPenalty: what you lose when you die

DeathPenalty takes one of four values:

  • None - you keep everything.
  • Item - you drop the items in your inventory, but keep equipped gear.
  • ItemAndEquipment - you drop inventory items and equipment, but keep your Pals.
  • All - you drop items, equipment and the Pals in your party. This is the default.

Dropped items stay in a box at the spot where you died, so you can go back for them. On a casual server, Item is a popular compromise: dying still hurts, but nobody loses a carefully bred Pal team to a fall. For hardcore or PvP servers, keep All.

Related combat settings are PlayerDamageRateAttack, PlayerDamageRateDefense, PalDamageRateAttack and PalDamageRateDefense. For the defense keys, a higher value means more damage taken, which surprises many admins. bEnablePlayerToPlayerDamage and bEnableFriendlyFire control PvP damage, and bEnableInvaderEnemy turns base raids on or off.

Day and night speed

DayTimeSpeedRate and NightTimeSpeedRate set how quickly time passes. A higher value makes that part of the day go by faster, so it ends sooner. A common tweak is to keep days normal and shorten nights:

DayTimeSpeedRate=1.000000,NightTimeSpeedRate=2.000000

This halves the length of the night while keeping daytime exploration unchanged. A value below 1.0 stretches that phase instead.

Survival needs

  • PlayerStomachDecreaceRate and PalStomachDecreaceRate - how fast players and Pals get hungry. Lower means less food management.
  • PlayerStaminaDecreaceRate and PalStaminaDecreaceRate - stamina drain.
  • PlayerAutoHPRegeneRate and PlayerAutoHpRegeneRateInSleep - health regeneration while awake and asleep.
  • ItemWeightRate - how heavy items are. Lowering it lets players carry more.

Base camps and guilds

Base limits are where server performance and gameplay meet. Every active base is simulated with its Pals working, so these values affect load directly.

SettingDefaultWhat it does
BaseCampMaxNum128Total bases allowed on the whole server.
BaseCampMaxNumInGuild4Bases per guild (maximum 10).
BaseCampWorkerMaxNum15Pals working at each base (maximum 50).
GuildPlayerMaxNum20Players per guild.
BuildObjectDeteriorationDamageRate1.0How fast buildings decay. 0 turns decay off.
DropItemMaxNum3000Dropped items kept in the world at once.

Raising BaseCampWorkerMaxNum to 20 or 30 is popular, but Pal pathfinding at a busy base is one of the heaviest things the server does. If the server starts to lag after a change like this, lower it again before blaming the hardware. Keep DropItemMaxNum at its default or lower: thousands of items on the ground add up.

Server identity, passwords and ports

  • ServerName and ServerDescription - what players see in the server list.
  • ServerPassword - leave empty for a public server, or set one to keep it private.
  • ServerPlayerMaxNum - the player limit. The game supports up to 32.
  • PublicPort - the game port, 8211 by default. On hosted servers the port is assigned to you, so do not change it unless you know the new port is yours.
  • AutoSaveSpan - seconds between automatic saves.
  • bIsUseBackupSaveData - keeps rolling backups of the world. Worth leaving on.

Admin password and admin commands

Set an admin password in the ini file, using something long and unique:

AdminPassword="change-me-to-something-long"

In game, open chat and log in with:

/AdminPassword change-me-to-something-long

You stay an admin until you disconnect. The most useful commands are:

CommandWhat it does
/ShowPlayersLists connected players with their player and Steam IDs.
/KickPlayer {SteamID}Removes a player from the server.
/BanPlayer {SteamID}Bans a player.
/UnBanPlayer {SteamID}Lifts a ban.
/Broadcast {message}Sends a message to everyone.
/SaveSaves the world immediately.
/Shutdown {seconds} {message}Shuts down after a countdown with a warning.
/DoExitStops the server immediately. Save first.
/TeleportToPlayer {SteamID}Teleports you to a player.
/TeleportToMe {SteamID}Teleports a player to you.

Anyone who knows the admin password can kick and ban, so never share it in a Discord channel and change it if a former admin leaves. The same password is used for RCON (RCONEnabled=True, RCONPort) and the REST API (RESTAPIEnabled=True, RESTAPIPort) if you turn those on for bots or dashboards.

RAM usage, memory growth and scheduled restarts

Palworld is a memory-hungry server. A small world with a few players can sit comfortably in a modest amount of RAM, but usage climbs as players explore, build bases and fill them with working Pals. Many servers also see memory grow steadily the longer they run, even when player counts stay the same. Rough guidance:

  • Up to about 8 players with a few bases: plan for 8 GB.
  • Around 8 to 16 players, or higher spawn and worker settings: 12 to 16 GB.
  • Full 32-player servers with many bases: 16 GB or more.

The most reliable fix for slow memory growth is a scheduled restart. A restart every 6 to 12 hours, at a time when few people play, clears the built-up memory and keeps performance steady. Give players a warning first and save before the server stops. A typical sequence is:

  1. /Broadcast Restart_in_5_minutes
  2. /Save
  3. /Shutdown 60 Server_restarting
  4. Start the server again.

Use underscores in broadcast messages, because some server versions cut the message off at the first space when it is sent over RCON. On a hosted server you can set this up as a scheduled task in the control panel instead of doing it by hand.

Other ways to keep memory and CPU in check:

  • Keep PalSpawnNumRate at 1.0 unless you have headroom.
  • Do not set BaseCampWorkerMaxNum and BaseCampMaxNumInGuild both to their maximums.
  • Turn on bAutoResetGuildNoOnlinePlayers with a sensible AutoResetGuildTimeNoOnlinePlayers on public servers, so abandoned guilds and their bases are cleared.
  • Keep the server updated. Patches often include performance and memory fixes.

A sensible casual preset

For a friendly group that wants less grind but still a challenge, these values make a good starting point. Change them inside your existing OptionSettings line rather than replacing the whole line:

ExpRate=2.000000,PalCaptureRate=1.500000,PalEggDefaultHatchingTime=2.000000,
DeathPenalty=Item,NightTimeSpeedRate=2.000000,CollectionDropRate=1.500000,
BaseCampWorkerMaxNum=20,BuildObjectDeteriorationDamageRate=0.000000

(Shown on three lines for readability. In the file, all of it stays on the single OptionSettings line.)

Make one or two changes at a time, restart, and check that they took effect in game. If nothing changed, look for a typo in the line or a leftover WorldOption.sav. Back up PalWorldSettings.ini and your save folder before big changes, and your world will stay safe while you find the settings that suit your group.

Run your own Palworld server

Edit PalWorldSettings.ini from the control panel, with DDoS protection, one-click updates and 24/7 support included.

Starting at $27.21USD/mo