GProxy for ghostgraz, updated for Warcraft 1.29+

[Vector]

From Saturday night to Tuesday night, Hoogies, Unitil and I have been working on updating GProxy for ghostgraz. Not only did we release a build for GProxy 2.3.4 (updated from 2.3.3 with the fixes for Warcraft III 1.29+), but we also made it possible to compile from source, if you would like to continue its development.

You can download it from the latest release here: https://github.com/MisterVector/gproxy- ... ses/latest

If you use GitHub, you can fork the repository here: https://github.com/MisterVector/gproxy-ghostgraz

[Gingah]

Crashes and fails with BNCSUtil. Is BNCSUtil necessary for 1.29+? Unitil's more basic interface (https://github.com/Unitil/gproxyplusplus) still works. Error:

Code: Select all

[Friday 17-08-2018 20:43:23] [GPROXY] Configuration file successfully loaded
[Friday 17-08-2018 20:43:23] [GPROXY] Starting winsock
[Friday 17-08-2018 20:43:23] [GPROXY] setting process priority to "above normal"
[Friday 17-08-2018 20:43:23] [GPROXY] Customized GProxy++ Version GhostGraz v2.3.4
[Friday 17-08-2018 20:43:23] [BNET] connecting to server [useast.battle.net] on port 6112
[Friday 17-08-2018 20:43:23] [BNET] resolved and cached server IP address 37.244.27.100
[Friday 17-08-2018 20:43:24] [BNET] connected
[Friday 17-08-2018 20:43:24] [BNCSUI] unable to create ROC key info - invalid ROC key
[Friday 17-08-2018 20:43:24] [BNCSUI] unable to create TFT key info - invalid TFT key
[Friday 17-08-2018 20:43:24] [BNET] logon failed - bncsutil key hash failed (check your Warcraft 3 path and cd keys), disconnecting
[Friday 17-08-2018 20:43:24] [BNET] disconnected from battle.net
[Friday 17-08-2018 20:43:24] [BNET] waiting 90 seconds to reconnect


After this posts, the process halts and crashes.

[Unitil]

@Gingah

It appears that your CD-keys were not entered or were invalid when trying to login.

Code: Select all

Invalid ROC key
Invalid TFT key

Be sure to edit the settings for all required info.

[Gingah]

Code: Select all

cdkeyroc = XXXXXXXXXXXXXXXXXXXXXXXXXXXX
cdkeytft = XXXXXXXXXXXXXXXXXXXXXXXXXXXX


Both are filled out in gproxy.cfg.

[Hoogies]

I know his issue, its not even the keys that are in fault, you need to get the updated files... which I do have.

Extract BNCSutil.rar In attachment, place this one in Warcraft III Folder in Program(x86) Folder where your original Warcraft file path is...

GhostGraz however can be anywhere.... Recommended to be placed in wc3 folder...

If your still having issues let me know. Thanks.

[Vector]

Sorry about that. I had an old copy of BNCSUtil in the release folder when uploading to the releases page. I have updated BNCSUtil with the release download.

[Gingah]

Is it pushed to the repo? Latest commit was august 15th.

[Vector]

Is it pushed to the repo? Latest commit was august 15th.

I updated the release download. The current source code will build BNCSUtil properly. The problem was when creating the folder with the release, I had placed an early copy of BNCSUtil there before finalizing the Qt/MinGW versions so I had just forgotten to update it.

[Gingah]

Ahh, was expecting a version-bump to reflect the change. Surely it warrants 2.3.5? Can confirm it works without crashing now.

[Vector]

You could argue that. 2.3.4 should have had the updated BNCSUtil. The source code to 2.3.4 would have built the correct DLL, so by not updating the version to 2.3.5, my reasoning is that there was no code change and merely a mistake on my part.

[Gingah]

@vector Did this break again with 1.30.1 (PTR)? BNCSUtil fails again with

Code: Select all

logon failed - bncsutil key hash failed (check your Warcraft 3 path and cd keys), disconnecting

This is with the 18th august BNCSUtil.dll from current GH release, 10th august one fails with file-error. This is generally why it's good to compile all in one place, by the way, so dependencies are statically bound to each version - and proper SemVer can be followed.

[Gingah]

Unitil helped me debug this, I had not expected the PTR server-address to be war3-PTR.classic.blizzard.com. Setting "server = war3-PTR.classic.blizzard.com" in gproxy.cfg makes it work with 1.30.1 (PTR).