gbe_fork/post_build/README.experimental_steamclient.md

What is this ?

This is a build of the experimental version of the emu in steamclient mode, with an included loader which was originally written by Rat431 and later modified to suite the needs of this emu.

The backend .dll/.so of Steam is a library called steamclient, this build will act as a steamclient allowing you to retain the original steam_api(64).dll.
See both the regular and experimental readmes for how to configure it.

---

Note that all emu config files should be put beside the steamclient(64).dll.
You do not need to create a steam_interfaces.txt file for the steamclient version of the emu.

---

How to ue it ?

1. Copy the following files to any folder:
   • steamclient.dll
   • steamclient64.dll
   • ColdClientLoader.ini
   • steamclient_loader.exe
2. Edit ColdClientLoader.ini and specify:
   • AppId: the app ID
   • Exe: the path to the game's executable/launcher, either full path or relative to this loader
   • ExeRunDir: generally this must be set to the folder containing the game's exe, if left empty then it will be automatically set to the folder containing the game's exe.
   • ExeCommandLine additional args to pass to the exe, example: -dx11 -windowed
     Optionally you can specify a different location for steamclient(64).dll:
   • SteamClientDll: path to steamclient.dll, either full path or relative to this loader
   • SteamClientDll: path to steamclient(64).dll, either full path or relative to this loader
   • ForceInjectSteamClient: force inject steamclient(64).dll instead of letting the app load it automatically
   • ResumeByDebugger: setting this to 1 or y or true will prevent the loader from calling ResumeThread() on the main thread after spawning the .exe, and it will display a mesage with the process ID (PID) so you attach your debugger on it.
     Note that you have to resume the main thread from the debugger after attaching, also the entry breakpoint may not be set automatically, but you can do that manually.
   • DllsToInjectFolder: path to a folder containing dlls to force inject into the app upon start,
     the loader will attempt to detect the dll architecture (32 or 64 bit), if it didn't match the architecture of the exe, then it will ignored
   • IgnoreInjectionError: setting this to 1 or y or true will prevent the loader from displaying an error message when a dll injection fails
   • IgnoreLoaderArchDifference: don't display an error message if the architecture of the loader is different from the app.
     this will result in a silent failure if a dll injection didn't succeed.
     both the loader and the app must have the same arch for the injection to work

Note that any arguments passed to steamclient_loader.exe via command line will be passed to the target .exe.
Example: steamclient_loader.exe -dx11
If the additional exe arguments were both: passed via command line and set in the .ini file, then both will be cocatenated and passed to the exe.
This allows the loader to be used/called from other external apps which set additional args.

DllsToInjectFolder

The folder specified by this identifier should contain the .dll files you'd like to inject in the app earlier during its creation.
All the subfolders inside this folder will be traversed recursively, and the .dll files inside these subfolders will be loaded/injected.

Additionaly, you can create a file called load_order.txt inside your folder (root level, not inside any subdir), mentioning on each line the .dll files to inject, the order of the lines will instruct the loader which .dll to inject first, the .dll mentioned on the first line will be injected first and so on.
Each line inside this file has to be the relative path to the target .dll, and it should be relative to your folder. Check the example.
Any .dll file not mentioned in this file will be loaded later, but in random order.

---

extra_dlls

This folder contains an experimental dll which, when injected, will attempt to patch the Stub drm in meory, only for v3.1