complynx

The only mod to make really not-a-window-long part's options and part manipulation from anywhere. Very nice indeed. Love this mod. One question to a creator: it has been a while since 1.1.3 has been released and there is already a 1.2 knocking around. Will there be any changes? Will there be a new release? I hope, 1.1.3 works fine, I have a doubt about 1.2. Is there any WIP behind the scenes?

How to make different surfaces passable and impassable at the same time for surface attached parts. This will be very useful for some parts like MK3 ones, they have flat surfaces, which are great for being passable ones. Example in the attached link. https://imgur.com/gallery/vuwW5

@PART[Multiport-a] { @bulkheadProfiles = size0,size1,size2,srf @MODULE[ModuleDockingNode] { @nodeType = size0,size1,size2 } } @PART[Multiport-b]{ @bulkheadProfiles = size0,size1,srf @MODULE[ModuleDockingNode] { @nodeType = size0,size1 } } @PART[Multiport-a]:NEEDS[ConnectedLivingSpace]:HAS[!MODULE[ModuleConnectedLivingSpace]] { MODULE { name = ModuleConnectedLivingSpace passable = true passableWhenSurfaceAttached = true } } @PART[Multiport-b]:NEEDS[ConnectedLivingSpace]:HAS[!MODULE[ModuleConnectedLivingSpace]] { MODULE { name = ModuleConnectedLivingSpace passable = true passableWhenSurfaceAttached = true } } This will add capabilities of multiports to interconnect with all stock ports. And CLS support.

Hi everyone! I'm fascinated about this mod but recent investigations come out with the question: Is there a reason to not make launch clumps a "resource generator" for TACLS like they are for electricity? While waiting for a transfer window on a ground it is quite useful.

Thank you for your answer. For the first two cases, I can use regexps nevertheless, but is there any other solution? In case of splitting parsing into two cases depending on just recently added variable? For the second case, maybe there is a better solution to distinguish these situations: to use regexp variable extraction or to use escape sequence? If the dollar sign is appeared twice it will be replaced as dollar sign, otherwise it is considered as a variable. And a variable replacement is to be done before regexp or other expression. So for my case the solution would be: @var_to_update ^= #:^.*$$:$$0;$var_to_paste$: and the process in the parser: 1) Is there a hash at the right side? 2) If no hash, skip to 4 3) Find every /\$([^\$]*)\$/ and replace with var referenced by the first match if it is not empty, else replace with $ 4) Do the expression stuff. In this case regexp replacement.

Propose: add Connected Living Space compatibility. I made a fast draft on it and pulled a request. https://github.com/SuicidalInsanity/Mk2Expansion/pull/1

Hi everyone. I'm stuck with the problem which I don't quite know how to solve. It's about variables and string appending. How to mix regexps and variables? Interesting cases (described in the sample code with comments): // somewhere PART{ name=SomePart1 MODULE{ name=SomeModule someVar=1;2;3;4,5,6 someVar2=Text1;Text2;Text3;Text4,Text5,Text6 } } // elsewhere PART{ name=SomePart2 MODULE{ name=SomeModule someVar=1,2;3;4,5,6 someVar2=Text1,Text2;Text3;Text4,Text5,Text6 } } // In my config @PART [*]:HAS[SomeModule] { @MODULE[SomeModule] { // Get first part of semicolon-separated list of comma separated lists myVar= #$someVar[0,;]$ // Or it indexes from 1? // Sum fields from comma separated part of semicolon-separated list of lists @myVar2 = #$myVar[0]$ @myVar2:HAS[#myVar[*,*]] += #$myVar[1]$ // How to do previous step(s) right? @myVar2 ...= ... // some other simple math // Append a string to texts @someVar2 ^= :^.*$:$0;TextAdded: // Here, it's OK and clear // Append calculated var @someVar ^= #:^.*$:$0;$myVar2$: // But here comes a problem, it throws a parse error during Var replacement process. // Try to append calculated var with yet another way @someVar ^= :^.*$:$0;#$myVar2$: // This does the appending but not the value placement. Instead I get a string "#$myVar2$" here. } }