PartModules, Required Inputs and isAlwaysActive only for ModuleGenerator?

[Roboto]

Regarding calls to requiresAllInputs and the associated INPUT and OUTPUT_RESOURCE, as well as isAlwaysActive, are they specific to the ModuleGenerator, or can we use them in modules that are not declared as ModuleGenerator?

Sorry if this has been covered before, I have done a few searches and was unable to find anything on that topic.

[Greys]

Ok so let's take a step back.

since KSP 0.20.0 everything in a cfg file is either a config node, or in a config node, in most cases where addons are involved that's PART{}

Everything inside a config node defines information about that config node.

So when you say PART{name = bedazzle}, you're setting the variable "name" in that particular instance of PART{} to "bedazzle"

Here's the trick. You can set any variable you want, and you can set it to anything you want to.

But if the code associated with the confignode you do it in does not know to use that variable, it won't do anything.

PART{bandana = banana} is totally valid and won't throw any errors at all.

PART{}, INTERNAL{}, PROP{}, ATTACH{}, MODEL{}, RESOURCE_DEFINITION{} and RESOURCE{}, all have specific code associated with them, but MODULE{} doesn't, the code associated with MODULE{}, and thus the code that uses the variables you set in it, is determined by MODULE{name}

So yes, you can set requiresAllInputs, input_resource, output_resource, and isAlwaysActive literally anywhere you want.

'S'not gonna do anything most of the time.

Edited September 1, 2013 by Greys

[Roboto]

Ok thanks, Greys, that's what I was getting at... I wasn't sure if they actually were usable with all partmodules or not. I see now that they are not, and have to be defined properly. Now that I'm looking at monodev and plugin development, I'm beginning to see how I can actually build out what I'm looking for.

Thanks for the help.