-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken Battle.net launch strings #19
Comments
you beat me to this, was going to submit this issue |
Additonally.. the demo should account for a battle.net game having battle.net launched. If battle net is not already running that must be started first and fully loaded before running that launch command |
@JamesCJ60 sounds like an easy bugfix but unfortunately I'm currently traveling. Will have a look when back. If you like feel free to submit a PR. |
I would say I'm not worried about it to much as it is just a DEMO app. This should be of course considered when implementing the library in any app. |
No problem! At least this note here could help someone later 😁
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Patrick Weiss ***@***.***>
Sent: Saturday, April 15, 2023 8:46:39 AM
To: tekgator/GameLib.NET ***@***.***>
Cc: project-sbc ***@***.***>; Comment ***@***.***>
Subject: Re: [tekgator/GameLib.NET] Broken Battle.net launch strings (Issue #19)
Additonally.. the demo should account for a battle.net game having battle.net launched. If battle net is not already running that must be started first and fully loaded before running that launch command
I would say I'm not worried about it to much as it is just a DEMO app. This should be of course considered when implementing the library in any app.
—
Reply to this email directly, view it on GitHub<#19 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASZ4DJMBOTZFVCZMJPRCS3LXBKKC7ANCNFSM6AAAAAAWQVSZEU>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Hi, I came across a bug when using .LaunchString with Battle.net games.
With the latest release, it currently returns --game=PRO instead of --exec="launch Pro", etc.
The text was updated successfully, but these errors were encountered: