[1.1.94] factorio binary looks for steam_appid.txt in working directory only

[sparr]

I have steam_appid.txt in the same directory as my factorio binary, which is sufficient to get the factorio modding toolkit vscode extension working. However, when I run the binary directly, I still get the behavior where it relaunches the game. If I change my working directory to where the binary is, it doesn't do that. I think it should look in the directory where the binary is located, even when run from somewhere else.

Code: Select all

% ls ~/.steam/steam/steamapps/common/Factorio/bin/x64/               
factorio  steam_appid.txt
% ~/.steam/steam/steamapps/common/Factorio/bin/x64/factorio       
   0.000 Initializing Steam API.
steam.sh[854726]: Running Steam on manjarolinux 23.0.2 64-bit
steam.sh[854726]: STEAM_RUNTIME is enabled automatically
setup.sh[854797]: Steam runtime environment up-to-date!
steam.sh[854726]: Steam client's requirements are satisfied
   0.000 Steam requires game restart, restarting...
%

Code: Select all

% cd ~/.steam/steam/steamapps/common/Factorio/bin/x64         
% ./factorio 
   0.000 Initializing Steam API.
[S_API] SteamAPI_Init(): Loaded '/home/sparr/.local/share/Steam/linux64/steamclient.so' OK.
Setting breakpad minidump AppID = 427520
SteamInternal_SetMinidumpSteamID:  Caching Steam ID:  76561197970260632 [API loaded no]
   0.000 2023-11-02 11:43:34; Factorio 1.1.94 (build 61774, linux64, steam)
   0.010 Operating system: Linux (ManjaroLinux 23.0.2)
   ...

[sparr]

Per https://partner.steamgames.com/doc/sdk/ ... amAPI_Init this may be a Steam problem.

[quyxkh]

Just use the website version, it doesn't daemonize itself, it gets you real console access, you can script it for benchmarking la la.

[Genhis]

Thanks for the report. Based on Steam API documentation, this is not a bug. You may find the DRM-free binary useful for mod development; you can download it from our website.