Palworld Known Issues, Workarounds and Fixes

In-game server commands are unavailable without administrator authentication

Server commands require AdminPassword in the configuration and an in-game /AdminPassword login. Pocketpair distinguishes obtaining administrator privileges from simply entering chat. Set up the configured credential before trying an administrative command; being a player connected to the server does not satisfy that requirement. [2]

Documented steps

1. After configuring AdminPassword, press Enter in game and run /AdminPassword with that password to obtain administrator privileges before using the desired server command. [2]

Increasing base and worker limits raises dedicated-server processing load

The official configuration table warns that increasing bases per guild and Pals per base raises processing load. It also identifies PalSpawnNumRate as affecting performance. These settings are part of the workload to review on a custom server; the documentation does not give one supported high-limit configuration that guarantees stable performance on every host. [3]

Dedicated server settings do not change after editing the default file

Pocketpair explicitly says editing DefaultPalWorldSettings.ini does not apply changes to the server. That default is used as the starting configuration; the active PalWorldSettings.ini belongs under the server’s Saved/Config directory. Check the WindowsServer or LinuxServer file described by the official documentation before assuming a parameter is broken. [3]

Documented steps

1. Edit Pal/Saved/Config/WindowsServer/PalWorldSettings.ini on the documented Windows installation, or Pal/Saved/Config/LinuxServer/PalWorldSettings.ini on Linux. [3]