This package contains all available MechCommander modding tools. Some are more or less useful - well i put them all in one package. Have fun modding MechCommander!
Hello dear MechCommander Modders,
those are all MechCommander modding tools i could find and used past half decade. This package contains those tools:
The Tigress tools may work on a regular Windows Desktop. The MC Modding tools you have to use via DOS-console - command prompt. Those are really mighty tools that saves MechCommander Modders allot of time cause they offer automated processes for autistic circling processes you need to have to do before you can do what you want to do while modding MechCommander.
This folder contains the most wanted tigress tools from NGNG. I never used it - i make my changes manually - and i leave game physics 100%
vanilla this way, cause the files allow colossal gameplay changes (weapons, mechs, pilots, vehicles)...
Be careful when using this! This is not well tested beta stuff. Some forum information says the executables only work from main folder -
some say they only work when they are put into Data subfolder...
I could work with the control panel (it starts the other submodules),
and MCG-Tools - which is actually a file extracting/compressing tool for
*.FST and *.DPK - mission files - so this was very useful to me cause it
spares time and some steps you would need to do between when using cMunsta
I placed them in both "ROOT\" / "ROOT\DATA" - somehow i got some errorreports using
the submodules of the mechcommander control panel.
**From original cMunsta extract** Just a quick note to say what the format for the file list used by MAKESOL and MAKEFST is as follows: u filename c filename The first letter is a command to say if the file should be compressed or not. (u = uncompressed, c = compressed). The filename can be any file relative to the directory to tool is in. That is, if the tool is in the MechCommander Gold game directory, the the tool will have access to all files in this dir and all subdirs below it. Do not use a ".\" in front of the filenames. If you wanted to access say, "test.abi" in ".\data\missions", then the filename to use would be data\missions\test.abi Note that this precludes having spaces in the filenames. The list should have one command/filename pair per line, the command should be at the start of the line.
(c) by RizZen 2020