plague006

I created an issue for you in github (https://github.com/KSP-CKAN/CKAN/issues/1082) so that your idea won't be lost in the forum thread. - - - Updated - - - As pjf mentioned the comment on line 12 isn't the right format (you don't need to comment it at all). You can reduce the entire install stanza down to: "install": [ { "file" : "GameData/KashCorp", "install_to" : "GameData" } ] If every folder inside "KashCorp" should be installed, then we can just install "KashCorp" itself. I will highlight though, that if AlphaAsh has other mods in CKAN that also install the "Agencies", "Flags", and "Resources" folders it becomes a whole other beast since you need to split things apart. Moving on you can eliminate lines 4-9. The mod name, author name, abstract, version, and release_status will be provided by KerbalStuff and "x_netkan_license_ok" will actually fail because the license listed on the KerbalStuff page isn't one that netkan will allow so you'll need a line with "license": "BSD-3-clause" So in the end it would be something like: { "spec_version": 1, "identifier": "RoversAndRoadsters", "$kref": "#/ckan/kerbalstuff/94", "license": "BSD-3-clause", "depends": [ { "name": "ModuleManager" } ], "install": [ { "file" : "GameData/KashCorp", "install_to" : "GameData" } ] }

Thank you so much. From 3.8gb and frequent crashes to 2.6gb and stable (so far).

I spent a while trying to get this to work, and with MM and FS installed, I don't get a tweakable on any stock fuel tanks. I later added tweakscale for good measure and saw the tweakable for size but still nothing for fuel type/tank setup. Edit: line 5 needs a closing ] and it should be good to go. Credit to Daz/Dazpoet.

Had this same issue, thank you. =)

Just to be clear, this (gif) is how uninstalling mod Y *should* be working. In the gif I show the relationship between the mods, and I only select 1 mod to be uninstalled but CKAN should force all dependent mods to be uninstalled along with it.

CKAN is halfway there. Currently there's no way to host or public modpacks with CKAN, but CKAN *does* have modpack functionality as an alternative to hosting .zip files with all the mods packed in (as you proposed in your thread). See: https://github.com/KSP-CKAN/CKAN/wiki/Sharing-a-modlist-%28metapackages%29

When you say registry, do you mean the Windows registry (ie. the one you see with regedit) or do you mean registry.json in your CKAN folder? If it's only registry.json, you haven't broken your computer. =) Can you explain further about what's happening with your refresh button? If you just need help *now* and everything seems like it's on fire and you to be able to play, then here's the nuclear option: copy the installed-default.ckan file in the CKAN folder to somewhere safe. Delete the CKAN folder, the GameData folder, and the Ships folder. Re-download the files that come with the base game (ex. verify local files on steam), then open CKAN and follow the instructions here to re-install all the mods you previously had (from the installed-default.ckan file you copied earlier). Note: some of the mods will lose their configurations, so you'll have to customize them back to the way you like them. Also if you want to describe how you ended up manually editing the registry, let me know and maybe I can give you a safer way to get the changes you want.

I didn't personally have an issue installing it. Can you send the output from CKAN so that we can better see what's going on?

I know that you know this (since you commented on the new thread), but I just want to state for all to see: no issue was closed/ignored/disregarded, the issues were moved from one place to another, but each one was kept intact. John's specific issue now lives here: https://github.com/KSP-CKAN/CKAN/issues/921 For Windows the install directories reside in the registry: HKEY_CURRENT_USER\Software\CKAN you can add installs via the command-line interface, see https://github.com/KSP-CKAN/CKAN/wiki/User-guide#using-the-cli There have been issues with firespitter and other mods (KerbalAircraftExpansion in particular) because they're all trying to provide the same files. Roughly 9 hours ago that should have all been resolved (https://github.com/KSP-CKAN/NetKAN/pull/1264), so give it another shot and let us know how it goes please. Can you pastebin the .netkan you wrote up and/or open an issue? (https://github.com/KSP-CKAN/NetKAN/issues/new)

A decent chance people using google will land here (I did): make sure "fullscreen" is unticked in your graphics settings. That will supercede -popupwindow

Basically you're saying your mod has a number of different ways it can be set up/installed by users: CKAN can handle this pretty well. To save me a thousand words: http://imgur.com/a/6X2F1 "Astronomer's Pack" is a single 400mb archive (http://kerbal.curseforge.com/ksp-mods/220335-astronomers-visual-pack-interstellar-v2/files). CKAN has multiple discrete metadata files appearing as mods in the list and each representing portions of the whole package. As seen in the images if you can't install both high and low quality clouds, but you can install high clouds with other non-conflicting modules. Edit: I had a look at filter extension's thread and the archive and realize the example I gave isn't a very good one. So with CKAN you can create something like "FE_base" where it would install all the modules related to the stock parts, and then "FE_b9" which would be the B9 component (and could only be installed if someone had b9 installed), and "FE_KW", etc. Essentially you could break down the mod in any way you saw fit (within reason of course).

Perfect, I'll get to work on it having it added.

I was looking into adding this to CKAN but I'm confused. The mod is named "Oxidizer Flameanator" and your name (the mod author) is "Haze-Zero", why is the folder your mod sits in called "KlearlyAeroSpace"? To be clear: you can name the folder however you like, just trying to make sense of it.

Hi Orionkermin, I'm here reaching out because _Augustus_ opened up an issue on the CKAN github (https://github.com/KSP-CKAN/NetKAN/issues/1261) hoping to add your mod to CKAN. Of course it's something we'd love to have. Currently your only hosting is with Curse which we can absolutely work with, but requires manual updates (by you or someone else) with each update the mod goes through. If you hosted on KerbalStuff in addition to Curse it would allow for automation (one-time setup and likely never having to do anything further). I totally understand that adding another host might be burdensome though, so if you choose not to go that route we'll still make things work. The second thing is that we would like your permission to have CKAN redistribute your mod, because you hold an "All rights reserved" license over it. I look forward to hearing from you here or over at the issue page on github that I previously linked. Edit: Just wanted to add a link to the wiki page with the 3 steps required to get set up on CKAN: https://github.com/KSP-CKAN/CKAN/wiki/Adding-a-mod-to-the-CKAN

Just giving you a heads up that I generated the .netkan file for the mod, so it's in the process of being added to CKAN. https://github.com/KSP-CKAN/NetKAN/pull/1326

Thanks for adding the mod to CKAN m4v! I happened to notice on github that you had some issues getting it up and running, and I appreciate you taking the time.

It's the internet, people offer their opinions in an effort to see change they want. See: http://en.wikipedia.org/wiki/Lobbying and http://en.wikipedia.org/wiki/Opinion As to the rest you're just straw-manning me: I never said my time > anyone else's, I never said whether I was using the mod or not, I said I was able to make an informed decision. If you, modders, or anyone else are offended by me (or others) lobbying for changes we want to see in mods or elsewhere: cool. I support your right to be offended. I tried to be as neutral and respectful as I could while offering my point of view, but it's the internet: I'm used to everyone getting offended by everything or considering everything rude. I honestly find it rather odd to opt out of a system that benefits end users. I mean I respect your decision fully but it still makes no sense to me at all. Keep up the good work though, it's a fun mod.

I noticed this mod was added to the CKAN repo, used it back in 0.90 and loved it. Glad I took a look in the thread though, knowing the author doesn't want to allow CKAN listing allows me to make a more informed decisions on whether to install or not. As to the debate over laziness: I can only speak for myself but KSP is a game for me, not a way of life. I have limited time to play games in a week, I choose not to spend more time than absolutely necessary to make sure the (currently) 74 mods I wish to use are up to date. Loved the mod in the past, would be great if the author reconsidered. If not, still admire the work done.

Just coming back to KSP from a long time away. Been picking the mods I want and *wow* did this one stand out. I was intimidated in the past by more hardcore life support, but wanted *some* consequences to derping. I feel like this is a great mix between the two, you can totally lose control of your starved kerbals, but have the ability to rescue them. Also doesn't hurt that it integrates so well with the full USI suite.

Thanks for the 101/102 update, love the ease this mod provides when I'm trying to pick the right size fuel tank. =)

Yes, because of the update.

I just started using CKAN today. Version listed in the client in CKAN is v0.21. On install IR.version says 0.12.RC1 Running fine with manual install though.