Battle.net launcher detection is busted

Currently calling launcher with --exec="launch WoW" only start the launcher not the game itself. After launcher is ready it need to be started once more with --exec="launch WoW" to start the game.

So correct config in this case look like this:

LauncherPath=C:\Path\To\Launcher\Battle.net.exe
LauncherArgs=--exec="launch WoW"
GamePath=C:\Path\To\Launcher\Battle.net.exe
GameArgs=--exec="launch WoW"
MonitorPath=C:\Path\To\World of Warcraft\_retail_\Wow.exe

OSOL can’t start Wow.exe directly as it will not receive auth data from Battle.NET client.

[WombatFromHell]

Confirmed. OSOL’s launcher detection isn’t working properly. ETA on a fix is “soon”.

[AcidWeb]

I can confirm that issue is fixed. Settings provided in wiki now work correctly.