|
NimrodX -> RE: Edit Database (6/3/2018 8:36:52 AM)
|
The MegaFAQ has the answer.
Note that you have some ability to modify units using the scenario editor, and you can export ".inst" files with your modifications that you or others can then import into a scenario.
So there are still some things you can do. For example you can create a Spy unit (Facility) in the scenario editor, rename it to "Blind Radio Ninja", take away his eyeballs, and give him a pile of ELINT gear and comms devices. But you can't change his maximum speed to reflect his limited mobility due to his blindness. (Maybe there's some way to do this in some indirect way like adding damage to him, but if so I don't know what it is.) Also, the player will see a link to the Spy in the database, not a Blind Ninja, and the database viewer will show the standard specs for a generic spy.
If you wanted to reduce his mobility zero you could add a small hard to see building, remove the autodetect flag from the building so enemies don't see it unless spotted, rename it to "Blind Ninja's Radio Shack" and add lots of ELINT and comms to it. But you wouldn't be able to lower the visual detection range to near zero like the Spy unit (unless there's some sort of "invisible building" that I haven't even looked for.) Also the player will see a link to the generic building in the database.
Baloogan has some good videos on inst files and doing this kind of thing where he adds tanks and MLRS to the back of a Littoral Combat Ship for example.
If you just "hack" the database directly then maybe you'll get it to work for yourself but even without licensing issues others will have a hard time trying to use your scenario and probably won't want to bother to try to "hack" your database into working, especially if it screws up other scenarios. Also, if using Steam then Steam will detect a bad file hash (especially if "verify integrity of local game files" is run manually) then delete and redownload the "damaged" file.
|
|
|
|
