Dedicated server or co-op game
In co-op, one player hosts the game on their computer: 4 players at most, and the world only exists while the host is playing. A dedicated server runs the world continuously on a separate machine, for up to 32 players who each connect on their own schedule, without waiting for anyone. For a group of friends who do not play at the same times, it is the only way for everyone to progress on their own.
The 32-player limit comes from the game's server: a bigger tier does not raise it, it keeps the game smooth as bases multiply. The dedicated server is published for free on Steam; each player still needs the game.
What slows a Palworld server down
The server keeps bases, their structures and the Pals inside them in memory. Usage climbs over the weeks, and a server that was just enough on the first night ends up stuttering. Two habits:
- plan headroom from the start: our plans start at 16 GB of DDR5, with tiers at 24 and 32 GB, on Ryzen 9 9950X;
- restart regularly at an off-peak hour, after running
/Save and warning your players.
The PalSpawnNumRate setting, which sets how many Pals live in the world, also weighs on performance: raise it with care.
Tuning the game in PalWorldSettings.ini
All settings sit on a single line, OptionSettings=(…), in PalWorldSettings.ini. Miss one parenthesis or comma and the server ignores the whole file. The most used ones: ExpRate for experience, PalCaptureRate for capture, DeathPenalty for what you lose on death, DayTimeSpeedRate and NightTimeSpeedRate for the length of day and night, ServerPassword and AdminPassword for access.
On first launch, this file is empty: you copy in the contents of the DefaultPalWorldSettings.ini template, shipped with the server, then change the values.
With us, you edit it from the client area; changes apply on restart. Announce your rates before launch and stick to them: a community does not take well to rules that change every week.
Renting a Palworld server with DDoS protection
The dedicated server listens on port 8211 over UDP by default. Remote administration goes through the REST API (port 8212 over TCP), the old RCON having been deprecated: neither should be open to the whole internet. In game, /AdminPassword followed by the password unlocks /KickPlayer, /BanPlayer and /Broadcast: choose a long admin password, different from the players' one.
As soon as a server is public, it can be hit by a denial-of-service attack. Anti-DDoS Premium, included with all our Palworld plans, filters traffic before it reaches the server, with a profile tuned to the hosted game. During an ordinary attack, your players stay connected, and you have nothing to configure.
Backups, migration and next steps
The world is stored in Pal/Saved/SaveGames/0/: Level.sav for the world state, and a Players folder for the characters. With us, it is backed up automatically every day, over a rolling 5 days, and restores in one click from the client area. Still, run /Save before every game update.
Coming from a co-op game? Its files can be copied to the dedicated server, but the former host's character must be converted with a community tool. Keep a copy of the original before you try. The guide how to create a Palworld server walks through each step, and the DDoS protection page explains the filtering.