ModuleManager – ‹module-1› OR ‹module-2›

[Teilnehmer]

I have a .cfg file consisting of two conditions with identical bodies:

@PART[*]:HAS[@MODULE[ModuleCommand]]:Final
{
  . . .
}

@PART[*]:HAS[@MODULE[KerbalSeat]]:Final
{
  . . .
}

Can I combine them into a single condition?

I tried

@PART[*]:HAS[@MODULE[ModuleCommand]|@MODULE[KerbalSeat]]:Final
{
  . . .
}

but this didn’t work.

Edited October 24, 2018 by Teilnehmer

[JadeOfMaar]

@Teilnehmer Remove the [*] in the second code block. it will help and should work.

[Teilnehmer]

Could you please explain? As far as I understood, @NODE[*] edits all NODEs containing a Name key, but I haven’t found in the documentation what exactly @NODE without [*] edits. What’s the difference?

[JadeOfMaar]

@Teilnehmer Certain nodes, "root nodes" which have no parent, do not need a [*] to be used to target them all. ModuleManager even considers this bad syntax for these, and this is known to break mods that target all science experiment definitions (well, this makes perfect sense as those don't contain a Name key).

[Teilnehmer]

And why should I remove [*] in the second code block only?

[JadeOfMaar]

This should be done with any code block, but I only mentioned the second one as that's what will allow for your OR condition with the patch.

[Teilnehmer]

Sorry, I don’t quite get it. What the resulting patch will look like?