Palworld 1.0: A Clean PalWorldSettings.ini File to Start Fresh

The release of Palworld 1.0 marks a major milestone for Pocketpair's survival game. A brand-new region, new gameplay features, improved dedicated server support... but also a few technical hiccups for server administrators who jumped into the update on day one.

Since the official launch, Steam Discussions and Reddit have been filling up with reports of server settings no longer applying correctly, unstable dedicated servers, save-related issues, and configuration files behaving unexpectedly.

A Completely Updated Configuration System

With the arrival of version 1.0, Pocketpair introduced a large number of new options to the PalWorldSettings.ini configuration file.

The downside is that many servers automatically generated configuration files containing dozens of empty parameters, while others continued using files inherited from the Early Access version. As a result, some settings were no longer applied correctly, leading to confusing behavior for server administrators.

Among the issues reported by the community are:

Server settings that appear to be ignored.
Difficulties logging in as an administrator.
Configuration values not being applied despite being present in the file.
Dedicated servers becoming unstable or requiring frequent restarts.

Our Recommendation: Start with a Clean Configuration

Instead of continuing to use an old configuration file that has been updated over multiple game versions, we recommend starting with a clean PalWorldSettings.ini.

That's exactly what we did on our own community server to eliminate any potential compatibility issues between legacy settings and the new options introduced in version 1.0.

Below, you'll find a clean PalWorldSettings.ini file that you can use as a solid starting point. From there, simply customize the values to match your preferred gameplay experience.

Before using this file: replace the placeholder server name and passwords, then back up your current configuration and save files.

[/Script/Pal.PalGameWorldSettings]

OptionSettings=(

ServerPlayerMaxNum=32,

ServerName="XXXXXX",

ServerDescription="XXXXXX",

AdminPassword="XXXXX",

ServerPassword="XXXXXX",

PublicPort=8212,

PublicIP="",

RCONEnabled=True,

RCONPort=25576,

Region="",

bUseAuth=True,

BanListURL="https://api.palworldgame.com/api/banlist.txt",

CrossplayPlatforms=(Steam,Xbox,PS5,Mac),

Difficulty="None",

DayTimeSpeedRate=1.000000,

NightTimeSpeedRate=1.000000,

ExpRate=1.000000,

PalCaptureRate=1.000000,

PalSpawnNumRate=1.000000,

PalDamageRateAttack=1.000000,

PalDamageRateDefense=1.000000,

PlayerDamageRateAttack=1.000000,

PlayerDamageRateDefense=1.000000,

PlayerStomachDecreaceRate=1.000000,

PlayerStaminaDecreaceRate=1.000000,

PlayerAutoHPRegeneRate=1.000000,

PlayerAutoHpRegeneRateInSleep=1.000000,

PalStomachDecreaceRate=1.000000,

PalStaminaDecreaceRate=1.000000,

PalAutoHPRegeneRate=1.000000,

PalAutoHpRegeneRateInSleep=1.000000,

BuildObjectDamageRate=1.000000,

BuildObjectDeteriorationDamageRate=1.000000,

CollectionDropRate=1.000000,

CollectionObjectHpRate=1.000000,

CollectionObjectRespawnSpeedRate=1.000000,

EnemyDropItemRate=1.000000,

DeathPenalty="Item",

bEnablePlayerToPlayerDamage=False,

bEnableFriendlyFire=False,

bEnableInvaderEnemy=True,

bEnableAimAssistPad=True,

bEnableAimAssistKeyboard=False,

DropItemMaxNum=3000,

DropItemMaxNum_UNKO=100,

BaseCampMaxNum=128,

BaseCampWorkerMaxNum=15,

DropItemAliveMaxHours=1.000000,

bAutoResetGuildNoOnlinePlayers=False,

AutoResetGuildTimeNoOnlinePlayers=72.000000,

GuildPlayerMaxNum=20,

PalEggDefaultHatchingTime=72.000000,

WorkSpeedRate=1.000000,

bIsMultiplay=True,

bIsPvP=False,

bCanPickupOtherGuildDeathPenaltyDrop=False,

bEnableNonLoginPenalty=True,

bEnableFastTravel=True,

bIsStartLocationSelectByMap=True,

bExistPlayerAfterLogout=False,

bEnableDefenseOtherGuildPlayer=False,

CoopPlayerMaxNum=4,

BaseCampMaxNumInGuild=4,

ItemWeightRate=1.000000,

EquipmentDurabilityDamageRate=1.000000,

SupplyDropSpan=180

)

A Few Additional Checks Before Troubleshooting

Before assuming your configuration file is the source of the problem, we recommend verifying a few key points:

Make sure your dedicated server has been updated to version 1.0.
Remove any old mods before updating. Pocketpair even recommends uninstalling them completely before launching version 1.0.
Create a brand-new world if you're starting a fresh playthrough.
Always back up your existing save files before making major configuration changes.

Dedicated Servers Still Need a Few Tweaks

The good news is that most servers work perfectly after being configured with a clean configuration file. However, some administrators are still reporting crashes, unexpected disconnections, or instability after several minutes of gameplay.

These issues have been reported across multiple hosting providers as well as on self-hosted servers, suggesting they are not specific to any single platform. Pocketpair will likely release one or more hotfixes for dedicated servers in the coming days.

In the meantime, starting with a clean PalWorldSettings.ini remains one of the simplest and most effective troubleshooting steps before investigating more advanced causes.

Online 24/7

Need a reliable Palworld server?

Deploy your server in just a few minutes and manage your settings through the VeryGames control panel.

Launch my server →