Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

74 Excellent

About TeddyDD

  • Rank
    Spacecraft Engineer

Contact Methods

  • Twitter

Profile Information

  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm surprised @SQUAD released such unfinished, buggy mess... wait, no I'm not surprised. I'm disappointed. Parts are nice though.
  2. Not true at least in my case. I'm playing since 0.13 I can plan and conduct interplanetary mission including slingshot with pretty good precision (KSP TOT is amazing tool). But usually I stay in Kerbin SOI. Why? I'm playing in semi-realistic roleplay style. I wont put three Kerbals in tiny capsule and send them in three years long flight. Interplanetary takes lot of time and effort to plan. I don't have much time to spend on KSP. Unmanned are easier, but they usually are satellites (rovers and driving sucks in KSP so much...) And planets are pretty boring in KSP. Nothing to do, flat
  3. KSP TOT is amazing tool, especially when you planing slingshots Pitty I can't use it anymore (Linux ftw)
  4. @Malah Nah, don't worry, with all policy changes and proposal to split the repo into stable/stagin some downtime is inevitable. Only thing that really made me angry is this thread: I'm not sure if @passinglurker tried force CKAN to change policy this way or this is supposed to be way to kill CKAN by unjustified censorship and blocking any possibility to talk about issue. Either way this is pathetic.
  5. @RoverDude Well ok. I agree. Lets focus on official, op-out repos now. We can think how improve user experience for advanced users later. Edit: Gods, this forum hates me. I want everything to be markdown ;=; How to reference user?
  6. It seems there is wip project like that here "We will encourage you to develop the three great virtues of a programmer: laziness, impatience, and hubris." -- LarryWall My favourite quote
  7. That's your opinion. My opinion is that nothing justifies user that don't read frigging notices in authors thread and ask for CKAN support when author clearly say "NO CKAN SUPPORT HERE". De-listing, staging repos and everything else is just workaround to people stupidity ¯\_(ツ)_/¯ for me its EOT Thats why me and @blu3wolf are insisting on creating unsupported, wild repo that would contain anything. (btw I'm interested in your idea to rewrite CKAN. What would you change? What kind of metadata would you use? What language? Could you drop me pm about details? ) Sure, you can be ag
  8. From what i learn in this drama - users are idiots that can't understand this simple sentence. This. Generally I love idea of unsupported repo as long as that stupid users won't use it.
  9. I'd like to have unsupported repo for advanced users but I this one must not be opt-out to make sense. Therefore it should not be part of offical CKAN to not cause controversy. I wouldn't call it done since many modders passionately hate CKAN, and most don't care about it. I agree that manual edition of JSON file is not something that average mod autor cant handle. But for example, looking for deps is tedious since you have to use identifier instead of name. This could be streamlined a bit. Also I know CKAN metadata quiet well but I'd like to have tool that visualize package rel
  10. I'v gone through the thread and I'd like to sum up things that could be done to increase CKAN metadata quality (before I open an issue at CKAN) 1. Add "maintainer" field to metadata. This could work similar to maintainers in AUR 2. Split CKAN-meta into two repositories: CKAN-meta and CKAN-testing (or staging, whatever). Those repositories would be opt-out for mod authors of course. 3. Don't accept .netkan without a maintainer. Automatically inflate .netkans provided by mod author to testing repo. Inflate .netkan to staging that is provided by third-party maintainer only after ma
  11. You can also grab ModuleManager.fozen and use netkan.exe to genrate ckan package (Like in Arch AUR). That is what I'm going to do.
  12. Install is quiet easy. Update 60 mod install is pretty hard. And time consuming. Maybe moderators should ban users who don't read first post in a thread? They are source of issue, not CKAN and mod devs don't care about them anyway.
  13. @Umlüx Yeah, I wouldn't count on Squad. If I recall correctly CKAN guys can mirror mods on S3. I suppose this feature will be priority now.
  14. Is even worse. Thanks to KerbalStuff api ckan files were generated mostly automatically. It's still possible if authors will host their mods via Github releases but Curse only mods have to be updated manually. Edit: There is torrent at Kerbalstuff site with all mods. Who wants 60gb of mods?
  • Create New...