This project automates most of the conversion work required to convert the legacy Cortex Command mods into Cortex Command Community Project compatible mods.
Put the mods you want to convert in the input folder and run convert.py. After convert.py is done, the converted mods are found in the output folder and can then be tested in CCCP.
This program will do most of the conversion work for you, but some conversion steps are too hard to automate, so it's likely that CCCP will still crash and/or output errors into the console. If this happens, you'll have to manually make some final adjustments to the converted mods found in the output folder.
"There are going to be cases that require user intervention. Priority, for example, is one of them. Few things should be setting sound priority, and the scale has completely changed such that 0 is highest and 128 (I think) is lowest. The correct way to deal with this is, either at the time of or at the end, show the user these cases and either tell them to deal with it manually, or give them a few options." -Gacyr
- Download Python3, and change directory to the
cc-legacy-mod-converterfolder - Run
python convert.pyif you want to convert old mods conversion_rules.pyhas theconversion_rulesdictionary inside of it. The dictionary contains entries that look like'foo': 'bar',which means means that any timefoowill be encountered byconvert.py, it will replace it withbar. You can add extra cases to it, see the next sections on how to do this.
Feel free to submit Pull Requests or Issues on this GitHub project for any additional cases that you'd like to have supported.
You don’t need all of these programs to get started, feel free to use whatever alternative programs you prefer:
- Download “Everything” - It’s like File Explorer on Windows, but way faster + more advanced.
- Download “SourceTree” - It’s like GitHub Desktop, but way more advanced.
- Download “NotePad++” - It’s like Notepad, but way more advanced (hence ++). You can also use an IDE like VS Code instead.
 |
|---|
| Let's say you've converted your old mod, but Cortex Command still crashes with the converted mod. |
 |
|---|
| The first thing you should do is open up the program Everything, which is used to search for any file on your computer, while also being much faster than Windows's standard File Explorer program. |
 |
|---|
You can now click the Search button at the top of the program, then Advanced Search..., and then you can type what you want to search in the all these words: field. If the your search result should contain multiple keywords, you can just place a space character between those keywords. |
 |
|---|
| As you can see, there are way too many results for this search, so we'll have to narrow down the search. |
 |
|---|
By adding the Ronin.rte\ keyword (the \ is really important to indicate it's a folder!) there's only a single search result left, which is our new path we were looking for. You can verify if this path leads to the same image as the original, Steam version of Cortex Command did if you want to make extra sure this is correct. |
 |
|---|
Open conversion_rules.py with any text editor of your choice, and add '': '', somewhere in the conversion_rules dictionary. In the left set of '' you want to add the old path which couldn't be found, which should have been mentioned in your error. In the right set of '' you want to add the new path you've obtained with Everything. |
Now run convert.py again, and it should automatically fix the error for you by replacing any mention of Ronin.rte/Effects/Gibs/GibA.bmp with Ronin.rte/Devices/Shared/Gibs/WeaponGibA.bmp. The main advantages of creating a case in the dictionary - instead of manually replacing any mention of Ronin.rte/Effects/Gibs/GibA.bmp - are:
- Being able to create a Pull Request on GitHub of that new case you added, which can then be used by the rest of the converters. If everyone were to make a Pull Request for every single case they found, the converter would become way more effective.
- If there are multiple locations where
Ronin.rte/Effects/Gibs/GibA.bmpis mentioned, you don't have to search for every single mention of it in every single file. Manually mass replacing stuff can be messed up.
If you need help with anything, you can contact the creator of this repository directly (#MyNameIsTrez1585 on Discord), or you can ask the kind people in the CCCP Discord server in #modding-discussion for help. It helps us if you mention where you've gotten stuck while reading this README file.