Quote Originally Posted by bbrass10
A mod installer/uninstaller/launcher would be a tool that works like InstallShield. It would allow modders to "package" their mods along with a set of rules as to how they should be installed, and distribute that package to end users. When the users install the mod, the installer would track changes to the installation like a version control system, so that it can revert back to any previous state. Duplicate files like "readme.txt" would be archived rather than overwritten, so that the user can access them by mod name and version. It would also install a program launcher which allows any given mod or set of mods to be selected via a command line option, which would be used by shortcut icons on the desktop and in menus. The launcher would perform any necessary preparations prior to launching the application. Of course, the installer would include an uninstaller, as well as a "system restore"-style utility that reverts the application to a previous state in case something goes awry.
This sounds ambitious so good luck to you!

One thing that would concern me is, unlike normal version control systems, you will not have exclusive control over the items you are versioning. For example, how will your system cope with the user installing a CA patch that changes files you have versioned? Doesn't it break down at this point?

I'm also not sure how many modders would use your proposed packager - they can be a conservative bunch and tend to like to do things their own way.