Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I can confirm that the solution for the Linux edition works fine. It's just that you won't be able to find the all the .so equivalents to .dll as in Windows machines.
The files you have to look for: steamclient.so, crashhandler.so, steamconsole.so, libtier0_s.so
1. Launch Steam through steamcmd to make sure all its libraries are up-to-date;
2. Replace all the original .so files belonging to Steam, wherever you can find them in your KF server directory (most of them are under /Binaries/Win64/lib64 AND /linux64) and give them another name (use mv command).
You can use find command (in the root directory of your KF2 server) to quickly locate those files (look up their name above in the post and my reply's first paragraph.)
3. You then symlink the original .so files from steam that are under linux32 and linux64 directories of steam, to where the previous KF .so steam libraries were.
And it worked for me as well.
KF1 server operators have been doing the same thing for years, by that I mean replacing the out of date binaries with up to date ones from Steam CMD .
Fail to do so and you're server will fail to even show up on the server list.
The simplest way I've found to do this is to set up a Cron job to run nightly that simply involves copying the prescribed binaries from the Steam CMD directory and overwriting the ones in the server directory.