COL (CO Loader)

This will come in handy for those of you who are creating private servers and want to bypass all the bullshit that has been added to the client.

WARNING you will be bot jailed if used on official servers! These edits are to be used for Private Server use only!!

Version 1.4 Features:

• Works on Clients version 6000+ / Conquer 3 Clients
• Works on English, Chinese and Egyptian Clients (Haven't tested anymore)
• Server.dat encryption is bypassed. (create/edit your own server list data)
• Annoying version check upon start game/login have been removed
• Start Conquer.exe directly (blacknull)
• Custom Exit URL, edit ExitWebsite in COL.config.ini to your desired URL or leave it blank to block the Popup
• Rename Conquer.exe window to whatever you like, edit ConquerWindowName in COL.config.ini
• Decrypted Password written to Login Packet

How to get it to work / Guide

Why the hell don't you just read directly from the outenserver.xml file directly instead of having to keep it in an archive file? That's ridiculous.

Quote:

Originally Posted by Best Coder 2014 Why the hell don't you just read directly from the outenserver.xml file directly instead of having to keep it in an archive file? That's ridiculous.

my guess is he didnt write any code injection to read from the file its self.. i guess he just jmped the encryption or NOP the asm out.

@OP
good work.
are the functions in this loader done by a specific memory address, or a pattern scan?

Quote:

Originally Posted by .Ocularis @OP good work. are the functions in this loader done by a specific memory address, or a pattern scan?

pattern scan dude


Version 1.1 released
-Custom Exit URL, edit ExitWebsite in COL.config.ini to your desired URL or leave it blank to block the Popup

Nice to see someone still has a brain in this community.

Quote:

Originally Posted by Ultimation my guess is he didnt write any code injection to read from the file its self.. i guess he just jmped the encryption or NOP the asm out.

But ...

Quote:

Originally Posted by CrystalCastle Guide Extract COL files into your Conquer directory Extract outenserver.xml from Server.gz Edit the server data in outenserver.xml to your hearts desired Open Server.gz with 7-Zip and replace the outenserver.xml with your edited version Load COL.exe

It sounds like you need to extract outenserver.xml, edit it to fit your needs, then re-add it to the Server.gz archive. :confused:

Quote:

Originally Posted by Best Coder 2014 But ... It sounds like you need to extract outenserver.xml, edit it to fit your needs, then re-add it to the Server.gz archive. :confused:

Which backs up what Ulti said entirely.

Quote:

Originally Posted by KraHen Which backs up what Ulti said entirely.

If he just NOP'd or JMP'd the decryption part, the client would still be reading from server.dat, not Server.gz? Am I missing something? :confused:

Quote:

Originally Posted by Best Coder 2014 If he just NOP'd or JMP'd the decryption part, the client would still be reading from server.dat, not Server.gz? Am I missing something? :confused:

It forces the client to load the gzip file instead of the one that is generated. It doesn't bypass the decryption ;)

Quote:

Originally Posted by CrystalCastle It forces the client to load the gzip file instead of the one that is generated. It doesn't bypass the decryption ;)

If you're forcing the client to load an unencrypted file, then obviously you're skipping the decryption of the server.dat file. Then I ask again: Why not just have the client read the outenserver.xml directly, instead of storing it in an archive file?

The server.dat is encrypted (RSA? can't remember exactly) gzip compressed file containing the outenserver.xml. This is how it is by default, but the client also has functionality to load an uncompressed file. After decrypting the server.dat, it checks if the resulting file is a gzip file or not, and handles it accordingly.
So it's enough to bypass the decryption and rename the outenserver.xml to server.dat.

Quote:

Originally Posted by Best Coder 2014 If you're forcing the client to load an unencrypted file, then obviously you're skipping the decryption of the server.dat file. Then I ask again: Why not just have the client read the outenserver.xml directly, instead of storing it in an archive file?

I see your point. When I get around to it I will look into actually pushing the data in from a file rather then how it is currently doing it :)


Version 1.2 Released
1.2 Features:

• Rename Conquer.exe window to whatever you like, edit ConquerWindowName in COL.config.ini
• Decrypted Password written to Login Packet

Quote:

Originally Posted by Freszone The server.dat is encrypted (RSA? can't remember exactly) gzip compressed file containing the outenserver.xml. This is how it is by default, but the client also has functionality to load an uncompressed file. After decrypting the server.dat, it checks if the resulting file is a gzip file or not, and handles it accordingly. So it's enough to bypass the decryption and rename the outenserver.xml to server.dat.

Thanks, this is the information I was looking for. I never looked at the server.dat encryption, so I had no idea.

Quote:

Originally Posted by CrystalCastle I see your point. When I get around to it I will look into actually pushing the data in from a file rather then how it is currently doing it :) Version 1.2 Released 1.2 Features: Rename Conquer.exe window to whatever you like, edit ConquerWindowName in COL.config.ini Decrypted Password written to Login Packet

[Only registered and activated users can see links. Click Here To Register...]

Version 1.3 Released
1.3 Features:

• General Bug Fixes. Please use Version 1.3+ from now on as it fixes some loading issues that were in the previous versions.