bnetlauncher

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.

Howto Use

  1. Extract the included exe to any location you want (ex: steam folder)
  2. Add the exe to steam as a non-steam game shortcut
  3. 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

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).

Known Issues

    • 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 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
      signed in.
    • 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.

Downloads

bnetlauncher_v118.zip
github repo (Source Code)
Older versions

107 thoughts on “bnetlauncher”

  1. Thanks, I’ll give this version a try tonight.

    The double instances opening isn’t an issue with bnetlauncher itself, its just a side effect of the workaround to first problem. The behaviour on the host maps out something like this:

    0s: stream1 is opened
    0s: launcher invokes destiny2.exe(1)
    1s: launcher exits
    1s: stream1 is closed
    10s: destiny.exe(1) opens on screen
    12s: stream2 is opened
    12s: launcher invokes destiny2.exe(2)
    13s: launcher exits
    13s: stream remains open as destiny2.exe(1) is displaying on screen

    x: destiny2.exe(1) is closed
    x: stream2 is closed
    x+1: destiny2.exe(2) opens on screen

    Those timings are rough, but the second instance of the process simply comes from the necessity to attempt to stream the game a second time coupled with some clever logic in the game to not try to display two instances of itself at once if two are open (if i drop back to the host desktop while stream2 is running i can see two instances of destiny2.exe with different PIDs in task manager).

    So the second issue isn’t really one I’d expect you to try fix, it was more just for background of the workaround I’ve used and the knock on impact.

  2. Update: The fix you’ve put in seems to have done the trick, stream just sits on a black screen for a few seconds until destiny2.exe finally gets brought to the foreground at which point everything behaves as expected.

  3. Thanks for your help, daf! I really appreciate it. I uninstalled my Battle.Net client, rebooted, made sure there were no lingering Battle.Net leftovers in the registry, then reinstalled the client. That got the URI associations in place and now bnetlauncher works flawlessly!

  4. Hey, I really love the bnetlauncher, I am using it every day with Overwatch. I’ve read on Bungie website that overlays are not supported (with some exceptions) .. I played Destiny 2 beta with this launcher to have the Steam Overlay, but now I am scared to launch it again, because I could be banned forever because of it. Is there any risk using it? I used it already and I didn’t have problem but I am scared now. (info about the Destiny 2 and overlays – https://www.bungie.net/en/Help/Article/46101 )

  5. That will depend on Bungie considering using steam overlay as a banable offence. bnetlauncher itself does do anything nefarious, it simply closes the game and reopens it under steam.

    In the end only Bungie can tell you for sure if you can be banned or not, all I can tell you is that I will personally still continue to use it with destiny 2, same as I’ve with every other game on battle.net game since i created bnetlauncher.

  6. Very flattered but currently there’s no way to donate, I appreciate the thought though, so thanks 🙂

Leave a Reply

Your email address will not be published.