Palworld

Server settings, admin access and what to expect from a game still in early access.

Everything in Your panel applies to Palworld. These are the parts specific to it.

Startup parameters

The essentials are in Startup parameters rather than a config file:

• Server Name and Server Description — what players see in the browser
• Server Password — leave empty for an open server
• Admin Password — separate from the player password, used for admin commands
• Max Players — the slot count
• Enable RCON — turn on if you want to manage the server with an external tool

Change a value, save, restart. Nothing applies until the next boot.

Game rules

Everything else — experience rate, capture rate, Pal spawn density, damage multipliers, day length, base and guild limits, PvP — lives in the server settings file, which you edit in the file manager. A restart applies it.

There are a lot of options. Change a few at a time and keep a note of what you altered; some combinations interact in ways the game does not warn you about.

Admin commands

Log in as admin in-game using the admin password, then use the game's own commands for kicks, bans and server management. The console in the panel is available too, and is where you go if the game itself is unresponsive.

Memory

Palworld is demanding. Plans start at 8 GB and that is a genuine minimum rather than a comfortable one — a populated server with several bases wants more.

Memory use grows with the number of players, the number of Pals in bases and how much has been built. A server that runs fine with three friends may struggle with ten on the same plan.

Early access, in practice

Palworld is still in development, and that has consequences worth planning for:

Updates arrive often and can change save behaviour. Take a backup before applying one.

Modding is unofficial and moves fast. You have full file access, so anything the community tooling supports you can install — but treat mods as experimental and back up first. A game patch can break them without warning.

Performance varies between builds. If a server that was fine becomes unstable right after an update, it may genuinely be the update rather than your configuration.

Moving an existing save

Upload your save folder through the file manager or SFTP and restart. Stop the server before uploading, and back up whatever is already there first — restoring over a running world is how people lose two saves instead of one.