certissian

First of all, thank you so much for creating CKAN! It really makes managing mods and especially updating them a breeze. I've got a suggestion regarding the repo refreshing process. I'd really like to see what exactly changed when I refresh the metadata. Maybe something akin to the update column in the interface telling me which mod packs have been updated (even if I they were'n installed before) and which mods were added. That way you can easily tell when your favorite KSP 0.90 mod has been updated to 1.0 and when a mod you had your eyes on for a while might have fixed a bug you had when you first tried it. There's another quality of life update that comes to mind. I'd like to be able to sort the list of mods by the installed and update columns. And here's something a little more complex: Being able to save and restore a mod profile. Profile meaning a list containing the mods you have installed as well as their versions. That way you can try a large number of mods and mod constellations and are still able to easily revert to a working state.

Looking at the data ingame, you get most data from landing on Jool, probably possible with a perfectly timed science module activation and transmission before the Kraken destroys the ship. The next best place seems to be landing on Eeloo which amounts to half as much science as landing on Jool.

Well guys, I delved into the KSP API and managed to write a little partmodule which extracts all available biome maps. So far it's only Kerbin and the Mun. I might take another look at it tomorrow and read out the color->description data. But here's what I got so far: EDIT: Had some extra time and added the info to the pics: Enjoy