HebaruSan

You'll probably have more luck if you specify what kind of mod you want to make and what kind of help you need. Bonus points for showing that you've made an effort to find and understand the existing modding resources that are stickied in the forum.

Yes. When an installed mod's metadata changes, the Update box becomes available, and checking it adds a re-install action to the changeset to apply the new metadata.

Yes, that sounds do-able. Just submit an issue with details and @JonnyOThanor I will take a look. https://github.com/KSP-CKAN/NetKAN/issues/new/choose Yes.

This is a pretty close guess. CryoTanks was missing a dependency on B9PartSwitch, so we had to add that. And both it and NearFutureSolar had a "Core" module split off with just the plugin, but this was done in a way that could break other mods, so we added a dependency to prevent that as well. Adding dependencies triggers a reinstall. https://github.com/KSP-CKAN/NetKAN/pull/9964 https://github.com/KSP-CKAN/NetKAN/pull/9965

Might be worth noting that in the first part of this, "report" means "post on the forum," while in the second part, "report" means "click the ellipsis → Report button without posting on the forum."

I see, good to know. It'll be interesting to see whether they do any follow-up to check whether the claim is valid. If they go by the license, they may decide to refuse the request. If that happens, let us know and we can use @techman83's API key to delete them. I guess this also puts fans of GU on notice to grab those archived versions while they still can!

I think the hard lesson of experience here is that if you're looking forward to KSS2, then once it is out, it would be wise to make your own backup copies of it before it also becomes unavailable. As one of the people who would normally field such requests, I have heard nothing about this. Did you contact someone about it already? If so, could you please tell me whom, so I can make sure it's someone who can actually follow through? Side note, the license for GU is: ... and the archived files are attributed to you, non-commercial, and unmodified from the originals. May I ask what you feel is objectionable about them?

As the author explained here, it was taken down and replaced by Galaxies Unbound: As the author then explained here, Galaxies Unbound itself was taken down and is planned to be replaced by Kerbal Star Systems 2: Kerbal Star Systems 2 has a thread here, but as yet there is no download: So going by official channels, nothing is currently available to download, but there is an archived copy of Galaxies Unbound here that I think some people have been using: https://archive.org/details/kspckanmods?tab=collection&query=galaxies+unbound&sort=-publicdate

The account still seems to exist: https://forum.kerbalspaceprogram.com/profile/232681-ksre-dev/ So I suppose they somehow got the mods to delete all their posts in this thread instead.

Here's the stickied post that explains how to start writing plugins, including how to set up the references. Good luck!

Take a look at Kerbal Konstructs, which already does that. You might be able to create assets for that mod instead of making your own plugin.

That was fixed in CKAN v1.31.0 (July 2022). Try updating your CKAN. https://github.com/KSP-CKAN/CKAN/releases/latest

Hi, I assume you mean KSRe. Good news, it was added 2 days ago. https://github.com/KSP-CKAN/KSP2-NetKAN/pull/170

Sorry if you already know this (it's hard to tell), but CKAN itself does now support KSP2. I just didn't come back and post an announcement on this thread.

Is either of these things true? I have had several years of experience with KSP1 modders, and it's pretty rare that they would simply outright "refuse" anything, let alone an eminently reasonable suggestion to improve logging.

That's not something CKAN would be capable of causing with a bug. The OS is telling CKAN it can't write to that file, not the other way around.

Yup, perfectly normal on Feb 22 of any year if you have ModuleManager installed.

No, it's fine, this is handled by CKAN and common practice for making providing mods mutually exclusive with one another.

Hi, @RKunze, it's cool that you're working on this! $kref: '#/ckan/netkan/https://raw.githubusercontent.com/Galileo88/JNSQ/master/CKAN/JNSQ.netkan' That line is wrong. It's causing all of JNSQ's custom definitions to be imported into your mod (except for the ones you're explicitly overriding), including the "provides" property you've quoted, which causes the conflict to be applied to your mod: { "spec_version": "v1.4", "identifier": "JNSQ-Rescale-1x", ... "provides": [ "EnvironmentalVisualEnhancements-Config" ], ... } You most likely want this instead, which will give you a clean slate without all the other JNSQ cruft: $kref: '#/ckan/github/Galileo88/JNSQ/asset_match/JNSQ\\..*.zip' (So no, you probably don't need to submit fix PRs to JNSQ or the main NetKAN repo.)

If you're asking what the red and white shape in the image is, I guess I might describe it as a "pennant"? https://www.google.com/search?q=pennant&tbm=isch

This is quite true for some issues, less so for others. For example, probably anybody on the team could fix this one pretty quickly, since it's just rearranging some strings and fixing some comically wrong calculations: If easy (yet very visible) issues like that are going unfixed because everybody is too busy, then I'd say it's reasonable to hope that they will start getting cleaned up as the headline features are wrapped.

Hi, are you asking about CKAN?

Those are the image files. The text is in the save file (persistent.sfs) like this. MODULE { name = FlagSite isEnabled = True placedBy = Gerdo Kerman PlaqueText = Why did that pay so much funds?! stagingEnabled = True state = Placed EVENTS { } ACTIONS { } UPGRADESAPPLIED { } }

Can we? You've only presented two data points. Two points could represent a line, but they can just as easily be quadratic, exponential, logarithmic, or some other more obscure pattern.

Which one?