Palworld: Server Limits for Bases, Buildings and Sync
Contents
- BaseCampMaxNum: the overall cap on bases per server
- BaseCampMaxNumInGuild: how many bases your guild gets
- BaseCampWorkerMaxNum: pals per base
- MaxBuildingLimitNum: the per-player building cap
- PhysicsActiveDropItemMaxNum: loot on the ground
- ServerReplicatePawnCullDistance: how far the server shows pals
- ItemContainerForceMarkDirtyInterval: chests in co-op
Palworld’s dedicated server load settings sit in one place, the Performances section of the configuration page in Pocketpair’s official documentation, the Japanese studio listed as both developer and publisher on the game’s Steam page. There are seven of them, and each limits something different: the number of bases, pals per base, buildings per player, items left on the ground, or the sync distance.
The setting names are in English, and you enter them into the server configuration file exactly as written, letter for letter. That file is described on the same configuration page; its path depends on how the server was installed, so it won’t be quoted from memory here, check the documentation. The whole page covers the dedicated server: it’s titled “Palworld Server Guide” and has a version switcher, current at the time this list was compiled at version 1.0.3 (what the update brought is a separate topic). The documentation doesn’t cover single-player here.
| Setting | What it limits | Numbers in the documentation |
|---|---|---|
| BaseCampMaxNum | all bases on the server combined | not stated |
| BaseCampMaxNumInGuild | bases belonging to one guild | 4 by default, maximum 10 |
| BaseCampWorkerMaxNum | pals on one base | maximum 50 |
| MaxBuildingLimitNum | buildings per player | 0 means no limit |
| PhysicsActiveDropItemMaxNum | dropped items with physics | not stated |
| ServerReplicatePawnCullDistance | sync distance of pals from the player, in centimetres | minimum 5000, maximum 15000 |
| ItemContainerForceMarkDirtyInterval | how often an open chest force-syncs, in seconds | not stated |
BaseCampMaxNum: the overall cap on bases per server
The official description is short: the total number of bases across the whole server. It’s the sum of everything every guild has placed together, not a limit for any single one of them.
Players only notice this setting once the server is already full. Once the overall cap is reached, a new base won’t go up even for someone whose guild still has a free slot. You click, nothing happens, and the reason isn’t obvious from the interface, so it’s worth warning server admins about this limit ahead of time.
The documentation gives no default value, no upper bound, and no note on processing impact for this setting. Pocketpair places a load warning next to two of the other rows, but not this one.
BaseCampMaxNumInGuild: how many bases your guild gets
The numbers here are stated: 4 by default, 10 at maximum. Right next to them is a direct warning that raising the value increases processing load.
In the game this is very literal. At four, your guild spreads across four spots, say a main base, a quarry, a farm, and a staging post near an interesting biome. Need a fifth, and the game simply won’t let you place the base box; the only way around it is tearing down one of the existing ones. Raise it to ten, and the guild can keep a separate base for each production line, barely hauling resources by hand across half the map.
For a co-op group of several people in one guild, four slots run out fast, since everyone wants their own corner. A small group on a home server benefits most from raising the cap, because the extra load is split among a few people rather than a crowd. For where to put each of these bases and what to build there, see the guide on base building.
BaseCampWorkerMaxNum: pals per base
The maximum the documentation states is 50 pals per base. The same warning applies: a higher value means more processing.
This setting decides how packed your production line gets. Too few workers, and there’s a queue at the workbenches, ore sits unprocessed, and you end up finishing the job by hand. Plenty of workers, and production keeps running while you’re off on a raid. There’s a flip side that has nothing to do with the number itself: the more pals work at one spot, the more the server has to recalculate their routes and tasks every tick.
It’s more useful here to look at quality than quantity. One pal with the right passive skills does more work than three random ones, without adding to the server’s load. The documentation gives only the ceiling, not a default value.
MaxBuildingLimitNum: the per-player building cap
The description: a limit on the number of buildings per player, with zero meaning no limit.
Players run into this limit at one specific moment: the next wall, staircase, or foundation won’t place even though the materials are there. For someone who builds compactly, the limit stays invisible for the whole playthrough. For someone putting up a multi-storey fortress with a perimeter fence, it turns into a wall in the middle of the project.
Zero removes the cap entirely, which suits a home server among a few friends where nobody crowds anyone else out. A public server with random players is better off with an actual limit, since one perfectionist builder creates load for everyone. The documentation names neither a default nor a maximum, so the admin picks the value.
PhysicsActiveDropItemMaxNum: loot on the ground
The official description: the maximum number of dropped items allowed to behave according to physics.
The situation where this shows up is a Palworld standard: after a fight or clearing out a stockpile, a pile of items is scattered on the ground. Each one can roll, fall off a ledge, or bounce, and each of those behaviours costs computation. The setting decides how many items get to do this at once.
What happens to items beyond the limit isn’t described, and the documentation gives no numbers for this row. Before touching it, it helps to know how your server generally handles load under pressure, which is covered separately in the system requirements.
ServerReplicatePawnCullDistance: how far the server shows pals
The sync distance of pals from the player, in centimetres. The boundaries are stated directly: minimum 5000, maximum 15000.
Anything beyond that distance isn’t synced to you by the server. At the minimum, pals only appear and start acting once you’ve walked up close, so a slope looks empty from afar, and a fight happening there only becomes visible once you’re right on top of it. At the maximum, you see noticeably further, which helps when you’re hunting a specific creature and want to spot it before it spots you. For anyone tracking a rare pal like Jetragon, a longer distance buys more time to prepare.
The server pays for it: a longer distance means more creatures whose state has to stay synced for every player at once. The documentation gives the range but not a default value.
ItemContainerForceMarkDirtyInterval: chests in co-op
This setting decides how often the server force-refreshes a chest’s contents while its window is open. The unit is seconds.
The problem it solves only comes up with other people in the game. Two players stand by the same stockpile: one is loading in coal while the other is pulling items out at the same time. If the second player’s window doesn’t refresh, they see stale contents and reach for something that’s already gone. A more frequent forced resync keeps the other player’s window fresher; a less frequent one cuts down on the background updates the server sends to clients.
For someone playing solo on their own server, this row changes almost nothing, since only one person ever opens the chest anyway. For a group clearing out a shared stockpile before a raid, the difference is noticeable. The documentation gives no concrete values or behaviour for zero, so it has to be tuned on your own server. If you’re just setting up a world for friends, start with the basics of getting a world running and come back to load settings once the group actually grows.

Frequently asked questions
Where do you enter these settings?
In the dedicated server's configuration file, described on the configuration page of Pocketpair's documentation. Check that page for the exact file path, since it depends on how the server was set up.
How many bases can one guild have?
Four by default, ten at most: that's the BaseCampMaxNumInGuild setting. The documentation directly warns that raising this value increases processing load.
How many pals fit on one base?
For BaseCampWorkerMaxNum, the documentation states a maximum of 50. It doesn't give a default value, only a warning that the load grows.
How do you remove the building limit?
Setting MaxBuildingLimitNum to zero means no limit. The limit is counted per player.
Do these settings apply in single-player?
No, the configuration page describes the dedicated server. It says nothing about single-player, so there's no point looking for these lines there.
At what distance does the server sync pals?
That's controlled by ServerReplicatePawnCullDistance, the distance from the player in centimetres, with a minimum of 5000 and a maximum of 15000. The documentation doesn't give a default value.
