⚠️Palworld Feybreak Update Thread

[thijsvanloef]

Hi All!

As you might know, Palworld Feybreak will release on the 23rd of December.

This issue serves as a megathread for all the changes required to ensure compatibility of the Feybreak update with this Docker image.

If you encounter any issues with the Docker container, please report them by commenting on this thread. Include detailed steps to reproduce the issue, relevant logs, and any additional context that could help in diagnosing the problem.

Together, we can ensure a smooth transition for everyone using this Docker setup with the new update. Thank you for your contributions!

1️⃣Breaking Changes:

• Fix Appmanifest Update issues

2️⃣Config Changes:

• Add new config options

3️⃣Miscellaneous Changes:

• none

Known issues

Palworld devs:

[Dedicated Server Player Data Issue]

We are experiencing an issue where player data is not loading correctly on dedicated servers in patch v.04.11.
~~Note: This is a dedicated server issue only. ~~

We have already identified the cause and are preparing to distribute a patch to fix this.
We expect this upcoming patch will resolve this issue.
Your previous character will be reverted after the patch has been applied, even if you make a new character during that time.

~~We apologize for any inconvenience caused and apologize for the delay. ~~
The patch will be released over the next couple of days.

⚠️This was fixed! To update, please restart your server!⚠️

[redjax]

Hey thijsvanloef, thanks so much for this great container! Made it very easy to set up a server for my friends and I :)

I did a docker compose pull, and it did pull some changes, but I see the server version is still Game version is v0.3.12.63518. Is this container already updated?

If so, well done, that would be crazy fast! Otherwise, I'm mostly just commenting here so I can see when the new server container is released and test it out :)

Thanks for your work!

[Printoiid]

Can confirm container has not been updated.

dagothur@dagothur:~/dockercompose/palworld$ sudo docker attach palworld-server
****Checking for new Palworld Server updates****
Current Version: 4799126612816973970
The server is up to date!
****Checking for available container updates****
The container is up to date!
****GENERATING CONFIG****
Using Env vars to create PalWorldSettings.ini
****Compiling PalWorldSettings.ini****
Compiling PalWorldSettings.ini done!
****GENERATING CRONTAB****
BACKUP_ENABLED=true
Adding cronjob for auto backups
time="2024-12-23T03:11:21Z" level=warning msg="process reaping disabled, not pid 1"
Cronjobs started
****Starting Server****
./PalServer.sh -port=8211 -queryport=27015 -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS
The file already exists: /palworld/Pal/Binaries/Linux/steamclient.so
time="2024-12-23T03:11:21Z" level=warning msg="process reaping disabled, not pid 1"
time="2024-12-23T03:11:21Z" level=info msg="read crontab: /home/steam/server/crontab"
Shutdown handler: initalize.
5.1.1-0+++UE5+Release-5.1 1008 0
Disabling core dumps.
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
Setting breakpad minidump AppID = 2394010
[S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.
Game version is v0.3.12.63518

[ikechan8370]

Information from steam api seems to show that linux version is still the old one, while windows version is the latest already.

        "2394011": {
          "config": {
            "osarch": "64",
            "oslist": "windows"
          },
          "manifests": {
            "public": {
              "download": "1623665456",
              "gid": "7474490384694930999",
              "size": "2231375134"
            }
          }
        },
        "2394012": {
          "config": {
            "osarch": "64",
            "oslist": "linux"
          },
          "manifests": {
            "public": {
              "download": "1521801184",
              "gid": "4799126612816973970",
              "size": "1972573925"
            }
          }
        },

So the container always says The server is up to date!. I think we must wait for linux version release.

[Printoiid]

Information from steam api seems to show that linux version is still the old one, while windows version is the latest already.

So the container always says The server is up to date!. I think we must wait for linux version release.

Do we have any idea why this is? Or when things will be updated? Is this dependent on the vendor or Valve?

[Azeuz9]

How to Update to the Newest Server Version

Updating to the newest server in this container is super easy.
The issue occurs because of an appmanifest file.

Steps to Update:

1. Stop Your Server
   Use the following command to shut down all Docker containers:

   docker compose down --rmi all

2. Navigate to Your Server Folder
   The default folder should be named palworld-server-docker (unless you renamed it).

   cd palworld-server-docker

3. Locate the Appmanifest File
   Move into the palworld/steamapps directory:

   cd palworld/steamapps

4. Rename the Appmanifest File
   Rename the file appmanifest_2394010.acf. For example:

   mv appmanifest_2394010.acf oldmanifest.acf

5. Restart Your Server
   Start the Palworld server as usual.

---

🎉 That's it!

Your server should now be up and running on the latest version!

[Printoiid]

Updating to the newest server in this container is super easy. The issue occurs because of an appmanifest file.

That's peculiar... Can confirm it's working here. It's a THICC update.

Success! App '2394010' fully installed.
****Checking for available container updates****
The container is up to date!
****GENERATING CONFIG****
Using Env vars to create PalWorldSettings.ini
****Compiling PalWorldSettings.ini****
Compiling PalWorldSettings.ini done!
****GENERATING CRONTAB****
BACKUP_ENABLED=true
Adding cronjob for auto backups
time="2024-12-23T03:31:09Z" level=warning msg="process reaping disabled, not pid 1"
Cronjobs started
****Starting Server****
./PalServer.sh -port=8211 -queryport=27015 -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS
time="2024-12-23T03:31:09Z" level=warning msg="process reaping disabled, not pid 1"
time="2024-12-23T03:31:09Z" level=info msg="read crontab: /home/steam/server/crontab"
The file already exists: /palworld/Pal/Binaries/Linux/steamclient.so
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
Shutdown handler: initalize.
5.1.1-0+++UE5+Release-5.1 1008 0
Disabling core dumps.
CAppInfoCacheReadFromDiskThread took 3 milliseconds to initialize
Setting breakpad minidump AppID = 2394010
[S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.
Game version is v0.4.11.64554

Thank you for saving the day!

[Akaku-Keninari]

for some reason after getting this update working, I get this sort of logspam

[2024-12-23 06:32:36] [LOG] RCON executed the command. ShowPlayers [2024-12-23 06:32:41] [LOG] RCON executed the command. ShowPlayers [2024-12-23 06:32:46] [LOG] RCON executed the command. ShowPlayers [2024-12-23 06:32:51] [LOG] RCON executed the command. ShowPlayers

[BigFatWizard]

Updating to the newest server in this container is super easy. The issue occurs because of an appmanifest file.

can confirm, worked perfectly fine for me as well. just delete or rename the appmanifest file and the server will download the update normally

for some reason after getting this update working, I get this sort of logspam

[2024-12-23 06:32:36] [LOG] RCON executed the command. ShowPlayers [2024-12-23 06:32:41] [LOG] RCON executed the command. ShowPlayers [2024-12-23 06:32:46] [LOG] RCON executed the command. ShowPlayers [2024-12-23 06:32:51] [LOG] RCON executed the command. ShowPlayers

As far as I remember, my server has been doing this already before the update.

[thijsvanloef]

for some reason after getting this update working, I get this sort of logspam

[2024-12-23 06:32:36] [LOG] RCON executed the command. ShowPlayers [2024-12-23 06:32:41] [LOG] RCON executed the command. ShowPlayers [2024-12-23 06:32:46] [LOG] RCON executed the command. ShowPlayers [2024-12-23 06:32:51] [LOG] RCON executed the command. ShowPlayers

This is normal, this is needed to check if players have joined and send webhooks

[thijsvanloef]

How to Update to the Newest Server Version

Updating to the newest server in this container is super easy. The issue occurs because of an appmanifest file.

Steps to Update:

1. **Stop Your Server**
   Use the following command to shut down all Docker containers:
   ```shell
   docker compose down --rmi all
   ```

2. **Navigate to Your Server Folder**
   The default folder should be named `palworld-server-docker` (unless you renamed it).
   ```shell
   cd palworld-server-docker
   ```

3. **Locate the Appmanifest File**
   Move into the `palworld/steamapps` directory:
   ```shell
   cd palworld/steamapps
   ```

4. **Rename the Appmanifest File**
   Rename the file `appmanifest_2394010.acf`. For example:
   ```shell
   mv appmanifest_2394010.acf oldmanifest.acf
   ```

5. **Restart Your Server**
   Start the Palworld server as usual.

🎉 That's it!

Your server should now be up and running on the latest version!

I am checking why this is necessary

[Azeuz9]

I am checking why this is necessary

Deleting the file won't trigger a re-download if the version is already up to date, so you can safely remove it when the container starts, before executing the rest of the tasks. The file regenerating each time is a minor issue...

It's a quick fix, but it gets the job done 💪