Make your Conquer.exe a .txt file. Then search for TQServer and there is your key. Awesome security eh =)
Probably that's not the problem.. but anyway, chek it.
The error is part of OpenSSL.Native NOT sending or anything related to anything about CONQUER.exe
Arco, you're probably using .NET 4.0, downgrade to 3.5 and make sure your libeay32.dll is in bin/debug and bin/release folders where it should be, also make sure you're using the right libeay as I don't know what OS you have,so if you have x64 try using Korvacs guide.
Also, if you use a wrong key you will only get a disconnect. I don't see why they declare such things as a 'wrong key'.
Also, if you use a wrong key you will only get a disconnect. I don't see why they declare such things as a 'wrong key'.
Well, Arco never said anything about disconnection. He said only that it errors when doing = new ConquerCipher("KEY");.
Quote:
Alright alex you were right about the libeay32.dll
Now the error I'm getting is;
That's because you try to get the clientkeypacket from a 1052 packet? Check your screen yourself lol, the buffer is only 28bytes length and it has to be atleast 128 to be a valid buffer for the clientkeypacket.
Hybrid's source updated to 5252 05/07/2010 - CO2 Private Server - 13 Replies Hybrid's source updated to 5252 :D! Rarrr TeratoDragon xD
[Help]Hybrid's Source 08/09/2009 - CO2 Private Server - 7 Replies Hey I find this really confusing. I want to try out this source but I don't know where to start. http://www.elitepvpers.com/forum/co2-pserver-discus sions-questions/203219-release-extremely-basic-but -working-bugless-c-source.html
If anyone can help me on this step by step on msn please add me: [email protected]
[Help] Connecting to Hybrid's source. 05/01/2009 - CO2 Private Server - 9 Replies Hey guys, me again.
I downloaded Hybrid's source, set it all up and ran the server.
When I connect it comes up with "Unable to connect to the game server", now this usually happens when I.P's are wrong, i think, but I only found 1 I.P I had to set, and that was in the client's server.dat
I am supposed to be using a 5017 client, right?
Thanks :mofo: