When you move save data from a Steam dedicated server to Linux SteamCMD, there’s a common issue where players might lose their data. I’ll explain a potential reason for this problem and provide steps to properly transfer the save data. Please note that this guide is not intended for transferring save data from a cooperative (coop) setup to a dedicated server.
Prerequisites
Before you proceed, make sure you have the following prerequisites in place:
- A Linux server with SteamCMD installed.
- The Palworld dedicated server must be properly installed on your Linux server.
- Ensure that you can successfully launch the server and join it without encountering any issues.
TL;DR
Here are the steps to transfer your save data from a Windows Palworld server to a Linux server with SteamCMD:
- Copy your save folder from
...\SteamLibrary\steamapps\common\PalServer\Pal\Saved\SaveGames\0\{YOUR_SAVE_ID}on Windows. - Paste your save folder at
.steam/SteamApps/common/PalServer/Pal/Saved/SaveGames/0/{YOUR_SAVE_ID}. - Modify
DedicatedServerNamein.steam/SteamApps/common/PalServer/Pal/Saved/Config/LinuxServer/GameUserSettings.inito your{YOUR_SAVE_ID}. - Create a folder
.steam/sdk64using the commandmkdir -p ~/.steam/sdk64. - Copy
.steam/steamcmd/linux64/steamclient.soto.steam/sdk64/steamclient.so. - Modify (or create if not exist) the content of
.steam/SteamApps/common/PalServer/Binaries/LinuxServer/steam_appid.txtto1623730. - Launch the server. If you see something like “Setting breakpad minidump AppID = xxxxxxx” in your server output, everything should be OK.
Cause of the Problem
The main issue lies in the difference in GUID (Globally Unique Identifier) between Linux and Windows platforms when players join a Palworld server. This discrepancy results in the server treating the player as a new one when transitioning between platforms. The root cause may be related to the Steam API and how Palworld generates GUIDs, although the exact mechanism remains speculative.
When a player joins a Palworld server, the server attempts to utilize the Steam API to acquire the player’s ID. Subsequently, it generates a GUID based on this ID. However, if the Steam API is unavailable, the server resorts to generating a GUID using other unidentified rules or values. On Windows, where the server is typically launched from Steam, the Steam API is consistently available and well-configured, leading to GUIDs based on the Steam ID. Conversely, on Linux, the presence of steamclient.so and steam_appid.txt is necessary to enable the Steam API. Without these configurations, the server generates GUIDs based on different, unknown criteria, resulting in disparities from those generated on Windows.
To verify this, you can set the AdminPassword in PalWorldSettings.ini, join a server, type /AdminPassword {YOUR_ADMIN_PWD} in the chat box to become an administrator, then press ESC. Your user ID will be displayed on the screen, revealing that the value differs between Linux and Windows for the same player.
If this guide did not answer your questions in mind, feel free to check our other guide on how to backup and transfer Palworld servers.
That's everything we are sharing today for this Palworld guide. This guide was originally created and written by NucBox. In case we fail to update this guide, you can find the latest update by following this link.
すみません、質問なのですが5番目のコピーはLinux64のファイルに保存なのか
.steamのファイルに保存なのか教えていただけないでしょうか