[Only registered and activated users can see links. Click Here To Register...]
Introduction
With that system, its easy way to orginize updates of pserver. The system is very simple to understanding and working.
Manual
In archive, there are two folders - "Client side" and "Server side".
Lets check out Client side:
app.ini - information in this file, let know to M2SU, which client's lauch file (ex. "metin2client.bin")
lng\config.inf - let know to M2SU, which localization file to be used.
lng\...ini - M2SU localization file.
update.ini - this file contain current version of client (ex. "1.0")
update.add - update server URL (ex. "http://yourdomain.ru/update/")
metin2.exe - M2SU executable
Server side:
index.html - web page, displayed in small M2SU's web browser
update.ini - this file contain current version of update (ex. "1.1")
update.zip - ZIP-archive with update files
Setup
Move "Client side" to client folder. In all system files, define data. (c.o Manual).
Server side, must put to public folder on http server.
Updating
If you want release an update to your clients, you must pack update files into a zip-archive. After that, you must put zip-archive to server side. Also, you must set current version of update in update.ini file. For example: if current version of client is 1.0, on the server side specify the version 1.1. I hope the meaning is clear.
How it works
M2SU read config file on client side, and read config file on server side, if the version conf. client's file often less than the server's conf. file, then there is an update notification. When updating, M2SU download update file on server side, and unpack it to client's folder with overwrite. After that, M2SU move update file to folder named as "Updates".
