Battle.net update broke this
mijofa opened this issue · 26 comments
Battle.net auto-updated to Build 10202 on 2018/06/22 and since then I haven't been able to make bnetlauncher work with Overwatch. I don't have any other Battle.net games installed so I'm not sure if it's actually affected any other games.
I'm runninng the latest version of bnetlauncher, I was running an older version, but updated when I ahd this problem and the problem is still occuring. I've attached the debug log below.
I can confirm that it's not just Overwatch. I get the same error for all of my installed Battle.net games (Overwatch and Destiny 2) on both my Desktop and Laptop with bnetlauncher v119
Looks like Battle.net doesn't support the "battlenet://" URI handler the same way anymore. I tried launching "battlenet://Pro" from the run dialog and all it did was open Battle.net to the Overwatch tab without launching the game. "battlenet://S2" switched to the Starcraft tab, so it's definitely triggering something in Battle.net, even though it's not launching the game itself
In battle.net logs I get this after I dispatch the URI handler:
D 2018-06-24 06:49:42.092167 [CommandQueue] {Main} Received IPC Message: IPC_COMMAND
I 2018-06-24 06:49:42.092207 [CommandQueue] {Main} Dispatching Command: handle_uri battlenet://Pro
I 2018-06-24 06:49:42.092242 [ScreenController] {Main} Changing screen to: Games
D 2018-06-24 06:49:42.092377 [GameController] {Main} Selecting game family by id: Pro
I 2018-06-24 06:49:42.094897 [GameController] {Main} Picked default selection by type for family: Pro lastSelectedAccountName= lastRegion=US lastTypeString=retail regionHint=US foundAccount=GameAccount(ai=[5272175-Pro(retail) r:?? entity:(Game: US-Pro-117784626) 05213C78[G]] region=US name= visible=1 uniqueId=Pro_retail) foundRegionOverride=US
I had already confirmed on issue #19 battle.net client no longer launches the game when using battlenet:// shortcuts.
I don't expect blizzard to fix it anymore so i'll try to find workaround, but it's going to take some time. Seems I may have found a quick and dirty way to work around it, you find a rough early beta here.
Works great! Thanks.
This actually works better for me than before as it previously didn't work if Battle.net was minimised in the tray, now it correctly brings Battle.net to the foreground and then launches the requested game
Improved version, if nobody reports any issue it will become the new release.
Now that the launching method is different, can we hope to create a shortcut for PTRs (Overwatch PTR for example) ? Or nothing has changed on this subject and it remains impossible ?
Thank you in advance.
It's was never impossible, just a pain to implement.
The only way I see to do it at the moment would be to just blinding send a click event into the window to hit the combo box to give it focus then use send arrow key keystrokes to change the selection.
This is a very hacky method which would break on any minor change to the blizzard client or if the user did anything during that process, that's why I've chosen not to do it as it more work then it's worth.
Thank you for the clarification !
Firstly, thanks Blizz for breaking stuff :D
Now to meaty stuff, I did some digging, and pulled new strings battle.net uses to launch games (and some windows)
All commands are now against "Battle.net.exe"
Commands (all are case sensitive):
--exec="launch DST2" Launches Destiny 2
--exec="launch WoW" Launches WoW
--exec="launch VIPR" Launches CoD: Black Ops 4 (probably, not out yet)
--exec="launch D3" Launches Diablo 3
--exec="launch S1" Launches Starcraft Remastered
--exec="launch S2" Launches Starcraft 2
--exec="launch WTCG" Launches Hearthstone
--exec="launch Hero" Launches HOTS (not tested)
--exec="launch Pro" Launches Overwatch
--exec="focus play" Opens or switches to Game tab
--exec="focus shop" Opens or switches to Shop tab
--exec="focus social" Opens or switches to Social tab
--exec="focus news" Opens or switches to News tab
--exec="dialog friends" Opens Friends window
--exec="dialog settings" Opens Launcher and goes to Settings window
With this known, I hope bnetlauncher will be fixed in no-time (or at least SOON™).
Edit: Looks like 1.20 beta is already done ... well, at least commands are now public, and someone will maybe want command for friend window :P
Edit 2: Beta 2 is sadly not working for me, I have friends window always open, and looks like ENTER is being send there instead of Launcher window which opens second later, but it works fine with friends list closed.
However I would like to recommend commands above if possible ;-)
They are used in JumpLists and are native.
@Ethan-BB thanks for the detective work, i'll redo the beta using your method since it's a lot less hacky.
WoW, D3, Destiny 2, HS, SC2 and OW works fine.
SC Remastered just opens the launcher ... gonna guess typo/wrong letter case?
Forgot to update sc1 since it's the only one that changed, will do it as soon as I can.
Is it possible to add support for CoD: BO4 in advance ?
--exec="launch VIPR" Launches CoD: Black Ops 4
It's already added (at least in beta) with codbo4 flag.
Hope this is the last beta needed. Everything should work, tested on regular and beta client with the games I had installed (overwatch, wow, diablo).
After thinking about it, pushed beta into release since it should be better then totally broken tool. Release is just beta 3 renamed.
Thank you @dafzor ! It's perfect !
I tried this on normal and beta launcher and it dont work at all. Maybe only a problem in europe.
got it!
Battle.net.exe --exec="launch S2" <-- works now
Launcher must already be loaded otherwise the game does not start and it ends in the launcher.
Just in case anyone's interested. Turns out I can use the 121b1 version to play PTR, I just gotta be real quick about selecting the PTR version before it manages to press enter
Oh man, I tough it was from Battlet.net.exe. Perfect.
@Ethan-BB Classic WoW is upon us now! How did you retrieve the list of game codes before? I'm trying to figure out what the code for classic is. The obvious ones like WoWC and CWoW aren't working :(
I doubt a valid WoW Classic code would exist since it's setup as a sub-game like the ptr.
That said, have you give the latest beta a try?
I doubt a valid WoW Classic code would exist since it's setup as a sub-game like the ptr.
That said, have you give the latest beta a try?
Beta is working perfectly for me.
Would still be nice to know what the product code is, or if it is possible at all to launch PTR-style games. If anyone figures it out, please share :)
hello, did anyone figure out the classic launch code? thanks