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

[StickLabs]

WS e t t i n g   m o d d e e d   t e c h   t r e e   a s   t h e   a c t i v e   o n e  SS e t t i n g   m o d d e e d   p h y s i c s   a s   t h e   a c t i v e   o n e  {S o m e t h i n g   w e n t   w r o n g   w h i l e   s e t t i n g   t h e   a c t i v e   p h y s i c s   c o n f i g .  /[ C u s t o m C o n f i g s M a n a g e r ]    ![ M o d u l e M a n a g e r ]    €‡M u l t i p l e   c o p i e s   o f   c u r r e n t   v e r s i o n .   U s i n g   t h e   f i r s t   c o p y .   V e r s i o n :    .  C a n ' t   f i n d   L o a d i n g S c r e e n   t y p e .   A b o r t i n g   M o d u l e M a n a g e r   e x e c u t i o n M o d u l e M a n a g e r  ]A d d i n g   M o d u l e M a n a g e r   t o   t h e   l o a d i n g   s c r e e n   { 0 }  - n y a n - n y a n +T o t a l   l o a d i n g   T i m e   =    F 3  s  'D a t a b a s e   r e l o a d i n g    %  L a b e l  €ÑY o u r   K S P   1 . 0 . 5   i s   r u n n i n g   o n   b u i l d   1 0 2 4 .   Y o u   s h o u l d   u p g r a d e   t o   b u i l d   1 0 2 8   t o   a v o i d   p r o b l e m s   w i t h   a d d o n s .  =C l i c k   t o   o p e n   t h e   F o r u m   t h r e a d  €¿h t t p : / / f o r u m . k e r b a l s p a c e p r o g r a m . c o m / i n d e x . p h p ? / t o p i c / 1 2 4 9 9 8 - s i l e n t - p a t c h - f o r - k s p - 1 0 5 - p u b l i s h e d / M o d u l e M a n a g e r    R e l o a d   D a t a b a s e  +Q u i c k   R e l o a d   D a t a b a s e  +D u m p   D a t a b a s e   t o   F i l e  _ M M C f g O u t p u t      . c f g  uY o u   h a v e   o l d   v e r s i o n s   o f   M o d u l e   M a n a g e r   ( o l d e r   t h a n   1 . 5 )   o r   M M S a r b i a n E x t . 
 Y o u   w i l l   n e e d   t o   r e m o v e   t h e m   f o r   M o d u l e   M a n a g e r   a n d   t h e   m o d s   u s i n g   i t   t o   w o r k 
 E x i t   K S P   a n d   d e l e t e   t h o s e   f i l e s   : 
 
  =O l d   v e r s i o n s   o f   M o d u l e   M a n a g e r  O K  _O l d   v e r s i o n   o f   M o d u l e   M a n a g e r   p r e s e n t .   S t o p p i n g  v e r s i o n          a t    %  l o s t   t h e   e l e c t i o n   V e r s i o n        
  5  w o n   t h e   e l e c t i o n   a g a i n s t 
  R a n   i n    cc o m p i l i n g   l i s t   o f   l o a d e d   m o d s . . . 
 M o d   D L L s   f o u n d : 
       v        /   v  +    { 0 , - 5 0 }   S H A 2 5 6   { 1 } 
 AN o n - D L L   m o d s   a d d e d   ( : F O R [ x x x ] ) : 
 : F O R [  9S k i p p i n g   : F O R   i n i t   f o r   l i n e    {.   T h e   l i n e   m o s t   l i k e l y   c o n t a i n   a   s p a c e   t h a t   s h o u l d   b e   r e m o v e d  cM o d s   b y   d i r e c t o r y   ( s u b   d i r e c t o r i e s   o f   G a m e D a t a ) : 
  G a m e D a t a  'L o a d i n g   P h y s i c s . c f g  P H Y S I C S G L O B A L S  €‰N o   P H Y S I C S G L O B A L S   n o d e   f o u n d .   N o   c u s t o m   P h y s i c s   c o n f i g   w i l l   b e   s a v e d  €‹  P H Y S I C S G L O B A L S   n o d e   f o u n d .   A   p a t c h   m a y   b e   w r o n g .   U s i n g   t h e   f i r s t   o n e  F o u n d   b a d   v a l u e  %F o u n d   n o   b a d   v a l u e  { 0 , 2 : x 2 }  /E x c e p t i o n   h a s h i n g   f i l e    0  /  #S H A   g e n e r a t e d   i n                S H A   =    S H A  v e r s i o n  K S P V e r s i o n  F i l e s S H A  C a c h e   S H A   =    u s e C a c h e   =    C h a n g e d   :    f i l e n a m e  . c f g 
  A d d e d       :    D e l e t e d   :    C h a n g e s   : 
      F I L E  !p a t c h e d N o d e C o u n t  c a t E a t e n C o u n t  U r l C o n f i g      n a m e      t y p e  p a r e n t U r l  u r l  / P h y s i c s  S a v i n g   c a c h e  ?E x c e p t i o n   w h i l e   s a v i n g   t h e   s h a 
  ]N u l l R e f e r e n c e E x c e p t i o n   w h i l e   s a v i n g   t h e   c a c h e 
  CE x c e p t i o n   w h i l e   s a v i n g   t h e   c a c h e 
  €ÁA n   e r r o r   o c c u r e d   w h i l e   c r e a t i n g   t h e   c a c h e .   D e l e t i n g   t h e   c a c h e   f i l e s   t o   a v o i d   k e e p i n g   a   b a d   c a c h e  GE x c e p t i o n   w h i l e   d e l e t i n g   t h e   c a c h e 
  T e c h T r e e  qN o   T e c h T r e e   n o d e   f o u n d .   N o   c u s t o m   T e c h T r e e   w i l l   b e   s a v e d    T e c h T r e e   n o d e   f o u n d .   A   p a t c h   m a y   b e   w r o n g .   U s i n g   t h e   f i r s t   o n e  !P a r e n t   n u l l   f o r    C a c h e   L o a d e d  M o d u l e M a n a g e r :       p a t c h  e s    a p p l i e d  %  l o a d e d   f r o m   c a c h e  ,   f o u n d       e r r o r  ,          w a s  e s   w e r e  /  e a t e n   b y   t h e   W i n 6 4   c a t  -D e l e t i n g   N o d e   i n   f i l e      s u b n o d e :    S  a s   i t   i s   s e t   t o   b e   d i s a b l e d   o n   K S P   W i n 6 4  +E r r o r   -   N o d e   i n   f i l e   1  h a s   c o n f i g . n a m e   = =   n u l l  : N E E D S [  =  a s   i t   c a n ' t   s a t i s f y   i t s   N E E D S CE x c e p t i o n   w h i l e   c h e c k i n g   n e e d s   :    !  w i t h   a   t y p e   o f    N o d e   i s   :    1D e l e t i n g   v a l u e   i n   f i l e :      v a l u e :      =    kA r g u m e n t O u t O f R a n g e E x c e p t i o n   i n   C h e c k N e e d s   f o r   v a l u e   "  " 
  %G e n e r a l   E x c e p t i o n      f o r   v a l u e   "  /D e l e t i n g   n o d e   i n   f i l e :    iA r g u m e n t O u t O f R a n g e E x c e p t i o n   i n   C h e c k N e e d s   f o r   n o d e   "    f o r   n o d e   "  " 
    =[ M o d u l e M a n a g e r ]   m o d d i n g   v a l u e s      
        =    ]E r r o r   -   C a n n o t   p a r s e   v a l u e   a s s i g n i n g   c o m m a n d :   [E r r o r   -   C a n n o t   f i n d   v a l u e   a s s i g n i n g   c o m m a n d :   ]E r r o r   -   C a n n o t   p a r s e   v a l u e   m o d i f y i n g   c o m m a n d :   *  gE r r o r   -   U n a b l e   t o   p a r s e   n u m b e r   a s   n u m b e r .   V e r y   o d d . aE r r o r   -   C a n n o t   u s e   o p e r a t o r s   w i t h   i n s e r t   v a l u e :   yE r r o r   -   C a n n o t   p a r s e   v a r i a b l e   s e a r c h   w h e n   i n s e r t i n g   n e w   k e y   cE r r o r   -   C a n n o t   u s e   i n d e x   w i t h   r e p l a c e   ( % )   v a l u e :   kE r r o r   -   C a n n o t   u s e   o p e r a t o r s   w i t h   r e p l a c e   ( % )   v a l u e :   }E r r o r   -   C a n n o t   u s e   w i l d c a r d s   ( *   o r   ? )   w i t h   r e p l a c e   ( % )   v a l u e :   yE r r o r   -   C a n n o t   p a r s e   v a r i a b l e   s e a r c h   w h e n   r e p l a c i n g   ( % )   k e y   :          - >   mE r r o r   -   C a n n o t   p a r s e   v a r i a b l e   s e a r c h   w h e n   e d i t i n g   k e y   sE r r o r   -   C a n n o t   u s e   o p e r a t o r s   w i t h   d e l e t e   ( -   o r   ! )   v a l u e :   cE r r o r   -   R e n a m i n g   n o d e s   d o e s   n o t   w o r k   o n   t o p   n o d e s aE r r o r   -   C a n n o t   u s e   i n d e x   w i t h   c r e a t e   ( & )   v a l u e :   iE r r o r   -   C a n n o t   u s e   o p e r a t o r s   w i t h   c r e a t e   ( & )   v a l u e :   {E r r o r   -   C a n n o t   u s e   w i l d c a r d s   ( *   o r   ? )   w i t h   c r e a t e   ( & )   v a l u e :   €ÓE r r o r   -   S k i p p i n g   a   p a t c h   s u b n o d e   w i t h   u n b a l a n c e d   s q u a r e   b r a c k e t s   o r   a   s p a c e   ( r e p l a c e   t h e m   w i t h   a   ' ? ' )   i n         :   
  ,  UE r r o r   -   C a n   n o t   f i n d   t h e   n o d e   t o   p a s t e   i n    :    : H A S [  [  ]  9    c a n n o t   w i l d c a r d   a   %   n o d e :    '    A p p l y i n g   s u b n o d e    #    A d d i n g   s u b n o d e    I    C o u l d   n o t   f i n d   n o d e ( s )   t o   m o d i f y :    . . /  )C a n ' t   f i n d   n o d e T y p e : MC a n n o t   p a r s e   v a r i a b l e   s e a r c h   c o m m a n d :    !C a n n o t   f i n d   k e y          i n    +I n v a l i d   V e c t o r   I n d e x !  WE r r o r   -   F a i l e d   t o   d o   a   r e g e x p   r e p l a c e m e n t :   '  :   o r i g i n a l   v a l u e = "  "   r e g e x p = "  €±"   
 N o t e   -   t o   u s e   r e g e x p ,   t h e   f i r s t   c h a r   i s   u s e d   t o   s u b d i v i d e   t h e   s t r i n g   ( m u c h   l i k e   s e d ) 
 UE r r o r   -   F a i l e d   t o   d o   a   m a t h s   r e p l a c e m e n t :   "   o p e r a t o r =    m o d   v a l u e = "  "      H A S [  ^  \ *  . *  \ ?  $  { 0 } [ { 1 } ] 
      N U L L  N U L L 
  /P r e t t y C o n f i g   E x c e p t i o n    { 0 } { 1 } 
 { 2 } { { 
  { 0 } { 1 }   =   { 2 } 
      n u l l  %v a l u e . n a m e . L e n g t h =  3v a l u e . n a m e . I s N u l l O r E m p t y =  n    v    { 0 }   N u l l   v a l u e 
  !{ 0 }   N u l l   v a l u e s 
  #{ 0 }   N u l l   S u b n o d e 
  { 0 }   N u l l   n o d e s 
  { 0 } } } 
  !R u n n i n g   t e s t s . . .  M M T E S T _ E X P E C T  T e s t    k  f a i l e d   a s   e x p e c t e d   n u m b e r   o f   n o d e s   d i f f e r s   e x p e c t e d :    f o u n d :    €]   f a i l e d   a s   e x p e c t e d   o u t p u t   a n d   a c t u a l   o u t p u t   d i f f e r . 
 e x p e c t e d : 
 
 A c t u a l l y   g o t : 
  t e s t s   c o m p l e t e .  M o d u l e   M a n a g e r  3M o d u l e M a n a g e r . C o n f i g C a c h e  -M o d u l e M a n a g e r . T e c h T r e e  +M o d u l e M a n a g e r . P h y s i c s  P h y s i c s . c f g  !P a r t D a t a b a s e . c f g  /M o d u l e M a n a g e r . C o n f i g S H A  €­( [ \ w \ & \ - \ . \ ? \ * ] * ) ( ? : , ( - ? [ 0 - 9 \ * ] + ) ) ? ( ? : \ [ ( ( ? : [ 0 - 9 \ * ] + ) + ) ( ? : , ( . ) ) ? \ ] ) ? ( ? : \ s ( [ + \ - * / ^ ! ] ) ) ? /( . * ) ( ? : \ s ) + ( [ + \ - * / ^ ! ] ) ? ( [ \ w \ & \ - \ . ] + ) ( ? : , ( ( ? : [ 0 - 9 ] + ) + ) ) ? ( ? : \ [ ( ( ? : [ 0 - 9 ] + ) + ) ( ? : , ( . ) ) ? \ ] ) ? EM o d u l e M a n a g e r . P r o p e r t i e s . R e s o u r c e s  c a t  5D a t a b a s e   r e l o a d i n g   s t a r t e d  ;D B   R e l o a d   O K   w i t h   p a t c h C o u n t =    e r r o r C o u n t =  /  n e e d s U n s a t i s f i e d C o u n t =  7D a t a b a s e   r e l o a d i n g   f i n i s h e d  M M S a r b i a n E x t  ?E x c e p t i o n   i n   I s C a c h e U p T o D a t e   :    C h e c k i n g   N E E D S .  !A p p l y i n g   p a t c h e s   : F I R S T  : L E G A C Y  : B E F O R E [  : A F T E R [   : F I N A L  +  r e l a t e d   t o   G a m e D a t a /  eE r r o r s   i n   p a t c h   p r e v e n t s   t h e   c r e a t i o n   o f   t h e   c a c h e  KE x c e p t i o n   w h i l e   d e l e t i n g   s t a l e   c a c h e    %L o a d i n g   f r o m   C a c h e  AR e l o a d i n g   r e s s o u r c e s   d e f i n i t i o n s  ]E x c e p t i o n   w h i l e   r u n n i n g   a   p o s t   p a t c h   c a l l b a c k 
  +M o d u l e M a n a g e r P o s t L o a d  C a l l i n g    ( )  1E x c e p t i o n   w h i l e   c a l l i n g    ( )   : 
  YP o s t   r u n   c a l l   t h r e w   a n   e x c e p t i o n   i n   l o a d i n g      p a s s    ( d e f a u l t )   p a s s  €ÁE r r o r   -   S k i p p i n g   a   p a t c h   w i t h   u n b a l a n c e d   s q u a r e   b r a c k e t s   o r   a   s p a c e   ( r e p l a c e   t h e m   w i t h   a   ' ? ' )   : 
 A p p l y i n g   n o d e          t o    C o p y i n g   N o d e       i n t o    ?E r r o r   -   E r r o r   w h i l e   p r o c e s s i n g   €•  t h e   c o p y   n e e d s   t o   h a v e   a   d i f f e r e n t   n a m e   t h a n   t h e   p a r e n t   ( u s e   @ n a m e   =   x x x )  D e l e t i n g   N o d e    M M _ P A T C H _ L O O P  L o o p i n g   o n    EE x c e p t i o n   w h i l e   p r o c e s s i n g   n o d e   :      AàX§ðòèF‘¨pþ7’   = M  €‰    
%       % %  
      -  59=    E eimquy  u  €Í  e  Q U   a e
i     UU  iim0
im      m      q q  y   €•
‰  
 •    ™  
 ©­}€}€}€q    ½ } } Á  Å  q q €É U} U q Uq   Ñ UUÍÑ Ñ Ñ €Õ€…  €‰€‘€‘ é  €
  €•€‘€•€‘      €‰ €‰€‘  €Á '$€•€€•€€•€‰€€í    €¥€€• €• €¥
€€• €• €• €•     €¥€€•€• €¥
€€¥
€• õ ù€€õ€¥€€u
€€u€¥€u
€u€¥€ueý €• €¥

[Red Iron Crown]

@StickLabs Some sort of context for your post and what you are trying to say would be very helpful.

[StickLabs]

17 hours ago, Red Iron Crown said:

@StickLabs Some sort of context for your post and what you are trying to say would be very helpful.

My Module manager is not working,only 11 patches applied.

[blowfish]

@StickLabs Still no idea what's going on.  Please describe in detail the exact problem you are having and then post your either log (uploading to Google Drive/Dropbox/similar then sharing and posting the link is a good way to do it).  We'd all like to help you but your post is rather difficult to decipher.

[Rayder]

Is there a way of disabling config files by pathname, filename, or otherwise?

I'm trying to edit some values in a CRP config but it's proving rather tricky. I can't delete the module and establish a new one in the one file, and it seems using :FINAL doesn't work. An example of what I'm trying to do is shown here:

Spoiler

!PLANETARY_RESOURCE[*]:HAS[#ResourceName[Oxygen]],* {}

PLANETARY_RESOURCE
{
    ResourceName = Oxygen
    ResourceType = 2
    PlanetName = Kerbin
    
    Distribution
    {
        PresenceChance = 100
        MinAbundance = 21
        MaxAbundance = 21
        Variance = 0
    }
}

The reason why this doesn't work? I'm unsure. This config successfully deletes the Oxygen resource from Kerbin, but it doesn't add it back in. It theoretically works, as the code to add in Oxygen is almost identical to the CRP config.

My theory is that my first line actually deletes my own config below it. But regardless, my PLANETARY_RESOURCE just doesn't work. I've tried a few different tricks including :FINAL, but I suspect that isn't designed for this purpose.

What does work is this:

Spoiler

@PLANETARY_RESOURCE:HAS[#ResourceName[Oxygen]],[#PlanetName[Kerbin]]:FINAL
{
    @Distribution
    {
        @MinAbundance = 21
        @MaxAbundance = 21
    }
}

Now here is my problem. CRP adds a different number of configs for different planets for different resources. As it stands, it seems I have to modify the ones I know I'll be using and then delete the rest. It's a rather tedious process, especially if there's a resource I'd previously removed and want to add back in and it doesn't make for a clean .cfg file. If I can just delete it straight up and then specify my own module that would make things much simpler.

Is there a way of achieving this, short of deleting the actual config inside the CRP folder?

Edited January 1, 2017 by Rayder

[WuphonsReach]

Not finding this in the history, so...

Can a MM patch be written to modify the DSN antenna power values on Kerbin, or the game difficulty settings related to CommNet?

(I suspect I'd have to write a DLL.)

[steve_v]

2 minutes ago, WuphonsReach said:

modify the DSN antenna power values on Kerbin

FWIW, the mods I've come across that do this use Custom Barn Kit.

[blowfish]

@Rayder You're probably right that it's removing yours too.  What you can do is set some flag in your node and check for it when deleting.

[Rayder]

7 hours ago, blowfish said:

What you can do is set some flag in your node and check for it when deleting.

This worked, and a little better than I'd hoped actually. Initially I added the flag onto my existing code but then I realised I can remove all of it, and just look for the tag. This also reduced the number of total edits I had to make; from about 40 down to 3:

Spoiler

!PLANETARY_RESOURCE[*]:HAS[~id[-1]],* {}

PLANETARY_RESOURCE
{
    id = -1
    ResourceName = Water
    ResourceType = 0        // Surface
    PlanetName = Kerbin
    
    Distribution
    {
        PresenceChance = 100
        MinAbundance = 1
        MaxAbundance = 50
        Variance = 20
        Dispersal = 3
    }
}

This had the somewhat predicted side effect of removing Ore  as well, but that's easily worked around. That is, unless I make the module excessively complicated with lots of filters. But now this code works. Thanks @blowfish

[akardam]

I'm close to pulling out what little hair I have left. I've been doing google and forum searches, but unfortunately neither of them really like the vertical pipe, which is at the heart of my woes.

Here's what I'm trying to do. I want to apply to all parts that have a given module, and that module having a setting, with one of two possible values. Thusly (this is one of the things I've tried that didn't really work):

@PART[*]:HAS[@MODULE[ModuleFoo]:HAS[#setting[1]|#setting[2]]]

This will modify parts where the value for "setting" is 1, but ignores any parts where the value of "setting" is 2.

If I eliminate the conditional, and try either 1 or 2, either one works.

I'm sure that there's some subtle bit of logic I just can't wrap my brain around... anybody have any suggestions?

[Rayder]

@akardam I think the issue might be your bracketing. Try this:

@PART[*]:HAS[@MODULE[ModuleFoo]]:HAS[#setting[1]]|[#setting[2]]

 

[blowfish]

5 hours ago, Rayder said:

@akardam I think the issue might be your bracketing. Try this:

@PART[*]:HAS[@MODULE[ModuleFoo]]:HAS[#setting[1]]|[#setting[2]]

 

That looks wrong to me.  The second HAS block is supposed to apply to the MODULE, and you've got some extra closing braces.

[Jebs_SY]

@sarbian

Have you ever thought about a blacklist-file for modulemanager where a advanced user can enter cfg files paths of mods that shall not invalidate the MM-cache?
I use a highly modded install (150+) and using the cache or not makes a loading difference of multiple minutes. Cached saves 1-5 minutes loading time.
However, I don't think that I can get multiple mod authors to chance their config path. And even if, atm I have a bug that rewrites the custom category cfg from squad each start, so it still would be handy to have a blacklist possibility.

[akardam]

13 hours ago, blowfish said:

That looks wrong to me.  The second HAS block is supposed to apply to the MODULE, and you've got some extra closing braces.

Yeah, that didn't even modify the part with the first value of "setting".

I suppose I can use separate patches (each with one different value of "setting") unless anyone has any better ideas...

[blowfish]

45 minutes ago, akardam said:

Yeah, that didn't even modify the part with the first value of "setting".

I suppose I can use separate patches (each with one different value of "setting") unless anyone has any better ideas...

I dug a bit through the code and it looks like or "|" isn't supported for HAS blocks.  @sarbian could confirm, but I think this is the answer.

[Nnimrod]

How do I edit a specific value of a key and only that value, skipping past the rest? I'm interested specifically in changing the size of attachment nodes in a part that I have rescaled.

node_stack_top = 0.0, 1.0293, 0.0, 0.0, -1.0, 0.0

It isn't specified, so it defaults to the size 1 node, and I'd like it to be the size 0 node, but I want to not make changes to the other values because I assume that rescaleFactor has already changed them.

[blowfish]

24 minutes ago, Nnimrod said:

How do I edit a specific value of a key and only that value, skipping past the rest? I'm interested specifically in changing the size of attachment nodes in a part that I have rescaled.

node_stack_top = 0.0, 1.0293, 0.0, 0.0, -1.0, 0.0

It isn't specified, so it defaults to the size 1 node, and I'd like it to be the size 0 node, but I want to not make changes to the other values because I assume that rescaleFactor has already changed them.

Since the node only has 6 values, just add it on to the end as a string

@node_stack_top ^= :$:, 0:

To briefly explain what's going on here, ^= tells MM to to replace something in the string.  Next is :XXX:YYY: which says "replace XXX with YYY".  Now, $ signifies the end of the string (since you want to add it to the end).  Then ", 0" is what you want to add on.

I'll add though, that rescaleFactor won't affect anything you're doing here.  That, and most other scaling is done in KSP's code, not in the configs.  So you'd really be fine to just replace it.

[Nnimrod]

2 minutes ago, blowfish said:

Since the node only has 6 values, just add it on to the end as a string

@node_stack_top ^= :$:, 0:

To briefly explain what's going on here, ^= tells MM to to replace something in the string.  Next is :XXX:YYY: which says "replace XXX with YYY".  Now, $ signifies the end of the string (since you want to add it to the end).  Then ", 0" is what you want to add on.

I'll add though, that rescaleFactor won't affect anything you're doing here.  That, and most other scaling is done in KSP's code, not in the configs.  So you'd really be fine to just replace it.

Thank you very much!

[sarbian]

12 hours ago, Jebs_SY said:

@sarbian

Have you ever thought about a blacklist-file for modulemanager where a advanced user can enter cfg files paths of mods that shall not invalidate the MM-cache?
I use a highly modded install (150+) and using the cache or not makes a loading difference of multiple minutes. Cached saves 1-5 minutes loading time.
However, I don't think that I can get multiple mod authors to chance their config path. And even if, atm I have a bug that rewrites the custom category cfg from squad each start, so it still would be handy to have a blacklist possibility.

Yes, I thought about it. The problem is that if I add a blacklist I then have to 1) load them by hand (not that hard but one more complexity) and 2) deal with people who will fill that blacklist without considering the impact and break mods by doing so (thus adding more work other modders).

[Jebs_SY]

1 hour ago, sarbian said:

2) deal with people who will fill that blacklist without considering the impact and break mods by doing so (thus adding more work other modders).

Yes, that is definitely a big thing to consider in such a decision / functionality. Hard decision. Maybe it's really better without a black list, unfortunately  

Just as feedback, I checked it in detail, at my 150+ mod install the difference is 3 minutes vs 6 minutes loading time. When one needs to restart while streaming this is a difference.
However, I think I can work around it without a black list, too. I disabled the update check (which adds a time stamp) of transfer window planer and asked, if the file can be moved. I set write protection to the squad custom category config file which gets rewritten each start atm caused by a bug in combination by FE und KSPI-I (I think). However this gives a "may not write file" exception while going into the editor, but well. At the end I removed a MM config error in the actual release of Mark IV Spaceplane System.
I think now I have a fair chance of getting cache usage. It still would be nice to have a kind of blacklist feature but I agree it should be done in such a advanced way that only users who know what they do use it. Maybe I should browse the source and there is already a hidden BL file feature?!
However, I think for now I managed to get around the main need.

 

[Jebs_SY]

@sarbian

Would it maybe make sense to blacklist at least "Squad\PartList\PartCategories.cfg" by default? There should never be MM stuff in, or?

[sarbian]

And it should never change ?

[Jebs_SY]

26 minutes ago, sarbian said:

And it should never change ?

Well, it does change when someone creates a custom category in the editor. I thought that MM doesn't need to patch against a editor category. But well, maybe it does need to? In this case forget my idea. Was a bad idea then. Sorry
 

[blowfish]

Regarding PartCategories.cfg...

The fact that KSP saves to it means that it wouldn't really make sense for a mod to edit its contents with a MM patch.  The changes in the patch would just be written to the actual file on the next save.  However, there's nothing that prevents them from doing this currently as it's read from the game database.

It seems like it might make sense to blacklist it

[Starwaster]

Except that what you would really be doing is 'blacklisting' part of the GameDatabase with a needless restriction just because Squad is using those nodes to write part of an external file?

There needs to be a better reason than that.  It needs to be demonstratably harmful and that neutering part of MM's functionality is more preferable than submitting a bug report to Squad to fix the behavior in question