Gproxy DLL
GProxy DLL
GProxy++ DLL is a reconnection plugin for Warcraft III. It is based on Gproxy++ by Varlock and Gproxy GUI by LadyGaga, made into a Warcraft III plugin with various bugfixes and optimizations by h3rmit. It is used as a tool that will allow you to reconnect to the game.
How to set up
- Click on the download link above.
- Download the 2 files, and move them into your Warcraft III folder (probably C:\Program Files (x86)\Warcraft III\).
- Launch Warcraft III.
- In Warcraft III, click the magnifying glass icon next to "battle.net" and ensure that "GProxy" is selected as your gateway.
- By default, this GProxy version is setup for Europe.battle.net connection. If you wish to change servers, you need to open the "gproxy.cfg" file in notepad and edit the server name to USEast.battle.net, USWest.battle.net or Asia.battle.net. You will have to restart WC3 afterwards.
Advantages
- Gproxy DLL works over Battle.net. By default it connects to europe.battle.net, but it can be easily changed.
- It does not require any cd-keys.
- It is a single file, and it is a Warcraft III plugin.
- Games that support Gproxy will appear with a [G] in front.
- Gproxy automatically spoof checks you upon joining a lobby.
Troubleshooting and Tips
GProxy is not listed as an option on bnet realm list
- Proceed and log on to your default realm (the same realm listed on your GProxy config file)
- Log out and close all wc3 and GProxy windows
- Re-run GProxy and you should see GProxy realm listed now
GProxy does not connect to bnet
- Press Windows start button and search for “cmd“ or “cmds” or “command prompt”, without the quotes.
- Once a dos window opens up, type “ipconfig /flushdns”, without the quotes. See figure 1.
Cannot join games
- Gproxy DLL may have port conflicts with WC3 client.
- Make sure Gproxy uses port 6112 to connect.
- Open WC3, go to options, Game, and check the port used by WC3.
- If it is 6112, try to change to 6113, 6114, and so on.
Note: ENT is new to this reconnection tool, and some errors might not have been discovered yet. If you encounter an error not listed below, please post a topic in the technical support forum.