Closed Vauff closed 5 months ago
It does update if you run the install script, so hitting 'reinstall' under settings fixes the server.
But for the future. Would this be solved with a symlink?
But for the future. Would this be solved with a symlink?
Maybe, maybe not - I'll take a look as soon as I can
I've updated the docker image's entry point to ensure the steamclient.so
binaries for sdk32/64 are updated after SteamCMD is done doing whatever it needs to do
I tried using a symlink, but it looks like this doesn't behave as expected - found my servers just failing to find the file at all.
This is now live on the dev Docker images:
I'll push to the main Docker image soon and close this issue when I do. No action should be required for any server using this egg, it should automatically pick up the new Docker image on start. Thanks for the report
Big LIKE!!!
/.steam/sdk64/steamclient.so
seems to never get automatically updated (see modification date).However
/steamcmd/linux64/steamclient.so
does.This has caused issues after todays CS2 update, because Valve seems to now be compiling against a newer
steamclient.so
.Manually copying the updated lib from
/steamcmd/linux64/
to/.steam/sdk64/
can solve the issue in the short term.