therave39

Perfect! Just wanted to confirm. Thanks again! For anyone else looking to add a User Script for server restarts, here's what I threw together: #!/bin/bash SERVER_IP=127.0.0.1 RCON_PORT=25575 RCON_PASS=password rconCmd () { command rcon -a $SERVER_IP:$RCON_PORT -p $RCON_PASS "$@" } if rconCmd info | grep "Welcome to Pal Server" >/dev/null then echo "Palworld is running" rconCmd "broadcast Server_will_restart_in_5_minutes" >/dev/null sleep 60 rconCmd "broadcast Server_will_restart_in_4_minutes" >/dev/null sleep 60 rconCmd "broadcast Server_will_restart_in_3_minutes" >/dev/null sleep 60 rconCmd "broadcast Server_will_restart_in_2_minutes" >/dev/null sleep 60 rconCmd "broadcast Server_will_restart_in_60_seconds" >/dev/null sleep 30 rconCmd "broadcast Server_will_restart_in_30_seconds" >/dev/null sleep 5 rconCmd "broadcast Server_will_restart_in_25_seconds" >/dev/null sleep 5 rconCmd "broadcast Server_will_restart_in_20_seconds" >/dev/null sleep 5 rconCmd "broadcast Server_will_restart_in_15_seconds" >/dev/null sleep 5 rconCmd "broadcast Server_will_restart_in_10_seconds" >/dev/null sleep 5 rconCmd save >/dev/null rconCmd "shutdown 5 Server_will_restart_in_5_seconds._Get_the_fuck_out" >/dev/null else echo "Palworld not running" fi This assumes you have ich777's RCON plugin installed (and RCON enabled on your server, obviously). It's extra verbose with the warnings/broadcasts, so you can adjust to your liking. Any feedback is greatly appreciated!

Quick question about the automated backups: does this process restart the server?

You're a legend, thanks a ton! I definitely missed this post.

Unrelated to the actual Docker image, but for anyone running a Palworld server: restart/backup your server often. Palworld seems to have some brutal memory leaks, and on two separate occasions over the weekend my Palworld server crashed due to OOM (it was using 25+ GB) and corrupted my gameworld. Both times I've had to start from scratch, which sucks. Here's a quick and dirty user script to back up your entire `Saved` folder (configs and world saves) #!/bin/bash BACKUP_DIR=/mnt/user/documents/palworld-backups BACKUP_NAME=backup-$(date -d "today" "+%Y%m%d%H%M") if docker ps | grep Palworld >/dev/null then docker stop Palworld >/dev/null && echo "Palworld stopped" cp -rp /mnt/user/appdata/palworld/Pal/Saved $BACKUP_DIR/$BACKUP_NAME && echo "Palworld saves backed up to ${BACKUP_DIR}/${BACKUP_NAME}" docker start Palworld >/dev/null && echo "Palworld restarted" else echo "Palworld not running" fi Any feedback is greatly appreciated!

The in-game Community Server browser is... kinda awful. The search functionality only filters through the pages of servers that you've loaded up (it only loads 200 servers per request). Even if you keep loading new pages of servers, theres no guarantee yours will ever show up. If you go the direct/passwordless route, anybody you have using your server will still see it in the Recent Servers section. Until they fix the password issue with direct connections, I'll likely keep my server out of the Community Server list.

I see the same thing in my logs, despite it working correctly. Are you able to connect to the server over LAN? You might need to remove "EpicApp=PalServer" from the game parameters and remove the password from PalWorldSettings.ini to connect directly

I think I ended up sorting this out. I just removed the container/image, removed the steamcmd/palworld directories from my appdata, and started from scratch. The steamclient.so is now found in the expected directory (when checking via the container's console). One thing I noticed/changed was the default container settings have /serverdata/serverfiles defaulting to /mnt/cache/appdata/palworld, which might have also caused some issues since I don't have my appdata on the cache. I'm not seeing any new errors that haven't been deemed expected, so I think this is working.

Ah my apologies, I never saw a corresponding "[S_API] SteamAPI_Init(): Loaded '/serverdata/.steam/sdk64/steamclient.so' OK." log so I wasn't sure if it successfully found the file at an alternate location. My /serverdata/.steam/sdk64/ directory is totally empty. I'm running Unraid 6.12.6

You're a legend! I noticed I'm getting the following errors in the logs: dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory dlopen failed trying to load: /serverdata/.steam/sdk64/steamclient.so with error: /serverdata/.steam/sdk64/steamclient.so: cannot open shared object file: No such file or directory [S_API] SteamAPI_Init(): Sys_LoadModule failed to load: /serverdata/.steam/sdk64/steamclient.so At a quick glance, it looks like the steamclient.so file exists at /serverdata/serverfiles/steamclient.so Is this an error on my end, or can that be safely ignored?