ENT Gaming

Decided to actually test out WC3Connect. For some reason, I desync all the time on WC3Connect compared to Battle.net. For example, check this account: https://entgaming.net/openstats/dota/?u=anti-denseman. Made it just to test the difference between the two servers. As you can see here, I desync on WC3Connect 6/6 times while only 1/5 times on Battle.net. If you don't mind, could you tell me what to do to connect with WC3Connect?

@Anti-DenseMan once everyone is using WC3Connect the desync issues should go away.

Because maybe the LAN players sometimes enter one state while bnet players enter a different state.

i also find that my WC3Connect frequently closes at the end of the game. I then have to re open and re log in.

@hydroponicTango this sounds like a different problem. You are talking about the .exe, right? Would you be willing to run the debug version of the app? This will have log messages that should be useful in figuring out the cause for the crash you are experiencing.

Instructions are here: viewtopic.php?f=4&t=135760&start=90#p525718

ok, ran it with the dbg version. it closed at the end of the game. Where is the log situated?

@hydroponicTango unfortunately it currently doesn't write to a file, the log is just in the command prompt. You'd need to run it from Command Prompt per instructions at viewtopic.php?f=4&t=135760&start=90#p525718 to get the log, and then can take a screenshot and PM it to me.

ok, unfortunately i didnt get a screen shot for that instance. Next time i am on i will try again and if it crashes I will take the shot of the prompt box

I have the same issue. I disconnect 90% of my games with entconnect while I had it for 10% on battlenet.

@poilut does WC3Connect crash? This is about WC3Connect crashing. Otherwise probably you are getting desync.

Alrighty, happened again. WC3Connect crashed which spat me out of the game this time. Issue is, when it crashes it also closes the command window which was displaying the actions of the app. With that closed there is zero screen shot capability to provide you. any other thoughts??

@hydroponicTango sorry, what I meant is to follow the instructions at viewtopic.php?f=4&t=135760&start=90#p525718 to run the debug version instead of double clicking the .exe. If you double click the .exe then the command prompt will disappear on crash, but if you open Command Prompt first and inside the black window with white text, type this:

Downloads\wc3connect-dbg.exe

Then it should run the exe and the command prompt won't disappear when it crashes.

Processing