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:

Destiny 2

Bungie has decided to implement anti-cheat mechanisms that also cause most overlays to not work as expected.

Troubleshooting

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)

Aditional options

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, -n starts the launcher directly instead of trying to use a scheduled task

--leaveopen, -l leaves the client open after launcher the game. If combined with --notask option it will show you as playing on steam until you close the client.

Adding more Games

From v2.00 onward bnetlauncher uses a internal gamedb.ini to control how games are launched. More games or custom configs can be manually added by creating a gamedb.ini file in:

%localappdata%\madalien.com\bnetlauncher\gamedb.ini

the directory where the bnetlauncher executable is located.

A gamesdb.ini.sample is distributed with bnetlauncher containing a copy of the built in shortcuts.

Important: Those defaults are not changeble. bnetlauncher will always override them with it’s internal gamesdb.ini file. However it is possible to create different entries with custom options.

noargs doesn’t throw an error when retrieving blank arguments from the game

waitforexit leave bnetlauncher open and waiting until the game existing

nolaunch don`t directly launch the game but just open the client and try to find the game for an additional 60s this can in theory be used for hacky PTR support.

Known Issues

Destiny 2 will not have Steam Overlay or any associate features when using bnetlauncher. This is intended by Bungie and cannot be fixed. Steam Input users can use https://alia5.github.io/GloSC/ to work around it.

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 battle.net client PTR versions of games, 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 clicking play.

Default launching the client trough a scheduled task may be incompatible with some setups, workaround is provided with notask switch/option.

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)

Uninstalling

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

type %localappdata%\madalien.com in start menu and open the folder, delete bnetlauncher folder to remove log and gamedb.ini files

Special Thanks

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.

Never experienced crashing caused by bnetlauncher, so right now i’m unable to reproduce the issue. Check if you don’t have other overlay software that may cause instability when interacting with steam overlay or even aggressive antivirus software.