Tweet
I don't know enough perl to do this myself, but I wonder how hard this would be:
A MOD manager mod
I see this as a button added to the main menu to access a mod management menu.
The mod management menu would have options to add, delete, or update an existing mod.
Mods would be specified by name and url location to download it.
Of course, the system would have to know the different archiving/compression routines and how to 'unzip' them into the correct location, with the mod folder name being the name specified earlier.
There could also be a checkbox to 'update all mods', in which case every currently installed mod's location url would be checked for a new version and automatically installed.
There should also be some uniform text file included in the archive which specifies the version, perhaps what other versions the new update is backwards compatible with, etc.
That way if the new version breaks something in save games from the currently installed version, it could prompt the user before overwriting, maybe with an option to install but with the version tag added to the name so the user can select which one to use.
Anyone think there is any value in something like this? And anyone want to volunteer to make it happen?
I think someone who knows perl should be able to do this rather handily.
A MOD manager mod
I see this as a button added to the main menu to access a mod management menu.
The mod management menu would have options to add, delete, or update an existing mod.
Mods would be specified by name and url location to download it.
Of course, the system would have to know the different archiving/compression routines and how to 'unzip' them into the correct location, with the mod folder name being the name specified earlier.
There could also be a checkbox to 'update all mods', in which case every currently installed mod's location url would be checked for a new version and automatically installed.
There should also be some uniform text file included in the archive which specifies the version, perhaps what other versions the new update is backwards compatible with, etc.
That way if the new version breaks something in save games from the currently installed version, it could prompt the user before overwriting, maybe with an option to install but with the version tag added to the name so the user can select which one to use.
Anyone think there is any value in something like this? And anyone want to volunteer to make it happen?
I think someone who knows perl should be able to do this rather handily.