- Joined
- Feb 2, 2011
- Messages
- 382
- Reaction score
- 200
I had some time today to throw the basic model together if it gets enough interest ill finish the final version + source.....
This is a test model for you to try if you want to hence the Pre Release in the Development forum
Client:
config file (ignore version file the patcher looks after that one)
edit the lines to suite your needs
change the patch URL to where you want to update from Note: needs the trailing /
Eg: PatchUrl=http://warrock.patch.ragezone.com/
Server side:
just upload the 2 files to the Patch Url you chose in above
Install:
Extract the Files to the Directory of the Client like so
link:
to make a patch create a zip file with the exact structure as the client
Zip contents Note no folder before the client structure.......
Eg:
music/Thema_1min.mp3
music/Thema28st.mp3
texture/1stPerson/arm_b.dds
texture/1stPerson/arm_b_knuckle2.dds
ect, ect.
once you have mad your patch rename the zip to 1.zip for 1st update 2.zip for 2nd ect, ect.
and edit the version.text file server side to meet the number of your patch.
so patch one = 1
patch two = 2
ect ect
this coding is the basis of which the final product will arise from.
(source to follow)
This is a test model for you to try if you want to hence the Pre Release in the Development forum
Client:
config file (ignore version file the patcher looks after that one)
edit the lines to suite your needs
change the patch URL to where you want to update from Note: needs the trailing /
Eg: PatchUrl=http://warrock.patch.ragezone.com/
Code:
PatchUrl=http://YOUR PATCH SERVER/
ServerKey=1d5856782db99133c224b4011b58fc620
WebSite=Not in Beta
Theme=Not in Beta
Server side:
just upload the 2 files to the Patch Url you chose in above
Install:
Extract the Files to the Directory of the Client like so
link:
You must be registered to see links
to make a patch create a zip file with the exact structure as the client
Zip contents Note no folder before the client structure.......
Eg:
music/Thema_1min.mp3
music/Thema28st.mp3
texture/1stPerson/arm_b.dds
texture/1stPerson/arm_b_knuckle2.dds
ect, ect.
once you have mad your patch rename the zip to 1.zip for 1st update 2.zip for 2nd ect, ect.
and edit the version.text file server side to meet the number of your patch.
so patch one = 1
patch two = 2
ect ect
this coding is the basis of which the final product will arise from.
(source to follow)