How to Change Guild Size and Base Limits on Your Palworld Server
Adjust guild player limits and the number of bases each guild can own via PalWorldSettings.ini — and learn why Pal worker counts require a different approach entirely.
Guild Player Limit
The maximum number of players allowed in a single guild is controlled by:
GuildPlayerMaxNum=20
Default is 20. You can increase this for larger communities or decrease it to encourage multiple competing guilds on your server. This setting lives in PalWorldSettings.ini, inside the [/Script/Pal.PalGameWorldSettings] section's OptionSettings=() block.
The full settings file is at:
Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
Base Slots Per Guild
Each guild can own a certain number of active bases (camps). The setting is:
BaseCampMaxNumInGuild=4
Default is 4, and the maximum configurable value via this setting is 10. Raising it lets large guilds spread out more; lowering it keeps the server tidier and can help with performance since each active base runs Pal AI workers continuously.
Applying the Changes
Edit PalWorldSettings.ini while the server is stopped, save the file, then start the server. The new limits take effect immediately on startup.
One important note: if a guild is already over the new limit when you lower GuildPlayerMaxNum, existing members are not kicked out. The guild just can't accept new members until it drops below the cap naturally (through players leaving). The game won't force-split oversized guilds.
Pal Workers at a Base — The WorldOption.sav Problem
This is where things get weird. The setting that controls how many Pals can work at a single base is BaseCampWorkerMaxNum. You'll find it listed alongside the other settings in PalWorldSettings.ini, and it looks like it should work the same way.
It doesn't — at least not reliably on dedicated servers.
On many Palworld server versions, BaseCampWorkerMaxNum set in PalWorldSettings.ini is ignored at runtime. The actual value is read from WorldOption.sav instead — a binary save file that takes precedence over the INI for certain settings. If you've bumped BaseCampWorkerMaxNum in the INI and nothing changed, this is why.
To actually change this setting you need to generate and upload a WorldOption.sav file. See How to Use WorldOption.sav to Configure Your Palworld Server for the full process.
Performance Considerations
Higher guild sizes mean the server is tracking more player data together, which can affect memory usage on larger servers. Very high base counts per guild compound this — each base runs its own Pal AI loop. If you're already running close to your RAM ceiling (especially given Palworld's memory leak), be conservative with these numbers.
Recommended starting points for most servers:
GuildPlayerMaxNum=20— fine for most communities, raise to 30–50 for large groupsBaseCampMaxNumInGuild=4— default is reasonable; increase to 6–8 for active builders