This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
⚠️Palworld Feybreak Update Thread #644
Comments
thijsvanloef
added
the
update
|
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 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! |
|
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 |
|
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 |
Do we have any idea why this is? Or when things will be updated? Is this dependent on the vendor or Valve? |
How to Update to the Newest Server VersionUpdating to the newest server in this container is super easy. Steps to Update:
🎉 That's it!Your server should now be up and running on the latest version! |
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.64554Thank you for saving the day! |
|
for some reason after getting this update working, I get this sort of logspam
|
can confirm, worked perfectly fine for me as well. just delete or rename the appmanifest file and the server will download the update normally
As far as I remember, my server has been doing this already before the update. |
This is normal, this is needed to check if players have joined and send webhooks |
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 💪 |
|
Fixed in #646 Edit: 1.2.0 has been released |
|
Hi, I can not see my issue. |
|
If i run a new save file aka new installations with my docker compose it works. |
|
@FurkanVG They (palworld devs) released a statement on this:
There is sadly nothing I can do about that |
Oh, i see the tweet now. |
|
https://x.com/Palworld_EN/status/1871175835211968776 |
|
Yea i know you can not help me, just wanted to clarify that your report was not helping to this issue. |
|
As FYI, i was able to fix my issue by making a fresh server installation, and migrating my save files. Needed to modify the hash value and that made it boot up then. Dont ask my why this was needed. |
|
Update from 1h 12m ago: |
|
Can someone tell me the correct value for region for the environment variable RANDOMIZER_TYPE? |
|
There is non known yet and in the official documentation, you cant find the value sadly: |
Quick how-toOBLIGATORY USE IT ON YOUR OWN RISK. NO WARRANTY ETC... MAKE BACKUPS!Just tested with Xbox mode server:
Note: I use
Note: For me after connecting to server it showed that beach intro video again. I just skipped it and it continued from where I was left off. |
|
Only issue with the above is that some user related data is actually stored on the client - map exploration, and presumably flags to indicate what tutorials have been shown. On windows, they can be found at Changing to a new save hash will invalidate these files. If you retain the old hash, and simply update |
|
I was able to pull the image again and connect on the newest version of Palworld :) Happy to see all the discussion in this thread, thank you all for looking into this :) |
|
Seems like most of the issues have been resolved, converting this into a thread instead of closing it :) |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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:
2️⃣Config Changes:
3️⃣Miscellaneous Changes:
Known issues
Palworld devs:
The text was updated successfully, but these errors were encountered: