4x4cheesecake

You could tripple check your double checked double check by trying the same but using a :FOR patch to add these mods instead of creating a folder. You know, just to be sure

I'm running a custom patch to fix that exact same issue. Don't remember where I took these values from, I think it's from the default scatterer config for stock Kerbin? Anyway, it works fine: @Scatterer_ocean:HAS[@Ocean[Kerbin]] { @Ocean[Kerbin] { %transparencyDepth = 100 %darknessDepth = 800 %causticsTexturePath = StockScattererConfigs/Planets/Caustics.png %causticsLayer1Scale = 0.200000003,0.200000003 %causticsLayer1Speed = 0.0612000003,-0.151199996 %causticsLayer2Scale = 0.277099997,0.267100006 %causticsLayer2Speed = -0.0748699978,0.174869999 %causticsMultiply = 1 %causticsUnderwaterLightBoost = 2 %causticsMinBrightness = 0.5 %causticsBlurDepth = 200 %lightRaysStrength = 1 %m_UnderwaterColor = 0.100000001,0.75,0.800000012 } } IIRC not all of these values are required to change for the desired effect but I got tired of trial and error at some point and just stopped once I got the desired result.

This option in the setting only exists if you got the making history dlc. The discoverable launchsites are not part of the dlc but the 1.12 update and should be available and appear in the launch list without this option present. In fact, I just tested it and it worked fine for me (without any dlc or the said difficulty setting present). Did you land and recover the vessel after discovering the launch site or did you revert the flight? If you just reverted, it also reverts the discovery

you can actually fix that for yourself by switching to a different theme in your account settings: https://forum.kerbalspaceprogram.com/settings/ Use the search function of your browser (usually ctrl + F) to locate the "theme" selection and choose anything but the default one And on topic: ferry contracts are working fine for me too, even though I'm running tourism overhaul alongside tourism plus and tourism expanded. I don't see how these contract packs would affect each other anyway, though in theory, there might be a chance for the game to create two tourist kerbals with the same name for contracts of different origin, which may or may not will confuse the game. Since 95% of the contracts are ferry contracts, some more details would be appreciated

Interesting. Didn't know that

I don't think MM can look for any folders. MM will just scan for .cfg and .dll files but as far as I know, those can be as many sub folders deep as you want. Do you mind to share what you are trying to do? There might be different solutions

At this point, I got the feeling this is not

It certainly got the ability to add colliders to scatter added through kopernicus. The Stock Visual Terrain mod made use of it back in the days. It's not an option which is simply toggled on and off in some settings but requires a MM patch, either written by yourself or provided by a mod which uses it. By default, it should be disabled, as far as I can tell by the stock config.

You sure about this one? Maybe I misunderstood something but other contract packs actually still use spaces for the agent name field and it works fine. For your multi-waypoint issue: I got no idea for myself but maybe take a look at JNSQ-KSRGAP (probably applies to every GAP contract pack but its the one I'm using and know about) since it offers "Multi Flights" where you start at one airport and continue to two different airports while also creating a waypoint for each airport. This works just on bases you have opened, so there must be some kind of progress tracking list in the background of which 2 airports can be picked at random. I personally don't understand these configs on a level to derive a solution to your problem but maybe you do

Does the cheat menu on the xbox version also provide a console? If so, it might be a bit easier to check for weird issues going on. To open the cheat menu, according to a quick google search, you need to pause the game and You should be able to just keep the menu open, switch to the SPH or VAB and try to save the subassemly again. If an error pops up in the console, take a picture for us In the mean time, you can also try to re-root the subassembly to something else. Again, not sure about how things are done on xbox but there might be a "re-root" tool in the editor, similar to the ones you use to rotate or offset parts. At least on PC, the whole "built your subassembly on top of a docking port" isn't t rue anymore. IIRC it used to be that way since the subassembly couldn't include the root part but it's possible by now. Whatever it might be, simply re-rooting might be worth a try. Oh, and another question: have you tried to save a very simple craft as a sub-assembly, just to check if it works at all? KSP can behave a bit odd when it comes to complex crafts, so maybe try to save something with like 2 or 3 parts, just for testing?

Did you simply miss the "@PART..." during copy&paste or is it actually missing? That could be a reason why. Beside of that: what are you actually trying to accomplish? Why do you need such a specific but still generic filter to target an ISRU? If it is just the stock converters you want to target, you can simply address them by their names using @PART[ISRU] and @PART[MiniISRU]. That would simplify your patch by a lot and even if you want to target more converters, I would still recommend to start small and expand later. You can write a working patch for both stock ISRUs now just to get it up and running and expand it to "every ISRU in the whole universe and beyond" later. That would also help you to experiment with all the other stuff you want to change instead of going back and forth just trying to target the correct part in your patch.

I certainly would at least until now. Took me a hot minute to understand what you're saying. Now that I think about it, that might be how I stumbled upon it the first time. And for everyone else being as slow as me: you can't target a node using a wildcard, if the node doesn't have any "name" key in the first place. It's basically NULL vs 0.

Oh, interesting... that's why some links in CKAN are broken as well. Mostly applies to older mods and I thought their threads might got deleted at some point but adding the "https://" in front of the link gets me to the actual thread now.

Hey there Just a quick heads-up: got 4 MM errors after installing the update: [ERR 20:11:13.250] Error - node name does not have balanced brackets (or a space - if so replace with ?): RationalResources/Deployment/Pack_FarFrontiers/+PLANETARY_RESOURCE:HAS[#Tag[AtmGasII]:NEEDS[FarFrontiers] [ERR 20:11:13.250] Error - node name does not have balanced brackets (or a space - if so replace with ?): RationalResources/Deployment/Pack_FarFrontiers/+PLANETARY_RESOURCE:HAS[#Tag[[SrfIceWater]]:NEEDS[FarFrontiers] [ERR 20:11:13.250] Error - node name does not have balanced brackets (or a space - if so replace with ?): RationalResources/Deployment/Pack_FarFrontiers/+PLANETARY_RESOURCE:HAS[#Tag[[ExoIce]]:NEEDS[FarFrontiers] [ERR 20:11:13.252] Error - node name does not have balanced brackets (or a space - if so replace with ?): RationalResources/Deployment/Pack_FarFrontiers/+PLANETARY_RESOURCE:HAS[#Tag[[AtmGasIII]]:NEEDS[FarFrontiers] Its a missing closing bracket in all 4 cases

Well, yes... that's exactly why this one is a bit weird. Since the INPUT_RESOURCE node got no name, you need to target all of them and then filter by their keys. And like you said, [*] brackets does target all the nodes, so you would expect that: @PART[*]:HAS[@MODULE[ModuleResourceConverter]:HAS[@INPUT_RESOURCE[*]:HAS[#ResourceName[Ore]]]] should do the same as @PART[*]:HAS[@MODULE[ModuleResourceConverter]:HAS[@INPUT_RESOURCE:HAS[#ResourceName[Ore]]]] but for some reason, it doesn't. In both cases, you tell MM to target every INPUT_RESOURCE within every PART which got any ModuleResourceConverter but once you include the brackets after INPUT_RESOURCE it doesn't work anymore. And I personally like to include all the brackets, it's just easier for me to read and understand what a patch does and where certain parts start and end. It also helps me to not forget any required ones while writing patches