quote:
I can leave the mod the way it is, and include in the mod data dirctory a file called NeoVehicleSize.txt. This file will be identical to the regular mod VehicleSize file, but using the NeoStandard shippic names instead. Then we write the utility to copy all the bitmaps and copy the Neo file over the regular mod VehicleSize file.
Excellent Idea. The Last line of the utility can copy the vehiclesize to a backup, then write over it with NSVS.txt.
quote:
One other thing. The utility will be writing the over the pic files in the mod directories, not the default SEIV directory right? Even though the pics are new pics and not overwriting exsisting files, we shouldn't be messing with peoples default directories.
The utility will never overwrite an existing file, except maybe the vehiclesize.txt as above.
If that's not enough, run it from the mod folder, and I'll have it look into the .\pictures\races folder and upgrade all the races it finds.
Now there is still the question of space. If we drag copies of all the races in the default directory out into mod folders, we'll have Andrés problem multiplied by the number of mods
quote:
A little over 1 mb more for each shipset, that means that if I wanted to upgrade every shipset I have installed (131) I would run out of disk space.
quote:
Maybe this will complicate the program too much, but could it look into the VehicleSizes.txt and only copy pictures that are referenced there?
Better yet (and simpler, too), I could just read from a mod-specific .INI file (a subset of our full .INI, leaving out some image definitions). The modder could specify which of the standard's images are required, and also which images to take as secondary choices.
This might weaken the standard a bit, since modders could define their own set of required images, but shipsets would be coming out with standard images, and it would be a bit of work to alter on your own. (Deleting sections that don't apply to your mod is easy, but adding a few new ones takes more time)
Decision time.