-
Posts
751 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Status Replies posted by politas
-
Hi StarCrusher96,
We're working through our Spacedock submissions to CKAN at the moment and have gotten to your Kerbol Starsystem mod. It's quite a tricky one to handle in CKAN.
So far, we're just installing the "Main Mod" part and ignoring the options, but I see that you've included a modified GameData/Kopernicus/config/system.cfg file. CKAN does not overwrite files, and the standards for Kopernicus is that you should use ModuleManager AFTER:Kopernicus to change the system config, rather than replacing the file.
-
Hi there!
Sorry for the long delay, but I am just now looking at the Spacedock automated submission of your Fourian Fuel Systems mod to CKAN. The automated process is very limited, and doesn't include things like dependencies or any other relationships, so we often create a fresh pull request.
You've specified that Fourian Fuel Systems requires InterstellarFuelSwitch - am I correct in thinking that it is only the plugin that is actually required?
I also see that your mod uses ModuleManager, so I have put that down as a dependency, too.
Are there any other details about your mod that might cause problems for you from users installing it via CKAN?
-
Hi there,
Very sorry to hear that you took your Deadskins mod down completely due to the CKAN team's policies and actions. I only just realised you had done so.
I've taken references to DeadSkins off of CKAN as per our new policy, and it will not be added back without your approval.
Sorry for the delay, and for any problems the CKAN has caused you.
Myk
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Bob!
Would you like a hand with your CKAN metadata? USITools is failing because there are two .version files being installed. You can specify a specific file in the $vref entry, like this:
"$vref": "#/ckan/ksp-avc/GameData/000_USITools/USITools.version",
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Or is http://spacedock.info/mod/847/Stock Visual Terrain going to be the replacement for the TextureReplacer parts? That seems like a good way to do it.
-
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Hi Berlin,
I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted.
Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.
-
Ok, thanks. Let me have a look at your downloads and I'll get back to you. One issue I find with the last version I have downloaded (0.7.1) is that there are a couple of scatterer config files, but not a complete set. It wouldn't be too hard for us to split out the Scatterer config into a dependency, but in order for SVE to fulfil that dependency, it would need to provide a complete set of scatterer config files (even if most are just the same as the original Scatterer)
CKAN currently won't overwrite any files, whether they're installed by another mod in CKAN, or just happen to exist (So we don't overwrite files in GameData/Squad, for example), we can't just replace the specific files.
-
-
Hi there! I'm a friendly CKAN-wizard offering to help you out with getting your mod listed in CKAN.
Your KRnD.netkan looks pretty good, apart from the license, which I'm guessing you updated after creating it. The reason you're getting JSON deserialisation errors (and I am too), is that your Github releases don't have a packaged ZIP file in the release contents. There is an undocumented feature implemented earlier this year that will let us use your GitHub releases as they are, though.
If you would like to self-host your netkan, so you can update the KSP version compatibility as required, I can submit changes to your netkan file and then add a metanetkan pointer to your github.
Or if you'r rather we CKAN people handle it for you, I can just put all the details into the main Netkan repo.
-
Hi there! I'm a friendly CKAN-wizard offering to help you out with getting your mod listed in CKAN.
Your KRnD.netkan looks pretty good, apart from the license, which I'm guessing you updated after creating it. The reason you're getting JSON deserialisation errors (and I am too), is that your Github releases don't have a packaged ZIP file in the release contents. There is an undocumented feature implemented earlier this year that will let us use your GitHub releases as they are, though.
If you would like to self-host your netkan, so you can update the KSP version compatibility as required, I can submit changes to your netkan file and then add a metanetkan pointer to your github.
Or if you'r rather we CKAN people handle it for you, I can just put all the details into the main Netkan repo.
-
Hi there! I'm a friendly CKAN-wizard offering to help you out with getting your mod listed in CKAN.
Your KRnD.netkan looks pretty good, apart from the license, which I'm guessing you updated after creating it. The reason you're getting JSON deserialisation errors (and I am too), is that your Github releases don't have a packaged ZIP file in the release contents. There is an undocumented feature implemented earlier this year that will let us use your GitHub releases as they are, though.
If you would like to self-host your netkan, so you can update the KSP version compatibility as required, I can submit changes to your netkan file and then add a metanetkan pointer to your github.
Or if you'r rather we CKAN people handle it for you, I can just put all the details into the main Netkan repo.
-
On another point, there is a set of mods we've identified that would fit into the "not 100% compatible" you talk about. It's been suggested that we might set up a "conflicts" relationship like this:
"conflicts" : [ { "name" : "B9AerospaceProceduralParts"}, { "name" : "InterstellarFuelSwitch"}, { "name" : "ProceduralAirships"}, { "name" : "ProceduralDynamics"}, { "name" : "ProceduralFairings"}, { "name" : "ProceduralParts"}, { "name" : "ProceduralParts-Extended"}, { "name" : "ProceduralProbes"}, { "name" : "TweakScale" } ],
Which would prevent your mod and any of those mods being installed at the same time. Would you say that is a reasonable choice, or is the incompatibility too minor to justify a complete block? (I am leaning towards the latter) There is a proposed "warning" relationship that should create a dialogue letting users know about minor compatibility issues, but that may not be implemented for some time.
-
-
I once tried to submit the mod to the ckan-repo (as you can tell by my already included .netkan-file in the git-repo). But the netkan validation-tool always just said "JSON deserialization error", which I was unable to fix. So I just stopped trying a while ago. If there is a ckan-wizard out there who can give me a few pointers or even add the mod for me? That would be greatly appreciated.
Hi there! I'm a friendly CKAN-wizard offering to help you out with getting your mod listed in CKAN.
Your KRnD.netkan looks pretty good, apart from the license, which I'm guessing you updated after creating it. The reason you're getting JSON deserialisation errors (and I am too), is that your Github releases don't have a packaged ZIP file in the release contents. When drafting your releases on Github, there's a text/data entry field taht appears, into which you can click and drag files from your computer. If you make a ZIP file containing just the files a user needs to install (leaving out the source code) and attach it there, CKAN will use that as the download for the release. The Source Code files that are automatically generated are unfortunately not available for downloading.
You can look at my own tiny little mod's github releases to see the difference - You can see that in addition to the "Source Code" zips, there is Sarkomand-1.0.zip in the Downloads section, which is the release zip I created locally and attached to the release when I created it.
-
Ah, turns out I had missed an undocumented feature implemented earlier this year that will let us use your GitHub releases as they are.
If you would like to self-host your netkan, so you can update the KSP version compatibility as required, I can submit changes to your netkan file and then add a metanetkan pointer to your github.
Or if you'r rather we CKAN people handle it for you, I can just put all the details into the main Netkan repo.
-
-
Hi Sobol,
I'm trying to fix up the CKAN metadata for your Space Launch Systems mods. Is the original SLSPartPack meant to only work with Realism Overhaul? I don't understand the distinction between the different packs and the dropbox download and how they should be installed.
-
Hi Sobol,
I'm trying to fix up the CKAN metadata for your Space Launch Systems mods. Is the original SLSPartPack meant to only work with Realism Overhaul? I don't understand the distinction between the different packs and the dropbox download and how they should be installed.