We are glad about every suggestion and every criticism which serves to improve the BiG World Project.
Something that would be cool would be to make the mod-config/order/compatibility/etc in a format not specific to BWS or install.bat.. Preferably in human readable format; something like xml for example (this is just off the top of my head, I don't know how you've implemented this stuff currently, also I am probably missing hundreds of pieces of info that are neccessary):
<mod name="unique mod name, not the file name, no version number in name"> <version major="1" minor="2" revision="3" prefix="beta"> // acceptable version numbers <version major="1" minor="2" revision="2"> // acceptable version numbers <download>http://first.url</download> <download>http://second.url</download> <homepage>http://home.page</homepage> <config name="recommended"> <option name="some install choice">2</option> <option name="some install choice">1</option> <conflict name="some other mod name"> <option name="some install choice">other mod choice</option> <option name="some install choice">other mod choice</option> </conflict> <src>file name to write on disk locally</src> <patch>patch file<patch> </mod>
Then BWS, or any other install script could just download the latest config and patches the first thing it does making sure that you get the latest files and patches. You could also keep a stable and a current version of the file to allow the user to have bleeding edge or not..
Anyways, it's probably way to late to integrate that as I'm guessing to implement something like that would mean rewriting too much; esp when the main benefit is for people who want to use your hard work on patches, compatibility checks and install order for their own.. I'm just going to suggest it anyway if you ever feel bored and want something to do
Thanks
j