1
0
Fork 0
1Panel-Appstore/palworld-server-tool
zhengkunwang c8e42cac65 feat: 应用增加支持的架构信息 (#1973) 2025-05-14 14:21:38 +08:00
..
0.9.9 chore(deps): update jokerwho/palworld-server-tool docker tag to v0.9.9 (#3540) 2025-03-26 13:51:55 +08:00
README.md fix: update Palworld and Palworld Server Tool settings (#2875) 2024-12-31 13:09:39 +08:00
README_en.md fix: update Palworld and Palworld Server Tool settings (#2875) 2024-12-31 13:09:39 +08:00
data.yml feat: 应用增加支持的架构信息 (#1973) 2025-05-14 14:21:38 +08:00
logo.png feat: 优化 palworld server tool 安装包 2024-02-23 16:50:36 +08:00

README_en.md

Palworld Server Management Tool

Manage dedicated Palworld servers with a visual interface and REST API.

Features and Roadmap Based on Level.sav Save File Parsing:

  • Complete player data
  • Player Pal data
  • Guild data

Features Based on Official RCON Commands (Server-Only):

  • Retrieve server information
  • View online player list
  • Kick/ban players
  • In-game broadcasting
  • Smoothly shut down the server with broadcasted messages

This tool uses bbolt single-file storage to periodically fetch and store data from RCON and Level.sav files.

It provides a simple visual interface and REST API, making management and development easier.

When deploying with Docker, you need to configure the external save path for the Palworld server. During installation, you must provide the corresponding external save path for the Palworld server.

Ensure that private server RCON is enabled by following the instructions in the official guide.


Notes on Save File Parsing

Parsing the Level.sav save file temporarily requires a certain amount of system memory (1GB~3GB) for short periods (<20s). The memory is released after the task is completed. Ensure your server has sufficient memory. If not, consider the following alternatives:

  1. Deploy the tool on a separate server.
  2. Use a local personal computer for deployment.
  3. Opt for either of the above when the game server's performance is insufficient.

By default, the PST tool and the game server are assumed to run on the same physical machine. For separate deployments, refer to the following resources: