Hello. As you all know, the Lanaya bug in DotA 6.83d has been known for quite a while in version 1.30.1 of Warcraft III. I recently updated the map to improve the crash prevention for Phantom Lancer's Doppelganger, as a few cases were reported to be still be causing a crash. Noticing this update, se...

As I just said in the other thread, it seems like Blizzard has fixed something that was affecting the previous map.

Now v3 has two fixes working simultaneously - my fix and Blizzard's fix. That's why everything is double. The solution is simple: go back to the previous version again.

@h3rmit With latest patch, buying items gives you two of each o.O It looks like old map works fine now with 1.29.1. Probably should've held off patching the map until the hotfix we knew was coming from Bliz. Oh well. Yup, I did say that the new patch would be coming soon. There was no need to updat...

PRECUM. wrote:Gproxy DLL will not work now because there is no way to change the version compatibility without mad skillz.

I plan to release a new version as soon as the 1.29.1 patch comes live.

@h3rmit Not sure if you are still active, but I challenge you to update the map and fix all of the bugs that resulted from the new patch. I will also create a gofundme page for you and donate the first $200 as soon as you accept this challenge. Challenge accepted. DotA 6.83d v3 is out, join bot DA-...

Just today Blizzard has updated its final USEast Battle.net server at 199.108.55.62 to the latest patch 1.27b.

@Kirim please try connecting again now.

On your keyboard, press [Windows Key] + [R]. A window like this will appear: https://upload.wikimedia.org/wikipedia/en/thumb/2/28/Run_Windows.png/302px-Run_Windows.png Type in it ipconfig /flushdns and press Enter. Alternatively, you can type cmd in it, press Enter, and a window like this will appea...

I made a post in Blizzard's forums, it's now up to them to fix it:
https://us.battle.net/forums/en/bnet/topic/20752548111

Until then, the only solution is the ipconfig /flushdns that was mentioned above.

Ok, after lots of research I've finally found what the cause of the problem is. The problem is not caused by GProxy DLL. Let me explain why. There are 12 USEast servers in total (199.108.55.51 - 199.108.55.62). When you try to connect to USEast, your computer picks one of these 12 servers to connect...

It has been pointed out to me by @Hazardous that the "Unable to validate game version" problem may persist even after the last update of GProxy DLL (0.07). I am still unable to replicate the problem or find clues about what is causing it. So, I'd like to ask 2 quick questions that may help...

GProxy DLL version 0.07 has just been released:

http://www.mymgn.com/gproxy

• Fixed some rare race conditions in the patching process
• Improved the AuthInfo patching method
• Added support for PvPGN servers
• Added game start notification

Thank you for the feedback. I am currently working on it.

I see, that's probably a race condition. It seems that sometimes Warcraft III somehow manages to load GProxy DLL before Game.dll is fully loaded.

I can't replicate the problem, but I'll try to fix it soon in the next version.

HazarDous wrote:The one we are currently hosting is from IceFrog if I recall correctly. Did IceFrog give away an open source code of the map for others to continue his work.

No, he didn't. I had a really hard time editing his version, and it took me a few weeks to fix the aforementioned bugs.

@KiwiKiller[QQ] : Here is the content of my gproxy.log (I try to add the log = gproxy.log, but it didn't help) : bnet_hostname = useast.battle.net log = gproxy.log That's your gproxy. cfg file. Search and locate another file, called gproxy. log . There is detailed information in there. @Diablo_ : I ...