Sandbox for Legion Beta

[IllidanS4]

"Connection Patcher version: Not on Github, x86 only"

Sorry? As I said, for x86 I get BLZ51914003 error when I try to log in. Are these correct for WowT_Patched.exe (16652264 B, 7.2.5.24163, enUS)?
MD5: df 18 91 07 52 c8 7f 83 66 fb 1f 50 47 37 34 c6
SHA1: 75 56 f0 e3 48 6c a4 c7 6e 2e d2 e4 d4 83 16 83 08 f5 b4 c2

[doityourself]

please set the correct portal in your config.wtf

[IllidanS4]

It's set to 127.0.0.1:8000 as stated in the readme file. I guess it gets to the server, because it prints "Client disconnected", but the connection is somehow dropped then. Here is the contents of ca_bundle.txt.signed. WoW also shows a window with "World of Warcraft is performing initial setup of required data files." before launching. Is that correct?

[doityourself]

It's set to 127.0.0.1:8000 as stated in the readme file. I guess it gets to the server, because it prints "Client disconnected", but the connection is somehow dropped then. Here is the contents of ca_bundle.txt.signed. WoW also shows a window with "World of Warcraft is performing initial setup of required data files." before launching. Is that correct?

Win10? or win7?

[IllidanS4]

Windows 7 (64-bit). Do the hashes match? Can you send me your patched exe?

[doityourself]

Windows 7 (64-bit). Do the hashes match? Can you send me your patched exe?

I bet this is the first sandbox you are using? If not did they work before?

There is no support for windows 7 because of certificate issues.

[IllidanS4]

This is the first sandbox for Legion I am using, but I had run emulators for older expansions, lastly for Warlords of Draenor. What are the certificate issues in Windows 7? I am sure a lot of people would be concerned about Windows 7 not being supported. Where are the sources for the server? I know C#, I may be able to fix the issue.

[doityourself]

This is the first sandbox for Legion I am using, but I had run emulators for older expansions, lastly for Warlords of Draenor. What are the certificate issues in Windows 7? I am sure a lot of people would be concerned about Windows 7 not being supported. Where are the sources for the server? I know C#, I may be able to fix the issue.

It's related to .net and it's tls cert handling on windows 7.
These problem exist since the first legion sandbox release and won't be fixed (or can't be idk...).
Also I don't support usage of old systems like windows 7.

[IllidanS4]

It's related to .net and it's tls cert handling on windows 7.
These problem exist since the first legion sandbox release and won't be fixed (or can't be idk...).
Also I don't support usage of old systems like windows 7.

Can you be more specific? Is the issue client-side or server-side. If server-side, can a server be run on Windows 10 and the client on Windows 7? Can the Battle.net server be simulated in some other way? If the game can run normally, surely the problem must be fixable.
I am not going to start an argument here, but Windows 7 is neither old nor surpassed.

[doityourself]

Can you be more specific? Is the issue client-side or server-side. If server-side, can a server be run on Windows 10 and the client on Windows 7? Can the Battle.net server be simulated in some other way? If the game can run normally, surely the problem must be fixable.
I am not going to start an argument here, but Windows 7 is neither old nor surpassed.

Windows 8+ support only, so it won't be fixed. The sandbox already contains the Battle.net auth protocol.

[IllidanS4]

Windows 8+ support only, so it won't be fixed. The sandbox already contains the Battle.net auth protocol.

Thanks for your help. It doesn't appear running the server on a Windows 10 computer helps.

[Horya]

Crit error on Character screen after new ptr update any chance for update?

[Horya]

are you gonna update it for 7.3 ptr?

[IllidanS4]

are you gonna update it for 7.3 ptr?

Preferably with support for desktop versions of Windows (i.e. Windows 7).

[doityourself]

Preferably with support for desktop versions of Windows (i.e. Windows 7).

No W7 support from my side!

I'll release an update later today