Ever since steam allowed to add non steam games to it that it become my gaming hub having all my games there ready to be launched.
There’s many ways to add blizzard games to steam, but I’ve made bnetlauncher to be the simplest method while retaining the benefits of automatic login.
It’s now been years since I last played a blizzard game so this project has been put into “maintenance” as I’m no longer a user of it.
Contributions are still accepted (new games, features, etc) but other then those no further developments will be made.
There still other launcher project in active development like Launchpad in case bnetlauncher no longer works for you.
- Extract the included exe to any location you want (ex: steam folder)
- Add the exe to steam as a non-steam game shortcut
- On the shortcut properties open Set Launch Options… and add one of the following codes:
|Call of Duty: Black Ops 4
|Call of Duty: Black Ops Cold War
|Call of Duty: Modern Warfare (2019)
|Call of Duty: Modern Warfare 2 Campaign Remastered
|Call of Duty: Modern Warfare 2 + Warzone 2
|Crash Bandicoot 4: It’s About Time
|Diablo 3 Public Test Realm
|Heroes of the Storm
|Overwatch Public Test Realm
|Warcraft 3: Reforged
|World of Warcraft
|World of Warcraft Classic
|World of Warcraft Public Test Realm
The result should look something like this:
Additionally, can also use Change Icon to use the icon of the game you’re adding. If you’re still unsure how it should work you can watch a video bellow of bnetlauncher in action:
Public Test Realm and World of Warcraft Classic
With the release of the the new client in 2021 it’s no longer possible to launch PTR and Classic version of games without manual interaction.
If you’re brave enough there’s an untested experimental 2.15 version that tries to restore that functionality.
In case of problems logging can be enabled by creating a enablelog.txt file inside
%localappdata%\madalien.com\bnetlauncher\, you can open the location by pasting the path into explorer or the run dialog in windows (WinKey+R)
- Launching WoW Classic and PTR version of game depends on the client gaining focus for bnetlauncher to send a keypress to it so it will launch the game. Not letting the Battle.net client gain focus will break the functionality.
- Slow computers might take too long causing to bnetlauncher to think something went wrong, see additional options on how to use –timeout to fix it.
- Enabling multiple instances of battle.net client in it’s options might break bnetlauncher functionality.
- Users of MSI Afterburner, Fraps and other overlay software might experience crashes do to incompatibility with their own overlay and steam’s, to solve the issue disable the 3rd party application overlay.
- The game, bnetlauncher and steam must all have the same running permissions to work properly, this means if one of them is running has Administrator/Elevated Permissions, then all of them must also be run has Administrator/Elevated Permissions.
- It’s not possible to automatically launch games with a specific region set. The client provides no direct option to do this, however a workaround can be done by creating a new game entry and the nolaunch option and manually selecting the region before clicking play.
- Battle.net client “ads” will interfere with the PTR and WoW Classic wow launch, when it happens user will need to press the play button manually to continue the game launch.
- Default launching the client trough a scheduled task may be incompatible with some setups, workaround is provided with
- Starting multiple copies of Startcraft Remastered may cause bnetlauncher to show an error since the game only allows one instance to be run at the same time.
- There’s no built in routine to clean up the log files if they pile up (logging is disabled by default)
- Call of Duty: Cold War might work better when using –timeout 10 for some users.
There’s also the following additional options provided by command line switches:
--timeout <seconds>, -t <seconds>changes how many seconds it tries to look for the game before giving an error (15 seconds by default).
--notask, -nstarts the launcher directly instead of trying to use a scheduled task
--leaveopen, -lleaves the client open after launcher the game. If combined with
--notaskoption it will show you as playing on steam until you close the client.
To remove all traces of bnetlauncher from your system:
- type ‘Task Scheduler’ in start menu and open it, expand library and delete bnetlauncher folder to remove the tasks used to start the client
%localappdata%\madalien.comin start menu and open the folder, delete bnetlauncher folder to remove log and gamedb.ini files
- Windows 7 SP1 or above (Only tested on current release of Windows 10)
- .Net Framework 4.7.2 (included in Windows 10 April 2018 Update [Version 1803] or above). Download link: https://www.microsoft.com/net/download/dotnet-framework-runtime
internet coder Maruf for ghost tray icon fix code github Ethan-BB for the new parameters to launch games on battle.net.
github RobFreiburger and iMintty for Starcraft Remastered and Destiny 2 support respectively.
/u/fivetwofoureight for creating and allowing me to use his icon. /u/malecden, Maverick, /u/sumphatguy and others for their help pointing out bugs.
github jbzdarkid for fixing some typos in the documentation.
github jacobmix for crash bandicoot 4 addition
github KyleStilkey for Diablo Immortal support
github d3rt0xx for MW2 & WZ2.0 support
github Sectimus for Diablo IV support