Palworld server quickstart

Open your Palworld service in the game panel. Allow installation and the first world startup to finish before inviting your group.

1. Choose the basic settings

Stop the server before changing Startup values. Our Palworld configuration exposes Server Name, Server Description, Max Players, Server Password, Admin Password and Auto Update.

Use Server Password for a private group and keep Admin Password separate. The first controls entry; the second grants administrative commands. Follow the field validation shown in the panel. The maximum player setting is a connection limit, not a performance guarantee.

Leave the assigned game port and the managed RCON settings unchanged. RCON is used by this server configuration for console commands and orderly shutdown.

2. Start and join

Press Start and watch Console while the game loads. A running panel status alone does not establish that the world has finished loading.

For clients with direct connection, enter the panel’s public address and game port in the address box below the server list, then connect. Pocketpair explains this in its connection guide. Tell support which platform you play on if your client has a different joining flow.

3. Find the game configuration

After the first start, stop the server and open Files. The Linux settings file is:

Pal/Saved/Config/LinuxServer/PalWorldSettings.ini

Editing DefaultPalWorldSettings.ini alone does not change the active settings. Keep the required configuration structure and change a few values at a time; see Pocketpair’s configuration reference.

Our startup process runs a settings parser and passes core options on launch. Use Startup for fields offered there; a manual edit to the same value may be replaced at startup. If a setting reverts, send us its name rather than repeatedly editing it while the server runs.

4. Save before an update or move

Use the panel’s normal Stop action and wait for shutdown. Download a copy of Pal/Saved/ before replacing a world, changing major settings or updating. Game-managed backup files inside that directory share the server’s storage; keep a separate copy too.

If you use in-game administration, Pocketpair documents /Save and scheduled shutdown in its command reference. Do not share your admin password with players.

For help, open a support ticket with your platform, server name, game version and the error shown when joining. Redact passwords from configuration or log excerpts.