mercredi 15 novembre 2017

[1.3] Real Fuels v12.2.3 July 30

First: I suggest you do NOT implement your new resource by editing other mod files. Sooner or later they will be updated and your changes will be erased forcing you to reimplement them all over again.

Instead you should create your own resource config file for the basic resource definition.

For the tanks you should patch them using a Module Manager patch. Your resource definition file and your patch files should live in a single folder that you can back up and move around (such as to new KSP installations when you update KSP)

If the new resource is to be cryogenic then it should not (at this time) have an hsp value.

For the tank definition patches see the example below where the new resource is called deltaWeeResource (the example assumes a like named RESOURCE_DEFINITION)

@TANK_DEFINITION[Default]

{

TANK

{

name = deltaWeeResource

mass = 0.000012

utilization = 1

fillable = True

amount = 0.0

maxAmount = 0.0

}

}

That patch adds a new tank to the Default tank type that can be filled with the deltaWeeResource. In the game every default tank can now be configured with that resource. You would need to do the same with every other tank type that you want to be able to contain the resource. (i.e. Cryogenic, Structural, Fuselage, etc etc)[1.3] Real Fuels v12.2.3 July 30

---------------------------------------------------------------------------
Visit this link to stop these emails: http://zpr.io/nfAVj

Aucun commentaire:

Enregistrer un commentaire