I think most (some?) modmakers now use Matryx's modinfo format in order to make full use of the mod picker.
I imagine the procedure for my suggestion would be something like:
-Launch program.
-Program searches through directories and finds (for example) Vikings directory.
-Program looks in Vikings directory for updateinfo.txt
-Program finds Vikings/updateinfo.txt and gets the following data:
Current Version: 0.92
URL:
http://www.sandman43.fsnet.co.uk/fil...ate_viking.txt
-Program goes to specified URL and finds another text file. That text file gives the following information:
Latest Version: 0.93
File location:
http://www.sandman43.fsnet.co.uk/files/viking0_93.zip
Size: 0.61meg
-Program has all the data it neds: Reports back to user.
"There is a more recent Version of the
Viking race style.
Current : 0.92
Latest : 0.93
Filesize : 0.61meg
Location :
http://www.sandman43.fsnet.co.uk/files/viking0_93.zip
Do you want to update it now? [Yes] [No]"
- User clicks "yes", and the program downloads the file and unzips it to the correct location. Bosh, job done.
Obviously the program would search for more than one update at a time, and the interface would be a bit more sophisticated, but you get the idea.
The racemaker / modder would be responsible for putting an accurate updateinfo.txt
in their zip file, and for maintaining the update_XXXXXX.txt file on their website. Just a couple of text files.
It all sounds plausible to me (but then I'm not a programmer=-)
------------------
SE4 Code:
L GdY $ Fr- C- Sd T!+ Sf-- Tcp-- A% M>M+ MpD! RV Pw Fq+ Nd- Rp+ G-
/SE4 Code
Go to
my meagre SEIV pages to generate your own code.