Not to steal anything from t0rento. I worked on this before I knew of his utility.

This is a command line utility that updates build 18 and 19 mods to version 20, using a simple find-replace list.

To use, extract and make a link to the executable on your desktop. Open the Cortex Command folder and select the modules you want updated. Drag and drop all of them at once onto the icon. The application will update all of them and give conversion times. Or, alternatively, just run the application--it'll list all modules in the root CC directory and you can enter their module names to update, to exit the loop hit enter or type exit or quit.

Wasn't aware anything needed to be changed, aside from the whole null.bmp thing (which is avoided if you do a clean reinstall).

The purpose of the application isn't primarily updating build 19 mods, though it does that too by proxy. It's two additional lines to add to the update definitions. No biggie. The primary purpose of the application is to update build 18 mods to 19/20 compatibility ... which it does with good speed, ~45ms to update the USC halo mod.

I was in a hurry, I've been AFK for the past 7 or so hours, so I forgot to mention that the application requires .NET 2 or higher--still unused to language transitions and requirements.

I don't care if another one released etc, but do you think you could provide the source code?

I always seem to discover new tricks where myself and another person code a similar application.

Edit:
Odd that the conversion file uses the same character for string separation as mine

Coincidence I guess.

If you add stuff to "update.txt" will it be included in the conversion? if so then this is by far the best one made so far, when new things are added, *BAM* changed, successfully converted.

Didn't think so, it's mostly just an automated-recursive find-replace tool. Not something difficult like a map editor like ChJees is talking about.

My two choices were either the pipe or semicolon. I just did a find-replace and used the pipe in the list. Both pipes and semicolons aren't permitted in file names, so either work. Luck of the draw I guess.


Just a warning, this is my first serious .NET executable and I'm adapting from a non-NET/Assembly style and compiler to a whole new style of environment. So things aren't clean, neat, or well organized. But it should be legible enough. I program in Object Pascal with the Chrome VS2008 plugin language, so look up "program.pas" and "cortexcommand.pas" for the bulk of the sourcecode.


Correct; t0rento's and mine do this.