Ok, there's 2 things here that can get kinda mixed up...
1. Module tags can have any name you like, as long as that object doesn't have another with the same name. So you could name it anywhere from "ModuleTag_05" to "AnotherModuleTag" to "WhatsInAName".
2. The files that are in the object and in the mappedimages folder can be any name you want. You can also create your own folders inside Object or MappedImages if you like, and stick your files in there. The game will automatically read ALL files and folders in there regardless of their names. So you could have "Data/INI/Object/NewSide/MynewsideInfantry.ini", or "Data/INI/MappedImages/NewCameoStuff/MyCameos3.ini".
There is one BUT though: The new file will only overwrite the old one if it has the same name! So if you make a new object called "AmericaTankCrusader" in a file called "Whatever.ini", then the game will read your unit from Whatever.ini and then, after that, it will read its own built-in AmericaVehicle.ini and replace your unit with the standard Crusader. The only way to prevent this would be to extract the original AmericaVehicle.ini to the right folder, and remove the Crusader's code from it. The game will not read its internal files if it already found one with the same name in Data/INI/Object or in Data/INI/MappedImages, so it will not overwrite your unit with the old Crusader.
|
UpgradeCameo for the specific object
