#STEAM API INIT FAILED ERROR MESSAGE WINDOWS#

Or remove the link again and try something else. If my advice isn't working you could try linking without the '-s'. (If you want to use relative paths instead you would probably need to cd to the exact same directory that the executable is when it is started and then create a relative link from there.) steam.exe -applaunch 70 -dev -console -sw +svlan 1 +map MyMap hl.exe -game cstrike -dev -console -fullscreen +svlan 1. Command-line batch script files launching these applications.

#STEAM API INIT FAILED ERROR MESSAGE WINDOWS#

', not 'ln -s steamcmd/linux32/steamclient.so. Windows shortcuts pointing to steam.exe with the proper -applaunch specified (see Steam section below).

'ln -s /home//steamcmd/linux32/steamclient.so. Make sure you use absolute paths for the source file when you are linking. I suspect he failed at creating the right link and made it refer to itself, i.e. Steam client modifies the steamappid.txt file incorrectly. The last person I gave this advice to got a different error message though about 'Too many levels of symbolic links'. Known issue: If you start the server without Steam running youll get following log message: 'SAPI FAIL SteamAPIInit() failed SteamAPIIsSteamRunning() failed.' This is OK since running Steam is not necessary for Dedicated servers. You can't really break something serious short term if you make the library findable in a few more places. Maybe ~/.steam/sdk32/ as target works too, maybe try that too. I know that /usr/lib/ is definitely looked into for libraries, so you might try that. Essentially 7D2D just needs to find the lib, so linking to anywhere it looks for libs should be fine The steamclient.so in your 7d2d directory or the one in steamcmd/linux32/ (if there is one) should be ones you can use AFAIK.

Steam api init failed error message