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
Deck Tracker not Launching Hearthstone #3708
Comments
Same for me. Debugged HDT, no errors. Maybe a Battle.net issue? |
Looks like blizzard changed something about the procotols. Don't have time to investigate right now, but this is the command that is no longer working: https://github.com/HearthSim/Hearthstone-Deck-Tracker/blob/master/Hearthstone%20Deck%20Tracker/Utility/HearthstoneRunner.cs#L52 |
I'll take a look. |
The "name" hasn't changed. |
Executing 'Battle.net.exe --exec="WTCG"' launches Hearthstone successfully, but i'm not sure if that's a desired solution since we have to know the installation directory. |
Since we can still launch the battle.net client via
I'm not sure how to best work around the Battle.net.beta client though. Is that the same executable? |
I guess we actually know whether we find the |
The command is actually 'Battle.net.exe --exec="launch WTCG"'. Just installed the beta version and the default and beta client are now running under the same name, so that shouldn't be a problem. I'll implement a fix. |
Gonna leave this open actually until the release it out, to prevent duplicates. There should be a release around noon PST tomorrow. |
Fixed with v1.6.8 |
Bug report
Expected Behavior
I expected to press the "Launch Hearthstone" button and have the Hearthstone app open with the deck tracker active.
Actual Behavior
Nothing happened - the "Start Hearthstone" button was gray for a second but then returned to its original state without the Hearthstone app having been opened.
Steps to reproduce behavior
Just clicking on start Hearthstone.
I've tried the other steps for it not working, such as changing the path, but none of it has worked so far. -
The text was updated successfully, but these errors were encountered: