The best Palworld dedicated-server configuration is not a single difficulty preset. Start with Pocketpair’s template, copy it to the active PalWorldSettings.ini, then tune access, progression, survival pressure, combat and death consequences for the people who will actually play. For most small groups, use Difficulty=None as a neutral baseline, set a realistic player cap, restrict platforms if necessary, keep backups enabled with enough disk space, and change only the individual multipliers your group understands.
The important trap is that editing DefaultPalWorldSettings.ini does nothing. The live file is created after the server starts, must be edited while the server is stopped, and must retain one valid OptionSettings=(...) line. The guide below shows where that file lives, how to edit it safely, which controls matter most, and how to choose relaxed, balanced or hardcore settings without relying on an unreliable global difficulty label.
What is the active Palworld server settings file?
A dedicated server reads PalWorldSettings.ini from its platform-specific configuration directory. The directories are generated only after the server has launched at least once.
- Windows:
Pal/Saved/Config/WindowsServer/PalWorldSettings.ini - Linux:
Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
Pocketpair’s official configuration page (version 1.0.4) explicitly warns: “Note that editing DefaultPalWorldSettings.ini will not affect the changes.” The default file is a template. It has to be copied into the active WindowsServer or LinuxServer folder before it can control a world.
The file begins with the section header [/Script/Pal.PalGameWorldSettings] and then uses one OptionSettings=(...) line containing the settings. Text values require quotation marks, and booleans must use the spelling documented for the option. Treat the line as a single configuration record: ForgeWorld reported that inserting a line break inside the parentheses caused settings later in the line to be ignored in its test.
How do I change Palworld server settings safely?
Make changes during a controlled stop/start cycle. This avoids a running process overwriting the file and ensures the server loads the new values at startup.
- Start the dedicated server once. This creates the
Pal/Saved/Config/WindowsServerorPal/Saved/Config/LinuxServerdirectory. - Stop the server cleanly. Do not edit the live file while the process is still running.
- Copy the template. Copy
DefaultPalWorldSettings.iniinto the appropriate active directory and rename or retain it asPalWorldSettings.ini, according to the files generated by your server package. - Edit the copied file. Keep the section header intact and preserve one
OptionSettings=(...)line. Put quotation marks around text and use the documented boolean form for values such asTrueandFalse. - Save a rollback copy. Give the previous working file a dated name outside the active path. A copy lets you recover from a typo without rebuilding the world.
- Start the server again. Settings are read at startup. Changes made while the process is running are not effective until the next start, according to ForgeWorld’s documented observation.
- Verify in game or through server controls. Test one group of related changes at a time, such as access settings first and progression settings second, so a bad result has an obvious cause.
Keep the file’s formatting conservative. A valid header with a malformed or split option line can make later values appear to save while the server silently ignores them.
Why are my Palworld server settings not applying?
Most failures come from editing the wrong file, changing the file while the server is active, or breaking the single-line option record. Check these causes in order before changing values again.
You edited the template instead of the live file
Changes to DefaultPalWorldSettings.ini are not read by the running world. Confirm that your edits are in the WindowsServer or LinuxServer directory and that the filename is PalWorldSettings.ini.
You did not restart after saving
Dedicated-server settings are loaded during startup. Stop the process, save the file, and start it again. A change made in an open file while the server is running will not become active merely because the file was saved.
The OptionSettings record was split or damaged
Keep the entire OptionSettings=(...) expression on one line. ForgeWorld’s October 2026 reference reports that a line break inside the parentheses caused subsequent settings to be ignored in its test. Also check that the section header is spelled exactly and that quotes and parentheses are balanced.
The setting is valid but does not control what you expected
Palworld’s dedicated-server difficulty is assembled from independent controls. A value under Difficulty may not change hunger, damage, stamina or death loss. Test the specific multiplier or penalty that represents the behavior you want rather than assuming a label changes every system.
A build update changed behavior
ForgeWorld checked its defaults against Steam build 25247047 and server version 1.0.5.102999 on October 19, 2026. Its reference listed 122 configuration options on October 22, 2026, but that count can change with game updates. Recheck the current option documentation after an update and validate important settings in a test session.
Which access and administration settings should a small group use?
Set access controls before progression values. A private group needs a realistic slot cap, a join password and a separate administrator password; crossplay and remote-management options should be enabled only when they solve a real need.
| Setting | What it controls | Practical group guidance |
|---|---|---|
ServerPlayerMaxNum |
Maximum simultaneous players | Match the actual group ceiling instead of leaving a large public-style slot count. |
CrossplayPlatforms |
Platforms allowed to connect | Pocketpair lists Steam, Xbox, PS5 and Mac as the default platform set. Narrow it when your group needs a restricted mix. |
ServerPassword |
Password required to join | Use it for a private friends-only world and share it through a trusted channel. |
AdminPassword |
Administrative privileges | Keep it separate from the join password and give it only to people who manage the server. |
RCONEnabled and RCONPort |
Remote console administration | Enable only when you need remote commands or a management tool; secure the port and password. |
RESTAPIEnabled and RESTAPIPort |
HTTP-based administration or automation | Leave disabled for a simple friends-only server unless an automation workflow requires it. |
bIsShowJoinLeftMessage |
Join and leave notifications | Useful for a small group that wants visible awareness of who is online. |
bShowPlayerList |
Whether players can view the player list | Keep enabled when the group values easy social coordination; disable if you prefer less presence information. |
ServerDescription |
Displayed server description | State the group’s rules, time zone or intended play style so guests know what they are joining. |
For a private world, combine the slot cap and password. A password alone does not prevent a larger-than-needed public slot allocation, while a low slot cap does not stop an invited player from sharing the join details.
What are the best Palworld settings for friends?
There is no universal best configuration. Choose the amount of routine, danger and irreversible loss your group will enjoy for a full campaign, then adjust individual controls instead of chasing a preset label.
Relaxed co-op
Use this profile when the group mainly wants building, exploration and creature collection after work or school. Lower survival pressure and lighten death loss, while leaving combat near the normal behavior your players already understand. Keep the player cap tight, use a join password and enable backups so one absent-minded disconnect does not erase a shared evening.
- Reduce hunger pressure and avoid unnecessarily punishing stamina settings.
- Use a lighter
DeathPenaltychoice so a failed expedition does not require a long recovery. - Keep capture, gathering and drop rates close to the group’s preferred pace rather than multiplying every rate.
- Do not raise Pal spawn volume automatically; more spawns can increase server load.
Balanced co-op
Balanced play keeps most rates near their defaults and makes death meaningful without making a mistake campaign-ending. GPORTAL’s illustrative balanced example uses DeathPenalty=Item. That is an example profile, not an official Pocketpair preset.
- Leave ordinary progression and combat close to their starting values.
- Use
DeathPenalty=Itemwhen the group accepts recovering equipment but does not want to lose every carried resource. - Keep hardcore mode and permanent Pal loss off unless everyone explicitly agrees.
- Use backups and document who has the administrator password.
Hardcore co-op
Hardcore is appropriate only when every player accepts that a bad decision can permanently change the campaign. Raise incoming damage or survival pressure deliberately, use DeathPenalty=All, and enable bHardcore=True. Consider bPalLost=True only after discussing permanent Pal losses with the whole group.
bCharacterRecreateInHardcore=Trueallows character recreation after a hardcore death, according to GPORTAL’s settings explanation; decide whether that softens the mode too much for your group.- Keep a written rule for disconnects, crashes and accidental deaths before the first session.
- Use backups for recovery from technical corruption, not as a way to erase an intended in-game death.
These three profiles are editorial combinations of documented controls. Pocketpair does not publish them as official presets.
How does Palworld dedicated-server difficulty actually work?
Dedicated-server difficulty is a bundle of independent settings, not a dependable master slider. Damage, hunger, stamina, experience, capture, gathering, drops, egg time, day/night speed, death loss, hardcore mode and Pal-loss behavior each contribute to the experience.
GPORTAL describes the system as having “no single difficulty slider” because you build difficulty from individual values in PalWorldSettings.ini. iTechGuides reported on October 14, 2026 that the dedicated-server Difficulty key was currently unused or ineffective and recommended changing the individual damage, death-penalty and survival multipliers instead.
Use Difficulty=None as the least misleading baseline unless you are deliberately testing a build-specific preset. If you try an Easy, Normal or Hard label, verify its actual effect on your current server build rather than treating the label as proof that every subsystem changed.
Which progression settings should a group tune first?
Change progression in the order players feel it: experience and capture first, then gathering and drops, followed by egg hatching and time flow. Make a short written decision for each axis so one player’s preferred pace does not quietly dominate the campaign.
Experience and capture
Experience gain determines how quickly characters and Pals reach new power thresholds. Capture settings determine how much effort is required to add a Pal to the team. Raising both can make early progression very fast, so adjust them together and test the first few levels before committing.
Gathering and drops
Gathering multipliers change the labor required for resources, while drop multipliers change the return from defeating or harvesting targets. Increasing both may remove the need for a base production loop; leaving one closer to normal can preserve a reason to explore and build.
Egg hatching
Egg time is a separate progression decision. A group that plays in short sessions may prefer shorter hatching, while a long-running server can keep the wait to make breeding a deliberate project. Change it independently of capture and experience so the campaign still has distinct milestones.
Day and night speed
Day/night speed affects the rhythm of travel, work and combat rather than simply making the game easier. Faster cycles can reduce waiting but may also compress the time available for a planned expedition. Agree on whether the group wants a faster schedule or longer uninterrupted work periods.
How should I tune hunger, stamina and combat damage?
Survival pressure comes from several multipliers, so adjust one pressure at a time and observe a complete play session before stacking changes.
- Hunger: Increasing hunger pressure makes food planning and production more important. Lower pressure suits relaxed co-op; normal or higher pressure gives survival specialists a reason to maintain supply chains.
- Stamina: Stamina changes affect climbing, gliding, swimming and repeated attacks. A severe reduction can make traversal feel punitive even when combat is unchanged.
- Damage: Incoming and outgoing combat damage should be considered separately. Raising incoming damage increases the cost of mistakes; raising outgoing damage shortens fights and can reduce the value of preparation.
- Time flow: Day/night speed interacts with visibility and travel. A combat-heavy group should check nighttime encounters after changing the cycle.
Do not describe a multiplier change as a global difficulty change. It changes the specific system attached to that parameter, which is why the server’s label can remain neutral while the world becomes substantially harsher or easier.
What death penalty should I use on a Palworld server?
Choose the death consequence as a group rule, not as a technical default. The main controls are DeathPenalty, bHardcore, bPalLost and, for hardcore characters, bCharacterRecreateInHardcore.
| Group preference | Relevant controls | What players should expect |
|---|---|---|
| Low-friction exploration | Light death-penalty choice; hardcore and Pal loss disabled | A failed trip costs less time and does not permanently remove a character or Pal. |
| Balanced consequences | DeathPenalty=Item |
Death matters and recovery is required without applying the harshest all-loss rule. |
| Hardcore campaign | DeathPenalty=All; bHardcore=True |
Death is a major campaign event and can permanently alter progression. |
| Permanent Pal risk | bPalLost=True, normally alongside a hardcore agreement |
A death can permanently remove Pals; use only with explicit consent from every player. |
If hardcore characters need a way back after death, bCharacterRecreateInHardcore=True permits character recreation. Decide whether that is a recovery feature or an unacceptable reduction in the mode’s stakes before enabling it.
How do server size and platform settings affect a shared world?
Player count and platform access are operational settings as much as social ones. A server sized for a small group should not advertise a large slot ceiling, and crossplay should reflect the actual devices your friends use.
Pocketpair lists Steam, Xbox, PS5 and Mac in the default CrossplayPlatforms value. Restrict that list when the group needs a controlled platform mix. If a friend cannot connect after a restriction, check the platform list before changing gameplay values.
Keep the slot cap aligned with the group’s real peak attendance. More slots can increase the number of simultaneous players the server must track and can make a private world appear open to people who obtain the password.
What performance settings matter most?
World scale has a direct processing cost. The most important controls for a small group are Pal spawn volume, base limits, worker counts, synchronization distance and backup activity.
| Setting | Effect or documented limit | Trade-off |
|---|---|---|
PalSpawnNumRate |
Changes Pal spawn volume | More simultaneous Pals can affect performance; raise it only when the server has headroom. |
BaseCampMaxNumInGuild |
Controls the guild’s base limit; Pocketpair caps it at 10 | Increasing the limit raises processing load. |
BaseCampWorkerMaxNum |
Controls workers per base; Pocketpair documents a maximum of 50 | More workers increase the amount of activity the server must process. |
ServerReplicatePawnCullDistance |
Controls Pal synchronization distance; documented range is 5,000–15,000 cm | Larger distances can keep more entities synchronized over a wider area. |
bIsUseBackupSaveData |
Creates backup save data | Useful for a shared world, but Pocketpair warns that backups increase disk load. |
Do not raise spawn, base and worker limits simultaneously while diagnosing lag. Change one load-bearing setting, restart, and observe the same activity before making another change.
How do Palworld save backups work?
bIsUseBackupSaveData creates a backup directory for recovery. Pocketpair lists the following schedule:
| Interval | Save data count listed by Pocketpair |
|---|---|
| Every 30 seconds | 5 save data |
| Every 10 minutes | 6 save data |
| Every hour | 12 save data |
| Every day | 7 save data |
These are the documented backup intervals for the setting, not a promise that every hosting environment exposes identical retention behavior. Backups consume storage and increase disk activity, so check available space on a self-hosted machine and watch disk load on a managed server. For a shared campaign, the protection is usually worth enabling; for a disposable test world, you may prefer lower operational overhead.
Should I self-host or use managed hosting for these settings?
Self-hosting gives you direct control of the configuration path, backups and restart schedule. Managed hosting usually adds a control panel and provider-managed process, but the same principles still apply: identify the active PalWorldSettings.ini, stop the server before editing, preserve the header and one option line, and restart before testing.
- Choose self-hosting when you are comfortable managing files, ports, operating-system updates, storage and recovery copies.
- Choose managed hosting when you value a web control panel, provider monitoring or easier restarts more than direct machine access.
- Either way, keep a known-good configuration copy and record who can use administrative controls.
Remote interfaces such as RCON and the REST API are optional management layers, not requirements for changing ordinary world settings. Enabling them adds another access surface, so use them only with a clear administrative purpose.
What should I check after a game or server update?
Configuration names and behavior can change as Palworld updates. Compare your existing file with the current official documentation, confirm that the active path has not changed, and test the settings that matter to your group.
ForgeWorld’s October 2026 reference counted 122 options and tied its defaults to Steam build 25247047 and server version 1.0.5.102999. That is a dated reference, not a permanent number. Keep the date and build beside your saved configuration so you know which version was verified.
- Back up the working
PalWorldSettings.iniand the world save. - Read the current option documentation for renamed, removed or newly added parameters.
- Start the updated server once, then stop it cleanly before applying edits.
- Validate access, one progression behavior, one combat behavior and the death rule in a short test session.
- Tell the group which settings changed before reopening the world.
What is a reliable starting configuration for most friend groups?
Begin with a private, neutral world and make the smallest changes that solve a known group preference.
- Copy the template into the active platform directory and confirm the header and single-line option structure.
- Set
ServerPlayerMaxNumto the expected peak group size, configureServerPasswordand create a separateAdminPassword. - Leave
CrossplayPlatformsbroad only if the group genuinely uses those platforms; otherwise restrict it. - Use
Difficulty=Noneas the baseline while tuning the individual multipliers. - Choose a death rule in advance.
DeathPenalty=Itemis the balanced example documented by GPORTAL; lighter or harsher choices should be an explicit group decision. - Enable backups if the world is important, while checking storage and disk-load impact.
- Keep spawn volume, base limits and worker counts conservative until you know the server’s performance margin.
- Restart, test, and change one category at a time.
This process produces a configuration your group can explain and adjust. It is more dependable than selecting an Easy, Normal or Hard label and assuming every system changed with it.
Frequently Asked Questions
Can I edit PalWorldSettings.ini while players are online?
You can open the file, but the dedicated server will not apply those changes during the current process. Schedule a clean stop, save the file, restart, and then verify the behavior before inviting everyone back.
Will changing server settings erase our existing Palworld world?
The documented workflow changes the world options file, not the world save itself. Make a dated copy of both the configuration and save data before experimenting so you can restore the previous state if a syntax error or update causes trouble.
How can I tell whether a platform restriction is blocking a friend?
Compare the player’s platform with the entries in CrossplayPlatforms and temporarily restore the documented broad platform set for a controlled test. If the connection works only then, narrow the list again one platform at a time.
Is enabling RCON required for ordinary configuration changes?
No. RCON and the REST API are optional remote-management controls; normal world tuning still uses the active PalWorldSettings.ini and a restart. Enable a remote interface only when you need automation or administration away from the host machine.
How should we roll back a setting that made the server too difficult?
Stop the server, replace the active file with your dated known-good copy, and start again. Keep a short change log so you can revert one category—such as death loss or combat damage—without discarding unrelated access or progression adjustments.