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 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 add one of the following parameters:
    <

    code game
    wow World of Warcraft
    d3 Diablo 3
    hs Heartstone
    ow Overwatch
    sc2 Starcraft 2
    hots Heroes of the Storm
    scr Starcraft Remastered

The result should look something like this:
Example bnetlauncher use

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 or other overlay software might experience crashes when both it’s overlay and steam try to attach to the game, disabling said overlay software fixes the issue.
    • bnetlauncher does not check invalid game arguments so it will just error out after 15s when not detecting a running game.
    • If the game is run as Administrator bnetlauncher will not be able to retrieve it’s parameters unless it’s run as Administrator as well, Steam will also need to be run as Administrator so overlay can work.
    • Sometimes battle.net client URI association will break making bnetlauncher unable to work, reinstalling the client should fix the issue.
    • 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 have not found a proper workaround for this.
    • If more then 3 battle.net games are started at the same time some of them will not be auto logged in, this seems to be a limitation with the battle.net client.
    • 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.
    • Running bnetlauncher as administrator will break steam overlay if steam is not also run as administrator

Downloads

bnetlauncher_v113.zip
github repo (Source Code)
Older versions

90 thoughts on “bnetlauncher”

  1. Every blizzard games launch well but I don’t have the overlay, and steam doesn’t say I’m in game. I have nothing in the log :/

  2. The log only works if you create a enablelog.txt in %localappdata%\madalien.com\bnetlauncher\ (you can copy the address into explorer to open it.

    Could you do that and send me the content of the log so I can try and see what’s going on?

  3. From the log everything seems to be working as intended so the overlay should be showing normally.

    Do other battle.net games show the overlay? If it’s just Overwatch then I’ll try running some tests on a friends machine (don’t own it and there’s not starter edition) .

  4. I just tested the new version and everything is working fine for me. I only have Overwatch though, so I can’t really say anything regarding other games. I’ll download HOTS and HS later.

  5. I found why, I needed to remove the launch on administrator, it work now thanks

  6. every time i try to start it, [2016-07-28 01:06:51.3649]: Battle.net Launcher for Steam version 1.6.6032.35355 started
    [2016-07-28 01:06:51.3774]: Checking for other bnetlauncher processes
    [2016-07-28 01:06:51.3794]: No other bnetlauncher detected
    [2016-07-28 01:06:51.3814]: Using parameter: battlenet://Pro

    this happens and it just says its in game for like 3 seconds and then closes

  7. I’m running into an unfortunate issue where this program, or, I suppose you can say the Steam overlay, conflicts with TSNotifer (a TS3 overlay http://tsnotifier.cfxxl.de/). If TSNotifier is already running, the game will not allow the Steam overlay to inject, essentially preventing it from being usable even though the game is being launched through Steam. Launching TSNotifier only after the game has started through Steam has the opposite effect; the overlay never appears, but the Steam overlay continues to work.

    I doubt this is an issue you can solve with this utility, but I thought it’d be good to bring it to your attention, just in case.

  8. Hi hedi, sorry for the late reply. Could you see if the “Windows Management Instrumentation” service is enabled and running on your system?

  9. You are correct, the only ones that can really fix that are the devs of tsnotifier and/or steam.

  10. Sadly this doesn’t work for me anymore. 1.3 recently stopped working, so I updated to 1.6 and it launches the Battle.net launcher with Overwatch selected, but it won’t automatically start the game. The overlay doesn’t work either, on the launcher nor the game.

  11. Actually scratch that.. I found the issue. It apparently doesn’t like if I run it without Battle.net being open first. With the older 1.3 I could use this and it would just start it, then launch. But this one seems to be different. Should I just keep the launcher open all the time?

  12. I get a strange error that doesn’t let me launch any games using bnetlauncher… Instead, a windows 10 “choose an app to open bnetlauncher” that’s completely empty shows up instead and doesn’t boot any games. Here’s the log:

    [2016-08-22 15:49:33.8424]: Battle.net Launcher for Steam version 1.6.6032.35355 started
    [2016-08-22 15:49:33.8424]: Checking for other bnetlauncher processes
    [2016-08-22 15:49:33.8474]: No other bnetlauncher detected
    [2016-08-22 15:49:33.8474]: Using parameter: battlenet://Pro
    [2016-08-22 15:49:34.1208]: battle.net client is fully running with pid = 4164
    [2016-08-22 15:49:34.1208]: Issuing game launch command at ’03:49:34.1208′
    [2016-08-22 15:49:34.2024]: Searching for new battle.net child processes for the game
    [2016-08-22 15:49:34.3485]: No child process found.
    (goes on for a while)
    [2016-08-22 15:49:45.2656]: No child process found.
    [2016-08-22 15:49:45.9070]: No child process found.
    [2016-08-22 15:49:46.5643]: No child process found.
    [2016-08-22 15:49:47.2169]: No child process found.
    [2016-08-22 15:49:47.8617]: No child process found.
    [2016-08-22 15:49:48.5076]: No child process found.
    [2016-08-22 15:49:49.1505]: No child process found.
    [2016-08-22 15:49:49.6519]: No child process game found, giving up and exiting

    But if I run the game before bnetlauncher crashes, it works, but doesn’t stick. Upon the next launch, it does the same thing. How can I solve this problem?

  13. Tried using this today on Windows 10 Pro, but nothing happens. Tried with the battle.net client running and closed.

    Here’s the log:

    [2016-08-25 15:54:01.1277]: Battle.net Launcher for Steam version 1.6.6032.35355 started
    [2016-08-25 15:54:01.1297]: Checking for other bnetlauncher processes
    [2016-08-25 15:54:01.1337]: No other bnetlauncher detected
    [2016-08-25 15:54:01.1377]: Using parameter: battlenet://Pro
    [2016-08-25 15:56:01.2405]: battle.net Helpers did not start.
    [2016-08-25 15:56:01.2425]: Could find the battle.net running and failed to start it. Exiting

  14. Do you plan to add support to Overwatch Test and add an option to toggle if battle.net should close or not after the game launches?

  15. Sorry for the late reply (notification on new comments borke down).

    Supporting the launch of PTR version is not supported trough the current method used by bnetlauncher, I might look into it but atm there’s no immediate plans to add it.

    As for leaving battle.net client open it’s not a good idea as it would make steam think you never closed the game until you closed the client. I already spent a few hours trying to work around that without much success.

  16. Are you running the battle.net client as administrator? The log seems to indicate bnetlauncher is finding a battle.net client but not battle.net helper processes

  17. The latest version should work in the same way, are you still having issues? If so could you provide a log?

  18. Good morning,

    Your launcher worked a few months ago but I think a recent Battlenet update broke it, it doesn’t work anymore. Here is the log :

    [2016-09-07 13:28:54.2728]: Battle.net Launcher for Steam version 1.6.6032.35355 started
    [2016-09-07 13:28:54.2932]: Checking for other bnetlauncher processes
    [2016-09-07 13:28:54.2987]: No other bnetlauncher detected
    [2016-09-07 13:28:54.3032]: Using parameter: battlenet://WoW
    [2016-09-07 13:28:54.3670]: battle.net client not running, trying to start it
    [2016-09-07 13:28:55.4422]: Failed to start battle.net client.
    [2016-09-07 13:28:55.4452]: Could find the battle.net running and failed to start it. Exiting

    Thank you for your work by the way

  19. With the battle.net client closed, could you try pressing Winkey+R to open the run menu and typing battlenet:// and seeing if the battle.net client actually starts?

  20. I just tried and Windows doesn’t recognize the command, it asks me to search an application on the Windows Store. It could be the problem, I don’t know if it’s specific to me or if Blizzard changed something but it doesn’t work on my friend’s computer too.

    Thank you for your answer

  21. There’s a few things you can try, you can go to “Control Panel\Programs\Default Programs\Set Associations” and check if BATTLENET entry is associated to “Blizzard File Switcher” (it’s actually just the battle.net.exe in program files), you can try reinstalling the battle.net client to see if it restores the association or you can try importing this regfile of the file association i took of my computer (Windows 10 Pro 64bit), only do the registry import as a last resort though.

  22. Bnetlauncher stopped functioning for me as of the Battle.net Streaming update. I followed your instructions to enable logging but nothing is in the log itself. If this was already solved I apologize but saw nothing. Blizzard file Switch’s association is present. I too am running Windows 10 Pro x64 Build 1511.

    The behavior is as follows; The launcher WILL actually make the game of choice launch, but the process itself terminates and I get no overlay. In Overwatch’s case in particular, it will launch, try to connect and have an overlay, then closes, then re-launches and prompts me for my Battle.net login.

    Any help would be appreciated, hate not having my overlay.

  23. Do you have blizzard streaming enabled? Could you also still post the log (or email it to me if you prefer)?

  24. [2016-09-23 15:31:11.2879]: Battle.net Launcher for Steam version 1.6.6032.35355 started
    [2016-09-23 15:31:11.2889]: Checking for other bnetlauncher processes
    [2016-09-23 15:31:11.3309]: No other bnetlauncher detected
    [2016-09-23 15:31:11.3319]: Using parameter: battlenet://Pro
    [2016-09-23 15:31:11.6679]: battle.net client is fully running with pid = 6652
    [2016-09-23 15:31:11.6689]: Issuing game launch command at ’03:31:11.6679′

    i cant launch overwatch 🙁

  25. It can’t find my launcher anymore today. Battle net is open and running.

    [2016-09-26 14:33:56.1758]: Battle.net Launcher for Steam version 1.6.6032.35355 started
    [2016-09-26 14:33:56.1788]: Checking for other bnetlauncher processes
    [2016-09-26 14:33:56.1818]: No other bnetlauncher detected
    [2016-09-26 14:33:56.1869]: Using parameter: battlenet://WoW
    [2016-09-26 14:35:56.2755]: battle.net Helpers did not start.
    [2016-09-26 14:35:56.2785]: Could find the battle.net running and failed to start it. Exiting

  26. It seems bnetlauncher is not finding two processes named “Battle.net Helper.exe” running, could you confirm that they’re indeed running on your system when you open the battle.net client?

  27. Battle.net desktop app
    Battle.net Helper
    Battle.net Update Agent

    Those are the three processes I see running.

  28. I could never figure out why I don’t have two “Battle.net Helper.exe” processes, so I modified your launcher to only check for one. It seems to be working just fine so far, but are there any problems I may run into only checking for one instance of the process?

    Also, any ideas why I no longer have the second helper process? Your unmodified version worked fine for me a few days ago. To my knowledge there hasn’t been any updates to the Battle.net app and I haven’t made any setting changes.

  29. I honestly don’t know, on my own personal computer battle.net client always create the two processes so that’s what i used to make sure the client was fully running. Making bnetlauncher check for a single process breaks launching games without the battle.net client running so i’m trying to better understand what’s going on in the battle.net client. Some theories I had so far where running the client in admin mode (didn’t work), 32bit windows (haven’t been able to test yet) and the launcher not having 3D acceleration on (not sure how to test for that). Once I actually understand what’s going I hope i’ll be able to push something that might work for everyone.

  30. It seems in Battle.net Client settings -> general -> advanced settings -> disable browser hardware acceleration will cause only one “Battle.net Helper.exe”, I’m assuming you disabled that setting which caused bnetlauncher to fail, I’ll try and figure out a better way to test if battle.net client is fully open.

  31. Ah ha! You are correct, I had apparently disabled the hardware acceleration.

    Thank you for the note about the flaw in my modification. I usually have Battle.net running, so it would have been awhile before I noticed it but it definitely would have left me scratching my head eventually.

    I have scrapped my modified version and have been using 17b2, your beta version. Functioning smoothly so far, but I will report any issues. Thanks for your swift and thorough responses!
    ~dredknot

  32. Daf,

    I apologize for the late reply, had some RL issues. As I said, the log never had anything in it, assuming it’s in the actual enablelog.txt file. The only thing that’s possibly worth noting is that when I did look in the folder, a file was in there labeled bnetlauncher_startedclient.lock. I deleted it but it never came back. I’m willing to attempt to record behavior and upload it somehow if that would be an example, but it’s not recording logs as it is.

    Is there anything else I can do?

  33. Looked at the log and couldn’t find anything that would explain the behavior you described. So I would really appreciate if you could record it with process explorer open with the bnetlauncher processes visible (minimize wininit.exe and chrome.exe process trees) in the hopes of figuring out what’s going wrong.

  34. If any of you are having the no overlay problem, it may be RivaTuner Statistics Server if you have MSI Afterburner installed. That was my problem. You can disable application detection for Overwatch specifically in the RivaTuner options.

  35. Thanks for this, really useful 🙂

    You should throw the sourcecode up on github so you people can report issues and maybe even fix them.

  36. Daf, I apologize for the delay, don’t have much time to sit down and record these things as of late. But I got the footage for you. https://www.dropbox.com/s/0x0xz61z7z0dj1l/clip0002.avi?dl=0 It’s only of Process explorer itself, and I saw above about disabling browser acceleration but it yielded the same results, so I turned it back on, hence the multiple helper exe’s running.

  37. ?ade do you have “Allow multiple instances of battle.net” enabled on the battle.net client?

  38. Daf, I do not. I enabled it just now, the end result was a secondary Battle.net window popped up prompting me for my login information.

  39. I reviewed the video a few times, got a overwatch installation on my computer (don’t own it so can only get to the login screen where it asks me if I wan to buy it) and everything seems to be working as it should.

    bnetlauncher requests battle.net client to start Overwatch, closes it and reopens it under steam to make steam overlay attach to the game, it all ran on my computer the same way it seemed to run on your video being the only difference the start and stop of atbroker.exe (accessibility tools from Microsoft).

    The only thing that would occur me to try at this point would be to temporarily disable any Anti-Virus or other overlay software to see it has any effect.

    I’ll also try and run some tests some other machines but that’s about all I can do atm.

Leave a Reply

Your email address will not be published.