If someone want it, here is the Hybridefender.dll that was used for Project Manifest in 5135 version.
static unsafe void Auth_ClientReceive(NetworkClient nClient, byte[] Received)
{
AuthClient Client = nClient.Owner as AuthClient;
Client.Crypto.Decrypt(Received, Received, Received.Length);
fixed (byte* pReceived = Received)
{
ushort Type = *((ushort*)(pReceived + 2));
switch (Type)
{}
You don't seem to understand the problem. The source builds fine and runs fine, no problems when it comes to that. But whenever a client logs in (or tries, lol), it never reach the 1086 hence the Receive is wrong, which I think comes down to the Crypto.Decrypt.Quote:
Everything is fine with the source eme.
Just download Visual Stuido 2008; The source was built under 2008 and since we don't have the sources , or your just lazy to port out the issues, download visual studio 2008 off the internet and build under 2008 conditions.
Other than that , if anyone needs help with the spell issue , use a skill and you dc right away. I got the fix for that.
I haven't encountered that, is there anything else that you need to do to trigger it? Beause my spells work just fine, the ones that are coded that is, not coded ones obviously don't work.Quote:
Everything is fine with the source eme.
Just download Visual Stuido 2008; The source was built under 2008 and since we don't have the sources , or your just lazy to port out the issues, download visual studio 2008 off the internet and build under 2008 conditions.
Other than that , if anyone needs help with the spell issue , use a skill and you dc right away. I got the fix for that.
He's using an untouched client, that starts without hybrid's defender...which means the auth crypto is wrong. (in client file in auth project, the good auth crypto is '//', replace it and it's fine)Quote:
I haven't encountered that, is there anything else that you need to do to trigger it? Beause my spells work just fine, the ones that are coded that is, not coded ones obviously don't work.
Sorry, should of mentioned that I'm actually injecting the HybridDefender into the client, lol. At first, I injected the HybridDefender that Kiyono used, which resulted in the injection failed and client closed. Then I tried with the one that's recently posted, on this page actually, whereas the injection was successful, but encountred this problem.Quote:
He's using an untouched client, that starts without hybrid's defender...which means the auth crypto is wrong. (in client file in auth project, the good auth crypto is '//', replace it and it's fine)