it does neither… it only checks MODs that have a MOD Version Check file included.
If you install a MOD that has a MOD Version Check file included, you'll want to install this to make sure you keep it up to date
How about a method that doesn't involve two extra files that need to be kept updated for every version? The existing installation instructions should have all the required info save for the remote location of the XML version file. So what about just having MOD authors add one line to their instructions specifying this location, like:
Code: Select all
<instructions href="http://www.example.com/install.xml" />
Then use the database to keep track of local version numbers. Have the user extract the MOD to the mods directory, where your script will scan whenever the user clicks on the tab. It can even break them down into categories: MODs that are stored in the database and in the directory, MODs in the database that aren't in the directory, and MODs in the directory that aren't in the database. Or for a simpler implementation, just have the user browse to the install instructions file they want to add.