Palworld 1.0.3 Server Update: New Setting and Dedicated Server Fixes

Palworld 1.0.3 arrived on August 12, 2026. Most of the patch is balance work for the World Tree and late-game production, but three lines matter directly to dedicated server owners: there is a new world setting and two dedicated-server bugs have been fixed.

Run an updated Palworld 1.0 server

The dedicated-server changes in Palworld 1.0.3

• A new enemy-camp setting. bAllowEnemyCampSpawnNearBaseCamp lets an owner allow hostile camps to appear near player bases instead of suppressing them in that area.
• Tower Boss Fast Travel fix. Fast Travel could activate unintentionally during Tower Boss battles on a dedicated server. That server-only bug is fixed in 1.0.3.
• Vibrating Pals fix. Pals on a dedicated server could appear to vibrate rapidly on a connected player's screen. The patch fixes that client-side presentation problem.

The wider patch also makes crude-oil extractors cheaper and faster, lowers several late-game technology costs, and increases access to World Tree Holy Water. Those are not server configuration changes, but they immediately affect the economy of a persistent world once the server and players are on 1.0.3.

What the new enemy-camp setting actually controls

The new option is separate from bEnableInvaderEnemy, the existing base raid switch. Turning raids off stops raid events. Turning bAllowEnemyCampSpawnNearBaseCamp on allows ordinary hostile camps to spawn close to a player base. One setting does not replace the other.

Leave the new option off if your group wants the area around a Palbox to remain a safer building zone. Turn it on if established bases have made nearby exploration too quiet and the group wants hostile camps closer to home.

How to update a self-hosted Palworld server safely

1. Tell connected players about the restart and use Palworld's /Save command.
2. Stop PalServer cleanly. Do not copy or update a world while the process may still be writing it.
3. Copy Pal/Saved somewhere outside the server installation. Palworld's rotating backups help, but an offline copy protects you from a failed update too.
4. Run SteamCMD with app_update 2394010 validate.
5. Start the server, confirm it finishes loading, then have one player verify the world, character, guild, bases and Palbox before everyone rejoins.

Update the server and clients together. If Steam has already moved the players to 1.0.3 while the dedicated server is still on an older build, the version mismatch can keep them out even though the process itself looks healthy.

How GHosting handles Palworld 1.0.3

The server Overview tab can compare the installed Steam build with the current one. Use Force update to validate the Palworld files and restart while preserving the world and settings. The Settings tab now includes Enemy camps near player bases. It is off by default, which preserves the earlier camp-suppression behavior until an owner deliberately enables it.

Save the setting, then restart the game server to apply it. It is written as bAllowEnemyCampSpawnNearBaseCamp while the rest of PalWorldSettings.ini, including values edited by hand, stays intact.

Should a dedicated server update now?

Yes, after taking the normal save backup. Pocketpair's notes do not announce a world-format migration, and the dedicated-server fixes are useful even if your group does not want the new camp option. The brief restart is preferable to leaving clients and the server on different builds.

Read Pocketpair's official Palworld 1.0.3 patch notes and the current server-setting reference for the upstream details. For a fresh install, use our complete Palworld 1.0 dedicated-server guide. If you are moving an existing save at the same time, follow the Palworld world-transfer checklist before replacing any files.