[1.8.x-1.12.x] Module Manager 4.2.3 (July 03th 2023) - Fireworks season

[blowfish]

[quote name='asgkatz']Is it ever necessary to have more than one version of the .dll? For example, if a certain mod comes with an older version? Or will it work fine with newest as well?[/QUOTE]

Like Sigma88 said, the newest will take priority, but it's good practice to remove the old ones too.

[Stone Blue]

^^
Is it generally the same case with KSPAPI Ext. as well?

Actually, is the election for newsest vers. a specific MM function, or generally a KSP built-in thing for all .dlls?...I'm guessing its the 1st case? Edited November 21, 2015 by Stone Blue

[BudgetHedgehog]

[quote name='sarbian']Both should work (unless I am missing something obvious). The log should tell you why it is not processed.[/QUOTE]

Would spelling mistakes have an effect? Both 'description' and 'resourceName' are spelled incorrectly.

[minepagan]

[quote name='sarbian']Both should work (unless I am missing something obvious). The log should tell you why it is not processed.[/QUOTE]
It still did not work - it was completely ignored. How do I access the log?

[Stone Blue]

^^
Pretty sure spelling and even case sensitivity matter for variable names....

You need the KSP.log in the main folder, for loading issues

[Mecripp]

[quote name='minepagan']It still did not work - it was completely ignored. How do I access the log?[/QUOTE]

Did you see the post above you [QUOTE]Would spelling mistakes have an effect? Both 'description' and 'resourceName' are spelled incorrectly. [/QUOTE]

wasn't really looking for what you was trying at first [code]+PART[linearRcs]
{
@name = airRCS
@cost = 200
@title = AIR-9000 Compressed air nozzle
@manufacturer = C7 Aerospace
@desctription = Designed for VTOLs and supermanuverable fighters, this nozzle functions like an RCS port, only it uses intake air!
@MODULE[ModuleRCS]
{
@resourceName = IntakeAir
@atmosphereCurve
{
key = 0 6400 0 0
}
}
}[/code]

@atmosphereCurve is that the only one you want or are you trying to add that one ?

EDIT- That part has this [QUOTE] atmosphereCurve
{
key = 0 240 <------- would be key,0 = *
key = 1 100 <----------- key,1 = *
key = 4 0.001 <-------------- key,2 = *
}[/QUOTE] Edited November 21, 2015 by Mecripp2

[lextacy]

also try

[I]$PART[/I] instead of +PART . Using the plus sign is not always stable. ALso is mecripp said, you need to" key" the atmosphere settings.

[minepagan]

[quote name='MeCripp']Did you see the post above you

wasn't really looking for what you was trying at first [code]+PART[linearRcs]
{
@name = airRCS
@cost = 200
@title = AIR-9000 Compressed air nozzle
@manufacturer = C7 Aerospace
@desctription = Designed for VTOLs and supermanuverable fighters, this nozzle functions like an RCS port, only it uses intake air!
@MODULE[ModuleRCS]
{
@resourceName = IntakeAir
@atmosphereCurve
{
key = 0 6400 0 0
}
}
}[/code]

@atmosphereCurve is that the only one you want or are you trying to add that one ?

EDIT- That part has this[/QUOTE]
1) Didn't see it, was ninja'd. (Noted, though.)
2)Is there any way to change it? I want it to have ISP like jets do, not rockets.....

[sarbian]

[quote name='lextacy']also try

[I]$PART[/I] instead of +PART . Using the plus sign is not always stable. ALso is mecripp said, you need to" key" the atmosphere settings.[/QUOTE]

Can you please not post FUD ? + works fine. Edited November 23, 2015 by sarbian

[lextacy]

how can I do a greater than less than operator ?

@PART
[*]:HAS[@RESOURCE[SolidFuel]]:HAS[#amount[[I][B]>349[/B][/I]]]

is this close?

[sarbian]

The brackets position are wrong. The amount test applies to the RESOURCE so you don t close the bracket there.

[code]
@PART[*]:HAS[@RESOURCE[SolidFuel]:HAS[#amount[>349]]]
[/code]

[Sigma88]

is there any way to check if two variables have the same value? (supposing they can be words, not only numbers)

[lextacy]

[quote name='sarbian']The brackets position are wrong. The amount test applies to the RESOURCE so you don t close the bracket there.

[code]
@PART
[*]:HAS[@RESOURCE[SolidFuel]:HAS[#amount[>349]]]
[/code][/QUOTE]

dang how could I have overlooked that , good eye bro

[Warzouz]

Is there a repository of simple scripts than intelligently tweak the game without changing the gameplay ?

[RadarManFromTheMoon]

I know it is possible to patch multiple parts by doing

@Part[parta|partb|partc]
{}

Is there a way to do the same but with modules instead? Like:

@Module[a|b|c]
{}

I tried and using "|" does not seem to work :/

I have a lot of PartModules on the same part that all derive from the same base class, so patching them all at once would make my life soo much easier. :D

[Sigma88]

[quote name='RadarManFromTheMoon']I know it is possible to patch multiple parts by doing

@Part[parta|partb|partc]
{}

Is there a way to do the same but with modules instead? Like:

@Module[a|b|c]
{}

I tried and using "|" does not seem to work :/

I have a lot of PartModules on the same part that all derive from the same base class, so patching them all at once would make my life soo much easier. :D[/QUOTE]

afaik there should be no difference between PART or any other module.

which values did you put in [a|b|c] ?

[RadarManFromTheMoon]

[quote name='Sigma88']afaik there should be no difference between PART or any other module.

which values did you put in [a|b|c] ?[/QUOTE]

[CODE]
@PART[*]HAS[@MODULE[ProceduralPart]]:FOR[ProceduralParts]
{
@MODULE[ProceduralShapeCylinder|ProceduralShapeCone]
{
%END_CAPS
{
CAPS
{
name=default
}
}
}
}[/CODE]

ProceduralShapeCylinder and ProceduralShapeCone are the names of the modules I try to add the default caps to.

Using a wildcard seems to work, but only with the first matching module.

[edit]

When I use @MODULE[*]:HAS[#name[ProceduralShape*]] instead of @MODULE[ProceduralShape*] (which are, according to the documentation, equivalent) it works fine.

[edit]

Also working: @MODULE[ProceduralShape*],*

Still no luck with: @MODULE[ProceduralShapeCylinder|ProceduralShapeCone],* Edited November 25, 2015 by RadarManFromTheMoon

[NathanKell]

I believe that @NODE[text] evaluates to @NODE:HAS[#name[text]]
And | in HAS only works for root nodes (@PART) not subnodes.

[Sigma88]

[quote name='NathanKell']I believe that @NODE[text] evaluates to @NODE:HAS[#name[text]]
And | in HAS only works for root nodes (@PART) not subnodes.[/QUOTE]

NODE[text] and NODE:HAS[#name[text]] should be the same but sometimes they behave differently

(When you change the name of a NODE for example)

not sure about the | thing, I thought it could be used on subnodes, I'll have to check if I've ever used it

[B]@RadarManFromTheMoon[/B]

Try with

@MODULE:HAS[#name[ProceduralShapeCylinder]|#name[ProceduralShapeCone]]

[HR][/HR]
I checked and I had already used[B] | [/B]in a subnode, but I never really tested to see if it worked or not

I'll test it when I get home Edited November 26, 2015 by Sigma88

[evileye.x]

I'm sorry for my stupidness, and all in advance.
I'm totally module manager noob, but I know it's an amazing moding tool and want to use it.

Is there's anyway to use conditions, let's say:
if
1) part is in SXT mod
and
2) has max tem >2400K
and
3) not a heatshield
then
maxtemp = maxtemp - 1000

Appreciate your answers, thak you in advance.

Hmm , looks the answer is exactly 1 page back :) I need to run tests
@PART
[*]:HAS[@RESOURCE[SolidFuel]:HAS[#amount[>349]]]

update - came up with
@PART
[*]:NEEDS[AIES_Aerospace]:HAS[#maxTemp:HAS[#amount[>2400]]]

{
@maxTemp = 2400}
does not work

update - solved!
[CODE]@PART
[*]:NEEDS[AIES_Aerospace]:HAS[#maxTemp[>2400],#manufacturer[AIES?Aerospace]]
{
@maxTemp -= 1000
}[/CODE]

MM Forever! Edited November 26, 2015 by evileye.x

[NathanKell]

Sigma: Yes, that's my point, they evaluate the same. Thing is, | doesn't work in child nodes' HAS blocks, only root node HAS blocks. So it doesn't work in subnode @NODE[foo|bar] either.

[Sigma88]

On 27/11/2015, 03:24:18, NathanKell said:

Sigma: Yes, that's my point, they evaluate the same. Thing is, | doesn't work in child nodes' HAS blocks, only root node HAS blocks. So it doesn't work in subnode @NODE[foo|bar] either.

I wasn't disagreeing with you on that point.

what I meant is, even if they are supposed to evaluate the same, they actually don't.

for example if you do this:

NODE
{
	name = firstname
	test1 = does it work?
	test2 = does it work?
}
@NODE[firstname]
{
	@name = secondname
}
@NODE[secondname]
{
	@test1 = it worked
}
@NODE:HAS[#name[secondname]]
{
	@test2 = it worked
}

you would expect to get something like this:

NODE
{
	name = secondname
	test1 = it worked
	test2 = it worked
}

but instead you get this

NODE
{
	name = secondname
	test1 = does it work?
	test2 = it worked
}

 

so there actually is a small difference between NODE[xyz] and NODE:HAS[#name[xyz]]

 

but regarding the "or" part you are completely correct, the operator | can't be used on subnodes

[NathanKell]

Huh. That looks like a bug then.

[sarbian]

An annoying one. Not sure if it will be an easy fix.

[evileye.x]

I'm trying to rebalance AIES engines ISP with MM patch.

The idea is

If Vacuum ISP >330 , then ISP = ISP *,9

@PART[*]:NEEDS[AIES_Aerospace]:HAS[@MODULE[ModuleEngines*],#manufacturer[AIES?Aerospace]]
{	
	@MODULE[ModuleEngines*]
	{
		@atmosphereCurve
		{
			%selectcur = #$key,0[1, ]$
		}			
	}
}	
@PART[*]:NEEDS[AIES_Aerospace]:HAS[@MODULE[ModuleEngines*],#manufacturer[AIES?Aerospace],#selectcur[>330]]
{
@MODULE[ModuleEngines*]
	{
			@atmosphereCurve
		{
			key0 = #$key,0[1, ]$
			@key0 *= 0.9
			@key,0 = #0 $key0$
			key1 = #$key,1[1, ]$
			@key1 *= 0.9
			@key,1 = #1 $key1$	
		}			
	}
}		

Doesn't work.

I don't get how to use conditions based on variables