Quote Originally Posted by bbrass10
I'm not proposing a mod switcher or mod manager. Those tools place the burden of managing mods on the end user. In this thread, a modder has already asked which additional files from the root directory will be required for any given mod; can the end user be expected to configure issues like that?

I'm proposing a packaging and deployment tool for modders, much like a simplified "InstallShield" tool designed specifically for M2TW.
Nice idea - this is a different approach to MedManager, which is a "mod switcher/mod launcher".

For many (most?) mods, installation can just be a case of file copying, which can be accomplished via a self extracting zip. An installer is useful if it can auto-detect the location of the M2TW directory, and for creating launch and removal icons. For MedManager I've assumed the user is able to extract a downloaded mod to the right directory, and MedManager takes care of the rest (creating the icon, cfg file etc).

The need to copy some files from the base install is for me still a bit problematical. Some files are definitely needed, others are optional but useful. For example, all the fmv stuff if you still want assasination etc movies. I was hoping the patch would remove the need to copy these at all - if they are in the base install, why can't the engine find them there?

Any way, I wish you luck!

I would also like to point out to everyone in general that there is no need to create a bat file for a mod - just create a Windows shortcut directly to the medieval2.exe, and add "@Mymod.cfg" to the Target in the shortcut properties, where Mymod is the name of the mod.