SteamAPI Initialization Issue During Server Startup about palworld-server-docker

[MoryCorp]

Can confirm the server works very well even with this message :

Increasing per-process limit of core file size to infinity.
- Existing per-process limit (soft=18446744073709551615, hard=18446744073709551615) is enough for us (need only 18446744073709551615)
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.

Been playing with friends for 24 hours and going

[SORAPSYGA]

I have noticed that despite this error, the game can still connect normally. However, there is no change in the container logs. I am currently testing it. Thank you very much for creating the Docker image.

I've encountered the same error, however it seems to still run the server as normal. Are you still able to join and play on the server?

[thijsvanloef]

I've encountered the same error, however it seems to still run the server as normal. Are you still able to join and play on the server?

[thijsvanloef]

I think (could be mistaken) that the fact there is no server output is a limitation that the Palworld devs need to find a fix for.

[zbellerose]

I can confirm the server is working fine even with those errors.

[thijsvanloef]

I'll still keep this issue open for visibility, however I do not believe this is something I can fix

[thijsvanloef]

I've added this to the known issues page on the GitHub Wiki,
https://github.com/thijsvanloef/palworld-server-docker/wiki/Known-Issues