JonnyOThan

I'm poking through some of the files and I don't see anything that couldn't be done with a MM patch. I'd suggest reading through the docs here: https://github.com/KSPModdingLibs/KSPModdingWiki/wiki/Guides-and-Resources#modulemanager

Can you elaborate on that? MM patches are extremely flexible and are vastly preferred to overwriting files from other mods.

New releases of mods are generally available on CKAN within 35 minutes, depending on where the bot is in the cycle. Sometimes the bot gets stuck and we need to rekick it. There is a page here you can watch for the bot's progress: NetKAN Status It looks like it's detecting some issues in the release (I've never seen this error before but GameData-in-GameData is pretty much always bad). It looks like the stuff in ForParallaxContinued is an optional install? We'll need to adjust the ckan metadata so it understands this properly. However I would strongly urge you to move that folder to the root of the zip file because users will generally never dig that deep into the mod folder. After reading the readme in there...is there a reason that stuff isn't just MM patches with NEEDS clauses?

@Caerfinon Please don't tell people to do this. That's how installs get broken. They can force-install KerbinSideCore from the versions tab in CKAN without changing the compatibility settings.

Sure thing. However... Kerbinside Core is only marked as compatible with KSP 1.5.1. In order for someone to install your mod from CKAN, they will have to get CKAN to install that (ideally by force-installing it from the versions tab, but some people change ckan's compatibility settings to do this which often results in them unintentionally getting old versions of dependencies that break their game). KerbinSideRemasteredGAP already depends on KerbinSideRemastered. Is it even feasible to install both KerbinSideRemastered and Kerbinside Core together? As a policy, we do not change KSP version compatibility for a mod without the author's consent. So there's a few options: Get @Ger_space's blessing to change the version compatibility of Kerbinside Core Find some other way to get the assets you need Adopt the mod yourself (but you'd still need to get permission from the author since it's ARR) If you have other comments or questions, I spun up a PR for your request here: https://github.com/KSP-CKAN/NetKAN/pull/10476 (keeping discussion in one place is ideal since we often need to read through this stuff to understand why certain decisions were made). But if you can't use github for some reason, here is fine too. That dialog box should tell you exactly what you need to do.

We could, but: that change would take effect nearly immediately. That’s not necessarily bad as long as the new dependencies don’t cause any issues for the current version. Another option is to submit a PR to the .netkan file yourself, and then we can time the merge to be close to the new release. The *best* option is to use an internal .ckan file within the mod release. Then the relationships with other mods can be updated whenever they change, in a release-specific way and you have more direct control. The data in the internal .ckan file gets merged with what’s inflated by the ckan bot. But if you’d rather not bother, we can change the metadata for you

They should be completely separate.

Do you have magpie? It’s probably the culprit. Otherwise post some logs.

CKAN does link to the repository, and it's a short jump from there to the releases page where you can see the changelogs: https://github.com/Kopernicus/Kopernicus/releases/tag/release-224

Please post your entire log file, ideally on a new issue on github.

Just released KSPBurst 1.5.5.2: Fix race condition causing game to soft lock when trying to flush logs while the compiler task is still running Available on github and CKAN.

As HebaruSan says, seems like you have a lot of stuff installed incorrectly. I'd suggest nuking your mods and use CKAN instead. I'd also suggest using Tweakscale Rescaled, as it has fewer of these bugs.

It’s pretty low priority since many of the parts don’t have unique IVAs. But I could probably do something for what is there. https://github.com/FirstPersonKSP/FreeIva/issues/289

This part actually comes from stock code. We’ve fixed some of these bugs but if anyone has a solid repro we’d like to know: https://github.com/KSPModdingLibs/KSPCommunityFixes/issues/147

Can you post the logs and craft file? I wonder if it’s picking up some other hatch instead of the clampotron. FreeIVA does add airlocks to the docking ports, so you should be able to eva through there. Perhaps it is obstructed as well. And try clicking the red handle instead of pressing F.