ckan fix for 1.2.2

[alee]

hi first of all i thanks all the developers of different mods you guys are doing a great job and also the one who make ckan you make our live easy  i want to say some mods are working great on 1.2.2 (if manually installed) but ckan says it is incompatible why this happen any idea.

[pincushionman]

Because there is both a "minimum" required KSP version and a "maximum" version supported in the listing. I believe these default to the same value.

I've seen some authors future-proof their listings by stating their max version is 1.X.99, but that is a gamble.

[Snark]

Moving to Add-on Discussions.

[Hupf]

Instead of manually installing mods, you can force ckan to install them if deemed "incompatible" using the CLI: https://github.com/KSP-CKAN/CKAN/wiki/User-guide#using-the-cli & https://github.com/KSP-CKAN/CKAN/issues/881#issuecomment-104538090

Pro: if the mod gets updated, CKAN will automatically manage it in future (it would list, but not update manually installed mods AFAIK)

Con: you have to get the package name from the GUI first and also would have to care yourself for any dependencies in the same way.

[stibbons]

@Hupf is mostly right. But the most recent release of the CKAN client includes some functionality in the GUI to extend which KSP versions to deem compatible with the current one. It doesn't seem to be very well documented in the wiki yet though.

Make sure you're running the most recent release, version 1.22.1, from https://github.com/KSP-CKAN/CKAN/releases . Then you can go to the Settings menu and select "Compatible KSP versions". From that dialogue, you can elect to also install mods that are marked as compatible with KSP 1.2.1 and 1.2 as well as the current 1.2.2, for example.

Note that a mod can opt out of that, and specify that it definitely should only be installed on a specific version. And, obviously, if you install a mod in a potentially incompatible version and everything breaks, you get to keep both pieces.