When they made New Horizons, they copied the modules\rigging.dll a bunch of times, then used a HexEditor to change the class name inside the .dll binary file. As a favor to allow Maelstrom to possibly be used similarly, I added features to rigging that would emulate the same behavior, but it requires different scripting and also modification to rigging.ini; I am not going to hex-edit the .dll files like they did, but instead provide the functionality that they were trying to achieve, but in a more proper manner, through features inside the engine/modules.
Use a visual file difference tool (like WinMerge) to compare that AIShip.c to the modified one we supply. Also compare the RESOURCE\INI\rigging.ini the same way and make the same changes in our version to the New Horizons version.
There are also similar issues with the LogInterface, where the original engine only allowed one instance of it, but New Horizons copied the .dll and hex edited it. So I added a way to achieve that too. This is why you need to compare all files in two versions and find the changes needed to make it work for Maelstrom (both programs, INI files and in some cases RESOURCE files that need to be moved to different directories).
