BUG: Battle.net applications fails on <GAMENAME>.exe

[Kreyren]

Battle.net installers fails with unexpected error resulting in installing wineprefix, but not listing it in phoenicis's Library.

STEPS TO REPRODUCE

Install any battle.net application without .executable(Battle.net.exe). Log-in -> Error occurs prior to log-in.

WORKAROUND

using .executable(Battle.net.exe) fixes the issue, but launches the Battle.net instead of the game -> Expected compatibility issues with end-users installing games on battle.net due missing dependencies in wineprefix that is optimized for other title.

EDIT: same error appears if the Battle.net installer is already installed.

[ImperatorS79]

All the Battle.net installers ?

[Kreyren]

@ImperatorS79 Correct, testing your hearthstone atm.

EDIT: Encountered same issue on OverWatch also.

[ImperatorS79]

EDIT: nvm, it is not that. Really strange behavior.

[Kreyren]

Afaik phoenicis checks if the executable was called for some reason.. That seems like horrible idea for applications that calls external installer/launcher.

Recommends removing this check or adapting a function for extermal launcher/installer if needed.

[ImperatorS79]

No, this is just the function which creates the shortcut, which is called when the installer ends. But yeah, this does not work if the installer call another .exe to install the game.

[Kreyren]

@ImperatorS79 noted.

[Zemogiter]

I have no issues with either Battle.net app and Starcraft 2. Check the scripts for both.