Safe starter settings framework
Begin with the Version 1.0 defaults or a documented copy of them. Pocketpair changed dedicated-server defaults to align more closely with single-player Normal difficulty, so an old configuration should be compared rather than copied blindly.
Define the server's purpose, keep a restorable backup, test privately, and adjust one category at a time. Categories include progression pace, gathering, capture, death behavior, Pal work, bases, raids, PvP or access rules, and multiplayer communication.
The practical effect of any non-default combination needs in-game verification.
Server approach comparison
| Approach | Main priority | Safe starting point | Needs testing |
|---|---|---|---|
| Casual | Low friction and clear group rules | Stay near defaults; review grind only after playing | Death policy, progression feel, and raid pressure |
| Small group | Pacing that matches shared sessions | Conservative load with documented backups | Offline progress, base load, and session cadence |
| Long-term survival | Stability and preserved progression value | Stable rules, scheduled backups, one change at a time | Economy impact, long-session memory, and rollback needs |
Casual server setting approach
- Keep combat and Pal balance close to default so official progression remains recognizable.
- Use clear death and rollback rules that reduce arguments after disconnects or mistakes.
- Review grind-related settings only after the group experiences Version 1.0 crafting and capture balance.
- Enable dedicated-server voice chat only if the group wants it and uses a supported platform.
- Treat any easier or faster profile as a group preference, not an official best configuration. Needs in-game verification.
Small group server approach
For a small group, match progression to actual session frequency rather than copying a public-server preset. A group that plays together weekly has different needs from players who join independently every day.
Keep base and player load conservative until the real world is tested. Version 1.0 includes dedicated-server optimization, but a safe capacity or object limit cannot be inferred from the changelog alone. Needs in-game verification.
Long-term survival server approach
Long-term worlds benefit from stable rules, scheduled backups, documented changes, and a rollback policy. Avoid large progression boosts or sudden difficulty changes that can permanently distort an established economy or invalidate player effort.
Before changing bases, raids, resource availability, Pal work, or death behavior, test the change on a copy and announce it in advance. Keep the pre-change configuration with the backup.
Settings that need testing after 1.0
- Player and base load under the expected concurrent population. Needs in-game verification.
- Experience and capture pacing after the official balance overhaul. Needs in-game verification.
- Gathering and crafting rates with new recipes, ores, tools, and resource distribution. Needs in-game verification.
- Raid pressure after the new wave-based system and scaling behavior. Needs in-game verification.
- Pal work pressure after Work Suitability and base behavior changes. Needs in-game verification.
- Memory use, stuttering, restart frequency, and long-session stability. Needs in-game verification.
Source note
This framework is based on Pocketpair's official Palworld v1.0 Steam changelog, including changed dedicated-server defaults, balance revisions, raid changes, multiplayer updates, and optimization work. Pocketpair does not publish a universal best preset, so this page avoids unsupported exact values and marks real-world recommendations for gameplay testing.