* fix(epic): start Epic titles that check their parent under an EpicGamesLauncher.exe stand-in Rockstar's launcher only accepts an Epic copy of GTA V when a process named EpicGamesLauncher.exe started it. DroidDeck's Epic client is a Linux program, so the launcher logged "Epic Games Launcher not detected as parent process", failed to relaunch through Epic and showed the game as unowned. - tools/epic-launcher: a small Windows EpicGamesLauncher.exe that starts the game with the rest of its own command line, unchanged, waits for it and returns its exit code. It ships as the epic add-on pack. - The Epic .droiddeck-launch.bat runs the game through it for Epic titles known to need it (GTA V, GTA V Enhanced, RDR2, RDR, GTA SA DE, Returnal, Phantom Blade: Executioners), or for any Epic game whose per-game environment sets DD_EPIC_PARENT=1; DD_EPIC_PARENT=0 turns it off. Those titles also start without Steam's SteamAppId. Without the staged stand-in the game starts directly, as before. - Steam launch options now reach Epic games (%*). - The launch hook fetches the pack when such a title finds it missing. - Rockstar's launcher found no Social Club SDK in the prefix and ran Social-Club-Setup.exe /silent, which never exits under Wine. For Epic titles that carry a Rockstar SDK installer, the hook now extracts the SDK from the launcher's own Redistributables copy (the version the launcher compares against) or, before the launcher is installed, from the game's copy, and registers it. It re-extracts when that installer changes and leaves the Rockstar Games Launcher key alone, so PlayGTAV still installs the launcher on first start. * fix(epic): fetch the parent stand-in exactly when the game will use it; keep Cargo output out of source digests The launch hook runs before droiddeck-game-env applies per-game variables, so it now resolves DD_EPIC_PARENT through droiddeck-game-env's own apply_config and game_id: an unlisted title with DD_EPIC_PARENT=1 fetches the pack, a listed title with DD_EPIC_PARENT=0 no longer waits for it. runtime_inputs no longer hashes the target directory beside a Cargo.toml under its source paths, so a local cargo build of a Windows helper does not fail verify(). tools/epic-launcher gets the same .gitignore as the other helpers. * fix(epic): a DD_EPIC_PARENT in the game's sidecar env decides the stand-in fetch too The .bat sets the sidecar's env before it reads DD_EPIC_PARENT, so that value overrides the game environment there; the launch hook now gives it the same precedence when deciding whether to fetch the pack. * test(epic): keep an inherited DD_EPIC_PARENT out of the launch hook tests --------- Co-authored-by: MaxsTechReview <maxjividen@gmail.com>
Epic Games Launcher parent stand-in
EpicGamesLauncher.exe starts the game named by its first argument as its own child, passes the rest of its command line to the game unchanged, waits for the game and returns its exit code.
Some Epic titles only accept a launch whose parent process is named EpicGamesLauncher.exe. Rockstar's launcher logs Epic Games Launcher not detected as parent process. and then treats the Epic copy as unowned. In DroidDeck the Epic client is a Linux program, so it can never be that parent. The check matches the process name, not its path: Heroic's stand-in works from C:\windows\command and from the game folder.
StoreLaunch writes the Epic .droiddeck-launch.bat to run the game through this executable for the titles in EPIC_PARENT_TITLES, or for any Epic game whose per-game environment sets DD_EPIC_PARENT=1. DD_EPIC_PARENT=0 turns it off. Without the staged executable the game starts directly, as before.
build.sh builds it with the GNU Windows target for the epic add-on pack. The app fetches the pack when it starts signed in to Epic, or when a launch that needs it finds it missing, and stages it in the Linux runtime at /usr/local/lib/droiddeck-epic.
cargo test --locked --manifest-path tools/epic-launcher/Cargo.toml