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 (Bungie seems to have purposely disabled overlay)

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

123 thoughts on “bnetlauncher”

  1. Hello! I love this launcher.. it works well with all my Blizzard games. However, today I can’t use it. It gives me this error…

    Error: URI handle broken
    —————————
    Some of the battle.net client functionality seem to be missing, without it bnetlauncher will not be able to function. Please reinstall the battle.net to fix the situation.

    Alternatively, if you’re still getting this message after reinstalling the client a repair can be attempted, this will create the missing registry keys and prompt you to add them to your registry (you must answer yes).

    Would you like to attempt the repair?
    If you choose No bnetlauncher will exit.
    —————————
    Yes No
    —————————
    ๐Ÿ™

  2. I’d appreciate it if you could provide a github link or similar so I can build your exe from source… not that you’re not trustworthy or anything, just better safe than sorry eh ๐Ÿ™‚

  3. Hopefully you fix the Destiny 2 one ๐Ÿ™ was great during beta. I need this tool because I play fullscreen (better performance than windowd) and i have 2 monitors, so alt tabbing is really annoying.

    Where as with overlay, I can chat with my friends and use the browser.

  4. Damn, stopped working for D2 ๐Ÿ™

    hopefully you figure out what’s going on ๐Ÿ™‚

  5. I have also not been able to get the launcher to work with Destiny 2. I’ve been using it for OW just fine. I have been reading that Destiny 2 isn’t allowing certain capture/streaming services to be used so I am suspecting it may have something to do with that.

  6. As far as I know it looks like it will only run desktop config only. Most likely due to Bungie walling us out.

    I’m not a coder of any kind but will gladly offer help

  7. Yup seems broken for Destiny 2!

    It’s launching but no overlay. Steam controller is remaining on desktop config.

  8. I can’t seem to get this launcher to work with Destiny 2, it works perfectly fine with Overwatch though.

    I’m able to launch Destiny 2, but the Steam overlay doesn’t appear. Is there something I could do to fix this? I set the launch options to ‘dst2’ and put the ‘bnetlauncher.exe’ into Steam as a non-Steam game. I’ve tried launching it with and without Battlenet launched, but I run into the same issue.

    1. @Draz There was a bug in the beta battle.net client that broke bnetlauncher. Latest version of the beta has fixed the issue so everything should work as expected.

    1. Very flattered but currently there’s no way to donate, I appreciate the thought though, so thanks ๐Ÿ™‚

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

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

  10. 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!

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

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

  13. This is pretty awesome, I just found it when trying to solve an issue Streaming Destiny 2 I recalled having with Overwatch.

    Works perfectly with other Blizzard Games I have but seems to be an issue around a delay in Destiny 2 (could just be a beta issue) whereby the launcher is closed before Destiny 2 has loaded on to the screen so causes the streaming to stop. If i then wait 10sec for the game to appear on the host monitor a second streaming session will connect to it and run fine, but does mean when the game is then closed a second instance opens (there seems to be some single instance limiting/queuing going on in the game itself that means if two instances of destiny2.exe are running, the second sits idle in a preloading state until the first closes). Obviously this isn’t a massive deal, just have to remember to VNC onto the host and close down the second instance of the program after I’m done with it, but thought it would be worth the feedback if you wern’t aware of it.

    Would there be any way to introduce a config option to add a delay to closing the launcher to prevent the initial streaming session from shutting down if this isn’t something widespread?

    1. @Ganewate, Okay, if I’m understanding this properly there’s two issues here.

      First seems to be bnetlauncher exiting too quickly and causing the steam home streaming to think Destiny 2 was closed, I’ve added a worked around in version 1.15 that should fix that, if it didn’t let me know and I’ll try to come up with another solution.

      The second issue is multiple instances of Destiny 2 launching? I’ve not encountered this yet, could you provide more detail?

  14. Thanks for making bnetlauncher! I’m trying to get it to launch Destiny 2 through Steam as a non-Steam shortcut, but I’m stuck.

    I don’t know how, my battle.net client doesn’t seem to have any kind of URI association. I’ve reinstalled the battle.net client twice. Start+R and battlenet://dst2 gives me a “There is no program associated to perform the requested action” error.

    Any suggestions? Should I try the reg file you posted in the comments above? Thanks a lot for the help!

    1. @Number 6, The reg file has since been removed since reinstalling the battle.net client would usually fix broken battlenet:// association. If it’s not working there might be something else causing the issue, regardless if you want to try and manually fix it you can use this regfile to manually add battlenet:// association, just be sure to edit the path to the battle.net client executable taking care to use double \.

  15. OK i’m blind or the parametres for the newer games were added recently, either way thanks ๐Ÿ™‚

  16. Not sure if it is possible or if it even applies, do you have the launcher URL for StarCraft:Remastered? Or a update to your launcher to include this? I’ve been trying to get steam overlay (or steam to launch it at all for that matter).

  17. Hello, this software works like a charm, now that SC:R is out i would like to make a request to add it to the bnetlauncher as well.

  18. Thanks, can you maybe upload the compiled version on GitHub to just in case. And maybe if you have the time it would be nice if you could make an launcher for Uplay Games too! ๐Ÿ˜€

  19. Thanks for the info, daf. If I do end up releasing anything, I’ll be sure to credit you (and GitHub it, of course).

    Why am I not surprised that Origin is a bit weird?

    I did a little googling on uPlay. It seems to also use a URI handler (uplay://launch/) so that might be a good angle to attack!

  20. Great work! I can now stream Overwatch to my Steam Link!

    I’d actually started work on a tool to wrap non-Steam games and automatically apply any workarounds needed to get the overlay working. This is also a C# project.

    However, I was missing the trick of grabbing the command-line args which Battle.net passed to Overwatch.exe, then killing and restarting it under the ‘wrapper’ application. Very, very good idea!

    My initial work on my version works something like this: (btw, I named it SteamBogie.exe – it’ll make most English-speakers chuckle, but it’s also a British English term for the wheel/axle/suspension assembly on railway carriages. Keeps with the Steam/Valve thing ;))

    So, perhaps, for battle.net games:

    SteamBogie.exe –launcher battlenet –command battlenet://Pro –client Overwatch.exe

    Then, for Origin, perhaps something like:

    SteamBogie.exe –launcher origin –game C:\Games\OriginGames\Titanfall\Titanfall.exe

    … and it’ll do whatever’s needed to get Origin games compliant. This seems to involve:

    * Quitting Origin if running
    * Launching the game EXE with the Origin EXE path added as an argument (that can be looked up in the registry)
    * Monitoring the process list to watch for the game EXE’s presence
    * Quitting and perhaps restoring Origin’s running/not-running state after the game EXE disappears.

    Certainly something to work on!

    1. Origin and uplay games can be started directly from the game exe, they will launch the client if needed and start running. The launch chain is a bit crazy tough, the game closes and launches the client which chain spawns a load of other processes which eventually launches the game for real (seriously check it with process explorer). So all you need to do then is monitor the game and close the launcher processes after it closes.

      It’s something I’ve thought about but been putting off due to not having any really clever way of doing it. For uplay I’ve already done something the “dumb way” with https://github.com/dafzor/nouplaynag and I suppose the same core idea would work with origin too.

      Best of luck developing your universal launcher.

  21. Hey man, program’s just throwing an error window “bnetlauncher has stopped working” trying to run diablo 3. I’m assuming it’s something to do with the change from battle.net client to blizzard app. I thought it might’ve just been a name change, but seems like it’s something else.

    Any chance of an update?

    1. There hasn’t been any change that required an update at the time of the client name change. First thing I’d ask you to try is getting the latest version, if there’s still an issue comment again and I’ll try to help you.

  22. No overlay software is used and I’ve never had to start battle.net as admin. I’ve e-mailed you a log file, hope it helps.

  23. I’ve used it previously without any issues but after a reinstall of Windows I have issues with the bnetlauncher. Sometimes it works fine but most of the time the launcher starts but doesn’t start the game and after a moment I get the error:

    “Couldn’t find a game started through Battle.net Client.
    Please check if you’re using a valid parameter.
    Aborting process and exiting.”

    I can still launch manually and will see the overlay…sort of (Shift-Tab brings it up, I see the FPS counter but new messages are not visible in the lower right corner as it should).

    1. Are you using any overlay software like MSI afterburner? Are you starting battle.net as admin? Those are two things that could cause problems, other then that i’d need to see a log (see instructions.txt for how to enable it).

  24. Now I don’t get error but the overlay doesn’t work :/, thx for the attention ๐Ÿ˜€

  25. —————————
    Error
    —————————
    Failed to obtain game parameters.
    Game should start but steam overlay won’t be attached to it.
    —————————
    OK
    —————————

    Any solution? ;(

Leave a Reply to Ryan6700 Cancel reply

Your email address will not be published.