weird issue i don't know where it coming from

[johnneijzen]

wc3proxy.log

[zortslowski]

I am having the same issue

windows 10 Build 19043
The Frozen Throne 1.27

If I leave the proxy as 1.28 I do not receive the error below.
I haven't had luck getting the proxy to resolve the game if I leave the version at 1.28.
I haven't found a link to a 1.28 patch

Run as normal user or as admin returns the same result

couldn't execute "C:\Users\username\wc3proxy-cli.exe": no such file or directory
    while executing
"open |[concat $command 2>@1]"
    (procedure "::tunnel::start" line 3)
    invoked from within
"::tunnel::start $::IP $::VERSION $::EXPANSION"
    (procedure "openTunnel" line 3)
    invoked from within
"openTunnel"
    invoked from within
".controls.bottom.2 invoke "
    invoked from within
".controls.bottom.2 instate !disabled { .controls.bottom.2 invoke } "
    invoked from within
".controls.bottom.2 instate pressed { .controls.bottom.2 state !pressed; .controls.bottom.2 instate !disabled { .controls.bottom.2 invoke } } "
    (command bound to event)```

[leonardodino]

maybe the path on which the wc3proxy.exe is located has some space in it?
I definitely didn't test that case. (i just placed it on desktop of a virtual machine, no spaces in user name)
can't debug now, don't have a windows machine handy 😕 (and I barely know TCL 😅 not the wisest choice to write it in)

this was written mostly as a way to get to work on my macOS. the original wc3proxy should work for windows.
(although it's cli only)

[knasiotis]

I have the same issue as the people above. There are no spaces in the path it is included.
"D:\knasiotis\wc3proxy-cli.exe".
It also keeps running in the background even after showing an error. It doesn't exit.
Apparently it works if I let it 1.28, but it does not work in 1.29 which is a very similar version

[andrewjbennett]

I was getting this error too when running on Windows, with version 1.27.

I found that repeatedly trying would eventually work (just click OK on the error then click on the connect button again); at one point I accidentally did 1.28 instead of 1.27 which didn't have any errors, I'm not sure if that was the reason that it sometimes started working with 1.27 afterwards.