Please, explain more.
With old one I can give lots of updates and I dont have to give 1 big to everyone.
Ex. If I offer to players full client v.1091 then they only download my new patches.
1091 => 1092 =>1093 and so on
But with this...only big file for everyone?
And if I make new update...they have to download again that new huge file?
[Guide(s)] Autopatch,Fixing MSg server prob,Changing music to your server. 10/17/2009 - EO PServer Guides & Releases - 5 Replies Alright first of all i'm sure someone posted these but i see threads of people looking for help so i'm going to explain in great detail how to do such things...
i will add more when i see fit. or i see them posted and add them.
#please sticky
Forcers autopatch2.exe setup....
First put the autopatch and config.ini wherever, and if your on a router open port 9528 tcp/udp i think thats the only one you need i'm not sure.
[Release] Real AutoPatch Server for Co 08/08/2009 - CO2 PServer Guides & Releases - 9 Replies ok this is simple it looks like this
latestpatchver=5001
ip=127.0.0.1
dir=enzf
bind 5000 = 5001-5002
latestpatchver= it checks your verison.dat to see if it match, if it doesnt it will update to the matching version
ip=external ip
[RELEASE] Autopatch server & dyndns play.exe 04/02/2009 - EO PServer Guides & Releases - 32 Replies Please see
http://www.elitepvpers.com/forum/eo-pserver-hostin g/297522-release-autopatchserver-3-0-a.html?highli ght=autopatch
[Guide] Autopatch server explained 01/22/2009 - CO2 Guides & Templates - 55 Replies If for some reason you want to set up your own autopatch server to go with your private conquer server, the following info should be all you need to get you going.
Update: Included an example of a working, but by no means complete autopatch server C# script, you can download it from the attachment, it's merely a demonstration to get you started.
All you need is a simple tcp/ip connection to the autopatch server.
(TQ's official server: 69.59.148.97 on port 9528)