Warforge (not working c# emu based on eWoW)

[Analhammer]

Hey,

i tried updating old eWoW to 3.3.5.
I also modified it so it has a more clustering like structure (with a proxy that redirects shit to x worldservers)
But i got stuck right before characters selection screen. Client just won't give me CMSG_READY_FOR_ACCOUNT_DATA_TIMES & CMSG_REALM_SPLIT. There must be something wrong with encryption... I allready wasted hours trying to figure it out but i couldn't find the problem.

I'm not expecting anyone to dig into the code and find out whats wrong, but ofcourse that would be awsome
It contains a lot of copy pasta from wcell (thx!)

Heres a little screenshot.

Download Source + Binarys here: Download

[Envoke]

Check the other cores and make sure you have all your packets and numbers correct.

[W@WAdict]

Analhammer,

We have not worked on eWoW in a long time, it was not up to the login point yet.

Although I will say that usually what I find when it gets stuck at the connect stage right after the realm list like you say, it usually is either the Auth Session packet is incorrect or the Encryption as you said. I am a newbie with C#, but will try and play with it a little bit to see what is going on in there.

Later.

W@WAdict.

Edit: Hmm, was just thinking how I had a similar problem when updating Spurious to 3.3.5.

If I remember correctly, Unix reminded me that Blizz changed the key for Encrypt/Decrypt to use the 40 byte K instead of the 20 byte Hash it used to use. I have not really had a chance to study the WarForge code, but this may be connected to the problem you are having, worth looking into any way.

Let me know if you make any progress on this.

Thanks.

W@WAdict.

[justMaku]

First of all, keys changed somewhere arround 3.3.3, also now the session key calculation changed. PM me, I'll send you my bot sources. It connects to 3.3.5 servers, but nothing else atm (it worked great in BC era, but now it's kinda useless)