This version of the script is for the original M&B. For the Warband version, head over here.
Download v1.9 Here
Updated 11-17-2008: v1.9 is now available.
v1.9:
- Much more robust support for Steam installations of M&B, both full version and demo. Steam apparently stores pseudo-registry files which contain the M&B registry info (found in "<Steam_path>\appcache" as "app_22100.vdf" and "app_22110.vdf"), so these are found and read. The install folder is therefore determined rather than guessed, and the M&B version number (ex. "1010"/"1.010") installed through Steam is also determined.
- Steam M&B version and any existing standard (TW) installation of M&B are now both checked against the version the mod is made for, since the Steam M&B version can now be found. If both installations exist and their versions both match the one which the mod was made for, the standard installation will be defaulted to instead of the Steam installation.
v1.8:
- Updated version display to properly indicate newer versions, i.e. "1.011" instead of "0.1011".
- Added in detection method for Steam installations of M&B if it isn't found elsewhere; Steam annoyingly doesn't store the M&B path in the Registry, but it does store its own path, which is extrapolated from to get the Steam M&B installation folder.
- Version mismatch warning message is updated to indicate possible Steam installation if version match isn't found; sadly, Steam also doesn't store the M&B version number in the Registry either.
- Special case added in for 1.010 and 1.011 to have them detected as compatible.
- Installation notes (in "install.txt") again slightly revised.
-----------------------
You know the main Mount&Blade setup executable which installs the entire game? It steps you though the installation, asking for the install directory, installing, and creating an uninstaller.
Well, the installer they use was created with the Nullsoft Scriptable Install System (NSIS), which is a free open-source program that I myself have used in the past to create installers for a couple of programs.
Once you've created an installer executable for your mod (which is pretty easy), it will automatically detect where the person installing your mod has M&B itself installed (it gets this from their registry), and defaults to the proper directory.
For example, if your mod was titled "My Cool Mod" and the person had M&B installed to "D:\Games\Mount_Blade 704", it would default to "D:\Games\Mount_Blade 704\Modules\My Cool Mod" for the mod installation directory.
Also, when creating your new mod directory, it will actually first copy over all the files from the "Native" module folder before overwriting with your mod files. That way, you can choose to only include the files your mod changes if you want.
Download v1.9 Here
Updated 11-17-2008: v1.9 is now available.
v1.9:
- Much more robust support for Steam installations of M&B, both full version and demo. Steam apparently stores pseudo-registry files which contain the M&B registry info (found in "<Steam_path>\appcache" as "app_22100.vdf" and "app_22110.vdf"), so these are found and read. The install folder is therefore determined rather than guessed, and the M&B version number (ex. "1010"/"1.010") installed through Steam is also determined.
- Steam M&B version and any existing standard (TW) installation of M&B are now both checked against the version the mod is made for, since the Steam M&B version can now be found. If both installations exist and their versions both match the one which the mod was made for, the standard installation will be defaulted to instead of the Steam installation.
v1.8:
- Updated version display to properly indicate newer versions, i.e. "1.011" instead of "0.1011".
- Added in detection method for Steam installations of M&B if it isn't found elsewhere; Steam annoyingly doesn't store the M&B path in the Registry, but it does store its own path, which is extrapolated from to get the Steam M&B installation folder.
- Version mismatch warning message is updated to indicate possible Steam installation if version match isn't found; sadly, Steam also doesn't store the M&B version number in the Registry either.
- Special case added in for 1.010 and 1.011 to have them detected as compatible.
- Installation notes (in "install.txt") again slightly revised.
-----------------------
You know the main Mount&Blade setup executable which installs the entire game? It steps you though the installation, asking for the install directory, installing, and creating an uninstaller.
Well, the installer they use was created with the Nullsoft Scriptable Install System (NSIS), which is a free open-source program that I myself have used in the past to create installers for a couple of programs.
Once you've created an installer executable for your mod (which is pretty easy), it will automatically detect where the person installing your mod has M&B itself installed (it gets this from their registry), and defaults to the proper directory.
For example, if your mod was titled "My Cool Mod" and the person had M&B installed to "D:\Games\Mount_Blade 704", it would default to "D:\Games\Mount_Blade 704\Modules\My Cool Mod" for the mod installation directory.
Also, when creating your new mod directory, it will actually first copy over all the files from the "Native" module folder before overwriting with your mod files. That way, you can choose to only include the files your mod changes if you want.
