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.
- 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:
code game wow World of Warcraft d3 Diablo 3 hs Heartstone ow Overwatch sc2 Starcraft 2 hots Heroes of the Storm scr Starcraft Remastered dst2 Destiny 2(Bungie seems to have purposely disabled overlay) codbo4 Call of Duty: Black Ops 4
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:
Optional: 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).
- Destiny 2 will not have Steam Overlay or any associate features when using bnetlauncher. This is intended by Bungie and cannot be resolved. Steam Input users can use GloSC
- Enabling multiple instances of battle.net client in it’s options will 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
- It’s not possible to launch PTR versions of games, bnetlauncher uses battle.net client URI handler to
start the games, which does not support the PTR versions. I haven’t found a solution for this.
- If bnetlauncher is used to start multiple games at the same time the last ones to launch will not be automaticly
- 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.
- Users of the 1.5 beta series will need to delete the “%localappdata%\madalien.com\Battle.net Launcher for Steam”
directory by hand.
- There’s no built in routine to clean up the log files if they pile up (logging is disabled by default)
- On close battle.net client will leave a “ghost” tray icon after being closed by bnetlauncher, moving the mouse
over it will make it disappear.