Releases: dafzor/bnetlauncher
Releases · dafzor/bnetlauncher
v2.05b1
v2.02
v2.01
v2.00
- Major reorganization of the code
- Totally changed how games are launched and detected running
- Should fix intermitent "game not found errors"
- removed -i option, people launching custom games should instead create a gamedb.ini
- added -t option that allows to manually set in seconds how long bnetlauncher waits for the game to start
- clients are now started using scheduled tasks so steam overlay wont affect them
- added -l option to leave client open if bnetlauncher started it
- no longer leaves tray icon when closing clients (courtesy of Maruf)
- new logger system with more consistent formating making it easy to view in proper apps
- new logger console when running debug builds
v1.22
- Update for renamed files in beta Battle.net client
Binary at: http://madalien.com/stuff/bnetlauncher/
v1.21
- Proper fix thanks to Ethan-BB for the new battle.net client method to launch games.
- Added Call of Duty: Black Ops 4
Binary at: http://madalien.com/stuff/bnetlauncher/
v1.19
- Added notes clarifying Destiny 2 compatibility issues.
- Possibly resolved some issues with incorrect checking of helpers in the previous version
- Major Internal code refactoring to make things tidier
Binary at: http://madalien.com/stuff/bnetlauncher/
v1.18
- No longer accept unknown options by default
- Added a -i parameter to still allow the use of any parameter if the user wants
- Added repair code that tries to restore battle.net client launch capabilities
- Improved documentation and error messages
Binary at: http://madalien.com/stuff/bnetlauncher/
v1.16
- Strip "-" and "/" from the launch option in case someone adds them
- Check alias before know launch option for better log messages
Binary at: http://madalien.com/stuff/bnetlauncher/
v1.15
- Wait for destiny 2 to exit to workaround in-game status issue
- Also remember to close battle.net client when exiting with an error
Binary at: http://madalien.com/stuff/bnetlauncher/