-
Notifications
You must be signed in to change notification settings - Fork 10
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
Issue reading game version #62
Comments
Not sure. Could be that you/wurst have given the wrong file it tries to get the version from, the game changed something or it is OS-related (not on Windows?). The dorkbox portable executable parser fails there, the fallback uses the Windows wmic.exe to get the version from the portable executable but only receives gibberish as you see above, which it cannot parse as an integer. |
I encountered this too and had to change my path to include |
|
When a runmap request is sent from vscode:
I propose making the following changes: |
#62: info-level logs for game exe version parsing
@Cokemonkey11 @Frotty Can this be closed? |
Nope, still happening. |
Current status seems to be:
What is the latest error message @ssetaiLe ? |
When I tried to reenable GameExeTest, it throws an exception on my system. Looking into it, it tries the
The only key I've ever seen is Why is the .exe not autodetected based on ROC v1.0 registry after installation GameExe Test code
|
I think I used the PROGRAM entry because it directly pointed to the game executable file rather than just the directory. But yeah, I just tested/based it on my local setup, have not tried it on a fresh installation. A problem is of course that it's partially different in different game versions. |
While I continue digging for old versions, here's the CDN data for legacy->battlenet-distributed transition (with v1.28). The takeaway from it: the only official method is to use InstallPath. That's how the modern team did it. https://github.com/mdX7/ngdp_data/blob/master/US/war3/blob/game
|
The text was updated successfully, but these errors were encountered: