Hello e*pvpers!
As I haven't really found a thread with a proper guide on how to do so, and you guys probably don't want to browse through thousands of pages in other threads, I'll write a guide on how to enable the autoupdater via SMC for your vSRO private server.
The very first step you need to do is to go to the SMC folder and create two simple folders named the way you see below:
Open up your smc_updater.cfg file and change the IP that is there to your server IP - this way the update will be done for your server.
After creating these two folders and figuring out what you want for your users to get when they launch your server client launcher, extract the necessary files from your client and place them into the Patch_Internal folder.
Make sure to create proper subfolders in the Patch_Internal folder - most likely you don't know how to do so, therefore I will provide an example based on a Media.pk2 file update, which is textuisystem.txt file. As you might or might not know, the file is located in Media.pk2 under the server_dep/textdata entry, so you have to recreate the categories in your Patch_Internal folder.
When done properly, it should look like that:
[Only registered and activated users can see links. Click Here To Register...]
So if you want to patch a file in your client, let's take textuisystem.txt for an example, you put it in the right path that is exactly the same as in media.pk2 or any other file you want to update.
After you have placed the files in the right folder, next thing you have to do is of course run your server. After your server is running, launch SMC and click on the ModulePatch tab and then SR_Client entry, next right click on it and select SR_Patch:22. Read the patch data(using a button, as there is a button you need to click in order to do so), click Analyze, specify your new client version, for example if you want your update to be marked as v1.202 then you type 202 as the version.
[Only registered and activated users can see links. Click Here To Register...]
When you've done all the stuff above, just simply upload the patch by clicking the Upload button. While you're done with SMC, let's head to the database then. In the SRO_VT_ACCOUNT database, open up the table named ModuleVersionFile. In that table you will find a record named as nToBePacked with the number of 0 for your newly uploaded files. Change 0 -> 1 and you're almost there.
The very last steps that you need to follow are really simple - close your DownloadServer & GatewayServer and simple re-run them. Once you've done that proprely, your new patch should be downloaded if user's client version is lower than the one specified in SMC & database.
I hope this tutorial helped you to enable the autoupdate function for your server client.
Thanks for reading!
As I haven't really found a thread with a proper guide on how to do so, and you guys probably don't want to browse through thousands of pages in other threads, I'll write a guide on how to enable the autoupdater via SMC for your vSRO private server.
The very first step you need to do is to go to the SMC folder and create two simple folders named the way you see below:
Code:
Patch_Internal Patch_Internal_Comp
After creating these two folders and figuring out what you want for your users to get when they launch your server client launcher, extract the necessary files from your client and place them into the Patch_Internal folder.
Make sure to create proper subfolders in the Patch_Internal folder - most likely you don't know how to do so, therefore I will provide an example based on a Media.pk2 file update, which is textuisystem.txt file. As you might or might not know, the file is located in Media.pk2 under the server_dep/textdata entry, so you have to recreate the categories in your Patch_Internal folder.
When done properly, it should look like that:
[Only registered and activated users can see links. Click Here To Register...]
So if you want to patch a file in your client, let's take textuisystem.txt for an example, you put it in the right path that is exactly the same as in media.pk2 or any other file you want to update.
After you have placed the files in the right folder, next thing you have to do is of course run your server. After your server is running, launch SMC and click on the ModulePatch tab and then SR_Client entry, next right click on it and select SR_Patch:22. Read the patch data(using a button, as there is a button you need to click in order to do so), click Analyze, specify your new client version, for example if you want your update to be marked as v1.202 then you type 202 as the version.
[Only registered and activated users can see links. Click Here To Register...]
When you've done all the stuff above, just simply upload the patch by clicking the Upload button. While you're done with SMC, let's head to the database then. In the SRO_VT_ACCOUNT database, open up the table named ModuleVersionFile. In that table you will find a record named as nToBePacked with the number of 0 for your newly uploaded files. Change 0 -> 1 and you're almost there.
The very last steps that you need to follow are really simple - close your DownloadServer & GatewayServer and simple re-run them. Once you've done that proprely, your new patch should be downloaded if user's client version is lower than the one specified in SMC & database.
I hope this tutorial helped you to enable the autoupdate function for your server client.
Thanks for reading!
