Launchpad vs BnetLauncher vs OSOL

Why another launcher tool?

While extremely useful, I just wasn't satisfied with the level of integration provided by other tools. I designed Launchpad to be able to do the same kinds of things those tools can do, but with a layer of simplicity, power, and a polished UI on top of it.

How Does Launchpad Compare to BnetLauncher?

I learned a lot from studying how BnetLauncher works, so the main magic that BnetLauncher provides is also provided by Launchpad. Both programs inherently know how to launch any Battle.net game based only on its internal launcher ID. Launchpad used to download and run BnetLauncher internally as part of launching Battle.net games, however, Launchpad has now replaced the need for running BnetLauncher at all since it can do the same thing.

Where they differ is primarily in their configuration. Launchpad offers a huge array of configuration options to customize how each launcher works. Additionally, through its configuration UI, you can do everything right from the main Launchpad window.

The other difference is in how seamless the games look within Steam. When you add a Non-Steam Game for BnetLauncher, you have to then edit the game to rename it and change its icon to match the game you want. With Launchpad, when you add the Non-Steam Game, it will already have the correct name and icon, and you won't get that pesky shortcut arrow over the icon in Steam.

How Does Launchpad Compare to OSOL (Origin Steam Overlay Launcher)?

Similar to how Launchpad compares with BnetLauncher, Launchpad is intended to be a superset of OSOL's functionality as well. The configuration system in Launchpad is similar to OSOL in that, for each game you want to launch, you have a number of configuration options you can set in a file that together define how the game is launched, and how to handle the game's launcher if there is one.

Launchpad has the same type of configuration system, except it offers more (and different) configuration options and more flexibility. For many games, you can get a smoother launch experience, or launch it in a way that might suit you better. However, Launchpad's extra configuration options mean you might have to spend more time finding what works best.

To use OSOL, you need to put a copy of the OSOL .exe and config file in the same directory as the game's .exe file. Then you run it to configure it, then you add the OSOL .exe to Steam as a Non-Steam game. You end up running into the same issue as BnetLauncher where you have to rename the game and change the icon, which adds a shortcut arrow.

Launchpad, on the other hand, generates exe files that already have the game's name and icon, so they look seamless in Steam.

Which Tool Should I Use?

While this is a subjective question, especially coming from the developer of Launchpad, I am determined to make Launchpad the most full-featured, seamless, and easy-to-use game launcher tool out there. It's designed in a more generic way and to be used in a wider array of circumstances than either of the other tools discussed.

However, BnetLauncher and OSOL are both amazingly awesome tools in their own right, so if Launchpad doesn't work for you, or you prefer the way that those tools handle things, you absolutely cannot go wrong downloading either one.

On the other hand, if you give Launchpad a try and find that it is lacking some feature that your existing launcher tool had, let me know and I can very likely add the feature for you.