Web Analytics Made Easy - Statcounter
Server Tools

Tools / Palworld

Palworld 1.0 Config Migration Doctor

Palworld 1.0 changed the dedicated-server config. Paste your pre-1.0 OptionSettings=(...) line - or your whole PalWorldSettings.ini - and get a 1.0-ready config: new settings added with defaults, renamed keys mapped, dead keys dropped, secrets blanked.

Detected passwords are blanked in the output and stripped before report hashing. Max 100 KB.

What Palworld 1.0 changed for dedicated servers

The 1.0 release (July 2026) reorganised PalWorldSettings.ini. If you carry a config forward from early access, three things happen silently: new settings run on defaults you never chose, renamed keys are ignored, and removed keys sit in the file doing nothing. Highlights the doctor handles for you:

  • New settings: item corruption (ItemCorruptionMultiplier), ranch speed (MonsterFarmActionSpeedRate), PvP kill drops (bAdditionalDropItemWhenPlayerKillingInPvPMode), voice chat, stat-point toggles (bAllowEnhanceStat_*), respawn penalties, modded-client control (bAllowClientMod), and a technology deny list.
  • Renames: AllowConnectPlatform → CrossplayPlatforms (now a parenthesised list), and the community alias EggDefaultHatchingTime maps to PalEggDefaultHatchingTime. DropItemMaxNum carries over to PhysicsActiveDropItemMaxNum.
  • Removed: dead early-access keys like bEnablePlayerToPlayerDamage, bEnableAimAssistPad, bActiveUNKO, bIsMultiplay, Region, and DropItemAliveMaxHours (superseded by item corruption).
  • Defaults worth reviewing: 1.0 ships softer defaults in places (death penalty, world backups, player list) - the doctor flags any you are still running at the old default.

Schema source: the official Palworld server configuration reference (docs.palworldgame.com), server guide version 1.0.0. Entries the reference leaves ambiguous are marked "verify" in the results.

How to install the upgraded config

  1. Stop the Palworld server.
  2. Back up Pal/Saved/Config/LinuxServer/PalWorldSettings.ini (or WindowsServer on Windows).
  3. Replace the OptionSettings=(...) line with the generated 1.0 line, or replace the whole file with the generated ini.
  4. Re-add AdminPassword / ServerPassword locally - the tool blanks them on purpose.
  5. Start the server and check the review list above for any "verify" entries.

FAQ

Does my old PalWorldSettings.ini still work on 1.0?

Mostly, but not cleanly: new settings run on defaults you never chose, renamed keys are ignored, and dead keys clutter the file. The doctor rebuilds the line against the 1.0 schema so nothing is silently ignored.

Is it safe to paste my config here?

Detected passwords are blanked in the generated output and stripped before anything is stored. Best practice is still to redact secrets before pasting and re-add them locally.

Can I paste the whole ini file?

Yes. The parser finds the OptionSettings=(...) line inside a full PalWorldSettings.ini paste (up to 100 KB).

What if I just want safer defaults, not a 1.0 upgrade?

Use the Config Migration Assistant for co-op / performance / public-server targets, or the Settings Generator to build a line from scratch.