Kinote

Bit fancier than the one I whipped up a while back after some tinkering. If you would like to add Protractor support, simply add the following under one of the @PART[*]:HAS[@MODULE[ModuleCommand]] headings, although I think more than one may be a bit redundant. For reference, my old config looks like this: Seems to still work.

I apologize if this is already a known issue, but has anybody else been having trouble with 'TweakableEverything 1-2' causing the heat shields to continuously play a puff of white smoke in both the VAB and low level flight? I spent a good chunk of the past hour removing mods one by one until I found the culprit, and it definitely seems to be TweakableEverything; remove it and the puff of smoke goes away only to return when the mod is replaced.

I want to say no. I believe without an entry it just defaults to 0, but I could be wrong.

I used too, but I deleted my other two KSP copies shortly after the latest patch was released. Back to just one and launching either through Steam or Mod Admin. One career for normal use, and one for testing with only the Start node unlocked. I think I might make a whole copy of a stock KSP folder, start a new career in that and then throw in just KAS and a few lines for one or two parts. EDIT: Starting a fresh campaign (within my original, fully modded KSP folder) with the following .cfg resulted in a big pile 'o nothing. What I'm curious about more than anything is why it worked perfectly for adding Engineer/Protractor/MechJeb to all the pods with that neat little module trick, but adding a simple line to a part is failing terribly when copy pasting the same line into the actual part.cfg works fine. The names all look right, most parts are copy/pasted right from the part.cfg itself. @PART[stretchyTank05m] { TechRequired = start } @PART[stretchyTank1m] { TechRequired = start } @PART[stretchyTank2m] { TechRequired = start } @PART[stretchyTank3m] { TechRequired = start } @PART[stretchyTank4m] { TechRequired = start }

For a little test, I decided to try something out. The start of the part.cfg looks like so: PART { name = KAS_CPort2 module = Part author = KospY TechRequired = specializedConstruction The little test .cfg I dropped into GameData: @PART[KAS_CPort2] { @TechRequired = start } My understanding is that since there is a TechRequired entry in the original .cfg, this new file should change that node from Specialized Construction, to Start, for the part CPort2. In practice, this doesn't seem to be the case.

That would be a mild case of derp on my part, I just posted the latest version I had whipped up. Since I had manually put each line into the part.cfg's at this point, I tried adding the @'s into the latest version to see if I could change the locations in the tree around. The first few versions had the syntax you showed. @PART[KAS_CPort2] { TechRequired = generalConstruction } @PART[KAS_Hook_Anchor] { TechRequired = landing } But, no dice. Will MM only read instructions from one custom .cfg? I've never tried combining all my smaller projects into one larger one with the functioning pod version.

I seem to have run into some difficulty with MM, but I'm not sure where I've gone wrong. My first project to add Engineer, Protractor, and MechJeb functionality to all pods worked out quite well, but my attempt to add tech tree entries to KAS and StretchyTank parts has failed and I'm not entirely sure why. I've tried scribbling the code up a few different ways but nothing works, although adding the lines directly into the individual part.cfg files works just fine although is a little too labour intensive with future patches coming down the pipe. Could somebody point me in the right direction? Cheers. Project 1: Working @PART[*]:HAS[@MODULE[ModuleCommand]] { MODULE { name = BuildEngineer } MODULE { name = FlightEngineer } MODULE { name = ProtractorModule } MODULE { name = MechJebCore } } Project 2: Failure @PART[KAS_Container1] { @TechRequired = start } @PART[KAS_Container2] { @TechRequired = generalConstruction } @PART[KAS_ContainerBay1] { @TechRequired = start } @PART[KAS_CPort1] { @TechRequired = generalConstruction } @PART[KAS_CPort2] { @TechRequired = generalConstruction } @PART[KAS_Hook_Anchor] { @TechRequired = landing } @PART[KAS_Hook_GrapplingHook] { @TechRequired = generalConstruction } @PART[KAS_Hook_Magnet] { @TechRequired = advElectrics } @PART[KAS_HookSupport] { @TechRequired = advElectrics } @PART[KAS_Pipe1] { @TechRequired = fuelSystems } @PART[KAS_Pylon1] { @TechRequired = advConstruction } @PART[KAS_Strut1] { @TechRequired = advConstruction } @PART[KAS_Winch1] { @TechRequired = generalConstruction } @PART[KAS_Winch2] { @TechRequired = generalConstruction } @PART[KAS_Winch3] { @TechRequired = specializedConstruction } @PART[KAS_Winch4] { @TechRequired = specializedConstruction } @PART[stretchyTank05m] { TechRequired = precisionEngineering } @PART[stretchyTank1m] { TechRequired = advRocketry } @PART[stretchyTank2m] { TechRequired = veryHeavyRocketry } @PART[stretchyTank3m] { TechRequired = veryHeavyRocketry } @PART[stretchyTank4m] { TechRequired = veryHeavyRocketry }