palworld

Start the server with default settings

$ [path/to/PalServer.sh]

$ [path/to/PalServer.sh] -port=[8211] -players=[1..32]

$ [path/to/PalServer.sh] -publiclobby

$ [path/to/PalServer.sh] -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS

$ [path/to/PalServer.sh] -publicip=[ip_address] -publicport=[port]

./PalServer.sh [options]
./PalServer [options]

-port=XXXX
    Specifies the UDP port for game client connections. Default is usually 8211.

-queryport=XXXX
    Sets the UDP port for server list queries and status information. Default is often 8212.

-players=Y
    Defines the maximum number of players allowed on the server simultaneously.
The game's server configuration file (PalWorldSettings.ini) also contains this setting.

-RCONPort=XXXX
    Configures the TCP port for Remote Console (RCON) administration. Used for remote server management commands.

-RCONEnabled=true|false
    Enables or disables RCON functionality for server administration.

-log
    Enables detailed logging output from the server, often useful for debugging.

-useperfthreads
    Optimizes server performance by utilizing performance-oriented threads, potentially improving stability and responsiveness.

-NoAsyncLoadingThread
    Disables asynchronous loading threads, which can sometimes resolve specific loading or stability issues, though it might impact initial load times.

-UseHostNetSpeed
    Instructs the server to use the host machine's network speed settings, which can be relevant for network performance tuning.

-EpicApp=PalServer
    A parameter often used internally by the server's launch scripts to identify the application.

The term "palworld linux command" typically refers to running the Palworld Dedicated Server application on a Linux operating system, rather than a standalone Linux utility named "palworld".

Palworld is a popular open-world survival crafting game known for its creature collection and base-building elements. To host a game for multiple players, a dedicated server is often deployed. On Linux, this server application is usually installed via SteamCMD and invoked through a shell script (e.g., PalServer.sh) or directly via its executable (PalServer). This allows users to host their own persistent game worlds independent of a client application, providing a stable and customizable environment for gameplay.

The "palworld" command does not exist as a standard Linux utility. This analysis refers to the Palworld Dedicated Server executable and its arguments. Running the server requires significant system resources (CPU, RAM, disk I/O), and performance can vary based on the number of players and in-game activities. Server configuration is primarily managed through PalWorldSettings.ini and DefaultPalWorldSettings.ini files, with command-line arguments often overriding or supplementing these settings. Ensure proper port forwarding is configured on your network for external access.

The Palworld Dedicated Server is typically installed on Linux using SteamCMD.
First, install SteamCMD itself. Then, log in anonymously and use the command app_update 2394010 validate to download the Palworld server files.

For persistent and robust operation, it's common practice to run the Palworld server as a systemd service. This allows for automatic startup on boot, easy management (start, stop, restart), and logging directly through the system's journal (journalctl).

While some settings can be passed via command-line arguments, the primary configuration for the Palworld server resides in PalWorldSettings.ini (and DefaultPalWorldSettings.ini for defaults) located in the Pal/Saved/Config/LinuxServer/ directory within the server installation path. These files control game rules, server name, password, rates, and more.

Palworld, developed by Pocketpair, was released in early access in January 2024. Following its highly successful launch, the demand for dedicated servers surged. The Linux dedicated server application was made available to facilitate self-hosting, allowing players and communities to run their own persistent Palworld instances. Its development history is tied directly to the game's rapid growth and the community's need for stable, customizable multiplayer environments beyond official servers.

steamcmd(1), screen(1), tmux(1), systemctl(1), htop(1)