DasSkelett

So I tried out a max_version in conflicts, per se works. However, using generalized mod versions doesn't work The problem is that CKAN handles mod versions only as strings, it doesn't parse/interpret them (in contrast to KSP versions). This is nearly impossible because there are a lot of different version naming schemes out there, and in a lot of cases mod authors don't even stick to one. Wwe also have some mods with versions like "v1.4.8" > "v1.5" > "v1.5.1" > "v1.5.2"... At the latest it would fail there. So you have to write one exact version as max_version. In my opinion that's also a safer way to handle conflicts. Else you would have to make sure the mod author names the next version how you expected it.

Oh I thought you meant KSP versions, overread the mod part. Honestly I don't know right now, I'll take a look. EDIT: Not possible. Yep, you can, I think.

You could set ksp_version_max just to 3, this includes every 3.X. So for real KSP versions, set ksp_version_max to 1.3: All 1.3.X are included as compatible, 1.4(.0) not. This is only possible if the min_version is a different minor, let's say 1.4(.X). But if the requirements haven't changed for KJRNext, this shouldn't be a problem for you See for example this commit.

If you only downloaded those mods yourself, but they would be available via CKAN, you could use the "Import downloaded mods" option, and if I'm not mistaken, this adds them to the CKAN cache. But in your case the mods are not available on CKAN, so you can't use the import function. So unfortunately no way that CKAN can save those mods in its own cache. If you want, you can move the zips yourself in the same folder that CKAN caches its downloads in, so you know where to search them later on. Go to Settings > CKAN Settings > Under "Download Cache" click "Open". Make sure you are using the current CKAN version, v1.26.2 if you do this, there was a bug with non-CKAN files in the cache folder that got fixed. But this still doesn't allow CKAN to (un)install those mods.

What do you mean with toggling? CKAN can't turn mods on and off, it's not a modloader. The CKAN client is only a installation utility. You have to download and install unavailable mods manually, however it should work if you install dependencies via CKAN, provided that they are available on CKAN. The CKAN client will show manually installed mods as "AD" - auto-detected. But you can't interact with them. To remove those mods again, you have to manually delete the files from GameData.

As @Rudolf Meier said, it's probably a leftover file from a previous installation of KJR or KJR Continued, they all three install into the same directory. Look into your GameData directory and delete the KerbalJointReinforcement folder, then try again.

The "Download Contents" button is only there to cache a mod and to see the contents if the mod is not installed yet, and it does not install it. To download and install it, you have to tick the left-most checkbox (column header is "Inst") in the modlist. If there is no checkbox to select, only a "-", make sure to mark KSP 1.6 as compatible under "Settings" > "Compatible KSP versions", because all dependencies of KPBS are only officially compatible with KSP up to 1.6 (Community Category Kit and Community Resource Pack), but should work fine nevertheless.

Done in https://github.com/KSP-CKAN/NetKAN/pull/7175. Can you open a issue on GitHub? What CKAN Version are you running? If its v1.25.X, maybe you are encountering this bug.

I think this occurs if you have "Auto update repository" active in the settings. We are aware of the problem.

Maybe you encountered the "window offscreen bug" https://github.com/KSP-CKAN/CKAN/issues/2717. If it happens again, look into your GUIconfig.xml, see if the window location is -32000, -32000, and if so set both values to 0 (see details in the linked GitHub issue). Is that the file after you deleted it, or the one which wasn't working? What exactly do you mean with "does not start anymore"? If you are able to, would you like to open a issue on GitHub? It's easier for us to help you over there.

Thanks! Yes, try a manual update. Should be available now.

Astronomer's Visual Pack depends on Environmental Visual Enhancements, which currently is only compatible with KSP up to version 1.4.99. You can check this in the relationships tab in the lower right. To be able to install EVE and thus AVP you need to mark KSP 1.4.2 or 1.4 as compatible (via Settings > Compatible KSP versions).

Hey, is this mod still actively supported? It seems you've deleted the mod on SpaceDock.

It's not your fault - SpaceDocks CKAN functionality is currently broken (see https://github.com/KSP-SpaceDock/SpaceDock/issues/188). For the time being, @HebaruSan did add the mods manually, but he's on holiday right now. I'll see if I can do it.

Yep, Open a GiHub issue please. If you want to translate it, you can, but you don't need to, I'm German too. But please include the full stack trace in the issue, not onl, the screenshot, there might be some needed informations hidden.

Thanks @Sunesha, I discovered the error too today, we ( @HebaruSan ) are working on this, see https://github.com/KSP-CKAN/CKAN/issues/2428 . This should only affect Scatterer, all other mods should be fine.