SpaceDock.info (Mod Hosting Site)

[Randazzo]

32 minutes ago, Stone Blue said:

While I agree with your sentiment, and I feel the best thing would be for ALL mod authors to make a forum release thread for ALL mods, I have been seeing an alarming trend, of more and more new mods just being thrown up on Curse, or SpaceDock (before that, it was even happening on KS), with absolutely NO forum thread, or ANY other place where the mod was hosted, or where people could come across it, or discuss it, or even get a basic idea of WHAT the mod was....

Can you give an example? I'm genuinely curious as to why any legit mod-maker would do such a thing.

Also, I cast my lot with the anti-social crowd. No fluff is necessary.

[DMagic]

2 hours ago, hoojiwana said:

Tags are a whole can of worms by themselves, due to the huge variety in KSP mods you either have a few tags that are too vague to be useful, or too many specialised ones. Custom ones like how Steam does it kinda solves that, but I don't think the userbase is anywhere near big enough for that to work. Ratings also have problems since people tend to either rate maximum or minimum based on nothing consistent. For example, someone might give a mod a minimum rating because they installed it wrongly and it broke their game due to no fault of the modder. There's also a problem when everything gets a 5 star rating, it becomes impossible to differentiate between anything.

I love the attention the site is getting beyond mere maintenance, but there are some things that weren't included in the first place (on KS) for good reasons.

I agree. Just look at how tags are used on this forum. Half of the time people just separate the title of the topic into 3 or 4 tags. The same goes for thread ratings.

I've said it on the GitHub issue, but I'll repeat it here. I don't think there should be any form of user-feedback on the site. I think downloads and follower count (which could be seen as a type of user-feedback, but also provides and useful and practical purpose) are good enough for determining popularity.

Anywhere that users are allowed to enter text will end up as another complaint box, just like the user review/feedback things on Curse, and another thing for me to ignore. Maintaining a single, obvious link to the addon forum thread (or maybe GitHub issue tracker) seems like the best option to me.

[Stone Blue]

55 minutes ago, Randazzo said:

Can you give an example? I'm genuinely curious as to why any legit mod-maker would do such a thing.

Just a few off the top of my list (I think all but maybe one or two are from Jun 2015 and later, majority are even more recent):

6 Crew Science Lab

6 Seat Mk3 Cockpit

Balastanks Extended

Ballast Water Tank

Ballistanks

Costly Science

Docking Tube

Jettison Fuel Mod

JSON Kerman

Kinstruments

KW Rocketry Plus

Lander Orientation Improvement

Mk2 Solar Batteries

Mk3 KIS Cargo Containers

Module Solar Tracking

Rotating Mk2 Ring

Rover Speed

Sepratron MKII

ShowFPS

Solar Panel Deployer

Stackable Fuel Cells

Submarine Systems

Trizzle AeroSpace Company

Wing Drop Tanks     EDIT: I HATE THIS NEW FORUM!!!!!!!!   AARRRGGGHHHHHHHHH!!!!

Edited March 1, 2016 by Stone Blue

[Stone Blue]

1 hour ago, Randazzo said:

Can you give an example? I'm genuinely curious as to why any legit mod-maker would do such a thing.

Also, I cast my lot with the anti-social crowd. No fluff is necessary.

Just a few off the top of my list (I think all but maybe one or two are from Jun 2015 and later, majority are even more recent):

 

6 Crew Science Lab

6 Seat Mk3 Cockpit

Balastanks Extended

Ballast Water Tank

Ballistanks

Costly Science

Docking Tube

Jettison Fuel Mod

JSON Kerman

Kinstruments

KW Rocketry Plus

Lander Orientation Improvement

Mk2 Solar Batteries

Mk3 KIS Cargo Containers

Module Solar Tracking

Rotating Mk2 Ring

Rover Speed

Sepratron MKII

ShowFPS

Solar Panel Deployer

Stackable Fuel Cells

Submarine Systems Tetrasat

Trizzle AeroSpace Company

Wing Drop Tanks

Edited March 1, 2016 by Stone Blue

[VITAS]

complaint about social featurs noted.

can we get back to the design itself?

e.g. is the top black area to high?

how should it handle responsive design? (what should be removed when it contracts or rearanged where)

are the colors ok?

what about contrast?

does there need to be a dark version?

where to put the menu button on mobile phones? (logo is in the upper left where i would put it)

and so on.

[Stone Blue]

@VITAS Sorry for slipping OT...

1) I like the black area at the top just as it is
2) the text for the "Top Mods", "New Mods", etc could be just a touch larger... Also, if those are clickable, maybe outline them, or tab them?

3) as to the text in the lower half... Gotta stay away from light blue... Need high contrast between text and background, WHATEVER the colors end up being... Also, being a laptop user, and even tho I am on, about the largest laptop screen (17.3"), I think the text needs to be just a couple sizes bigger...

4) I didnt mind the DARK blue color you had in the "SpaceDock" bar at the top...

I know you are going to get ALL sorts of differing opinions on this... Just dont let yourself get frustrated with this... No matter what, not everyone will be happy with the layout...

[VITAS]

i can say the logo and its colors wherent my choice but result of a public vote. i submitted my own designs to it and they didnt make it

the dark blue color of the top bar makes the logo hard to see.

thank you for your heads up. in the end i will do what i think is best and if someone doesnt like functions or colors i will give them the option to ignore them. spacedock isnt ckan on a webpage. if someone wanted to just dl files by name i could simply dump them on some ftp.

[sal_vager]

Pinned for TOTM March @VITAS, congrats

[VITAS]

thank you.

i want to thank my mum, my teacher, and all other ppl who made this possible. you are great

 

heres a spacedock wallpaper im working on:

Edited March 1, 2016 by VITAS

[GenPage]

3 hours ago, DMagic said:

I agree. Just look at how tags are used on this forum. Half of the time people just separate the title of the topic into 3 or 4 tags. The same goes for thread ratings.

I've said it on the GitHub issue, but I'll repeat it here. I don't think there should be any form of user-feedback on the site. I think downloads and follower count (which could be seen as a type of user-feedback, but also provides and useful and practical purpose) are good enough for determining popularity.

Anywhere that users are allowed to enter text will end up as another complaint box, just like the user review/feedback things on Curse, and another thing for me to ignore. Maintaining a single, obvious link to the addon forum thread (or maybe GitHub issue tracker) seems like the best option to me.

While what @VITAS mentioned about social features is very OT. There is obviously a lot of feature requests and things we all want to see out of a mod hosting site. Our team is dedicated to providing the best experience for modders to provide hosting and information about their mod. As we progress out of the initial "OMG WE NEED TO GET UP AND RUNNING" phase, our focus will turn to bug fixes and highly requested features along with a design refresh. There might be some disagreement about prioritization but the topic is always open for civil discussion. 

Also YAY TOTM! Thank you @sal_vager

[Monkthespy]

I would recommend just one social feature, which is "report as broken" or "not functioning well". I suppose after a certain threshold of a number of these reports a little red/yellow/green tick would pop up a warning users that other users think the mod is currently broken. The counter should probably get reset after any update, although this could be abused, but I don't see a reason why you would try to abuse it. For the mod author, the reports could have a little text box that sends it to the mod author telling them why the user thinks its broken. If needed (maybe like a brigade) the mod author could send a complaint to the admins requesting the counter to be reset or something like that.

Another is something simple, the mod author could mark it as experimental, beta, or full release, and it would obviously show up for the user. This could be expanded as well, allowing a mod author to put warnings that aren't in the description and should catch the users attention (maybe a big red box).

Just some of my thoughts.

[legoclone09]

8 hours ago, Monkthespy said:

I would recommend just one social feature, which is "report as broken" or "not functioning well". I suppose after a certain threshold of a number of these reports a little red/yellow/green tick would pop up a warning users that other users think the mod is currently broken. The counter should probably get reset after any update, although this could be abused, but I don't see a reason why you would try to abuse it. For the mod author, the reports could have a little text box that sends it to the mod author telling them why the user thinks its broken. If needed (maybe like a brigade) the mod author could send a complaint to the admins requesting the counter to be reset or something like that.

Another is something simple, the mod author could mark it as experimental, beta, or full release, and it would obviously show up for the user. This could be expanded as well, allowing a mod author to put warnings that aren't in the description and should catch the users attention (maybe a big red box).

Just some of my thoughts.

I like that a lot!

[ferram4]

Allow me to be opposed to a "not working" button for a simple reason: 99% of the reports are going to have little to no explanation of what went wrong and will be utterly useless to modders in actually figuring out what went wrong and that method will discourage people from bothering to report on the forums or github where things can be followed up.  It's no different than adding a commenting system: it's another place for bug reports to show up, and modders aren't going to check them all, which interferes with getting bugs fixed, which is worse for users.  Be good at hosting and finding mods and that's it; don't engage in scope creep.

As for layout, frankly, until it's being used it's gonna be difficult to tell the actual problems that are gonna slip through.  As for the colors, I guess it works, but I'm tired of seeing facebook/forum/blue-white color schemes everywhere.

[Monkthespy]

2 minutes ago, ferram4 said:

Allow me to be opposed to a "not working" button for a simple reason: 99% of the reports are going to have little to no explanation of what went wrong and will be utterly useless to modders in actually figuring out what went wrong and that method will discourage people from bothering to report on the forums or github where things can be followed up.  It's no different than adding a commenting system: it's another place for bug reports to show up, and modders aren't going to check them all, which interferes with getting bugs fixed, which is worse for users.  Be good at hosting and finding mods and that's it; don't engage in scope creep.

As for layout, frankly, until it's being used it's gonna be difficult to tell the actual problems that are gonna slip through.  As for the colors, I guess it works, but I'm tired of seeing facebook/forum/blue-white color schemes everywhere.

Yeah, I see your point. The problem is I don't think (like you said) people would understand what the button is for. It's not for just normal bug reporting but if the whole mod is malfunctioning and not working. But alas, I don't think they will understand that.

The only solution would be if a sufficient number of reports come in an actual admin goes in and tests the mod, although this would get out of hand real fast. It would have to all be moderated which I don't think Spacedock admins have the manpower to do. Still, maybe there is a good implementation of this but I don't know.

[TiktaalikDreaming]

44 minutes ago, ferram4 said:

Allow me to be opposed to a "not working" button for a simple reason: 99% of the reports are going to have little to no explanation of what went wrong and will be utterly useless to modders in actually figuring out what went wrong and that method will discourage people from bothering to report on the forums or github where things can be followed up.  It's no different than adding a commenting system: it's another place for bug reports to show up, and modders aren't going to check them all, which interferes with getting bugs fixed, which is worse for users.  Be good at hosting and finding mods and that's it; don't engage in scope creep.

As for layout, frankly, until it's being used it's gonna be difficult to tell the actual problems that are gonna slip through.  As for the colors, I guess it works, but I'm tired of seeing facebook/forum/blue-white color schemes everywhere.

I'm with @ferram4 on this.  The "Forum link" has always been (IMHO) the indicated spot to air complaints, bug reports, etc.  Having a bunch of different places to track for bug reports would be a pain in the proverbial.  And, as per terms of use etc etc, all mods should really have a forum topic, and that's where it makes sense to have discussion about the mod, bug-reports, usage issues etc.

I'm not averse to having a bug report feature on spacedock, if it can be turned on or off per mod.  It might work for some mod authors.  But I think it's a good idea to encourage the use of the KSP forums for most mods.

[Stone Blue]

I'll also add, dont forget a couple of the biggest reasons people seem NOT to like Curse/Curseforge, and why they seemed to like KS, is the cluttered interface, and all the extra "fluff" on Curse's pages...  KerbalStuff had a simple, elegant interface.... for a more civilized age...

Edited March 2, 2016 by Stone Blue

[Elway358]

17 hours ago, VITAS said:

spacedock isnt ckan on a webpage. if someone wanted to just dl files by name i could simply dump them on some ftp.

From what I see, I honestly think that IS what most people want. I don't have much of a dog in this hunt because I just find a mod I want on these forums and then get it from CKAN, but I think the "vision" for what you guys are wanting Spacedock to be is starting to take a hard right turn from what the people who will be using it want it to be.

I have to agree that all the social feature stuff is pure junk in my eyes. I 100% despise twitter, facebook, insta bla bla bla, ratings, likes, etc. being mixed in with my gaming. The ONLY(useful) feature missing from your site at the moment is a good search/sort option for the mods. Adding that would actually make the site a one-stop shop for FINDING new mods as well as easily downloading them. As it stands now, you have to know what mod you even want for the site to be close to useful for an end user. Anything else added would be nothing but bloat IMO.

I can't thank you guys enough for getting all the mods back up very quickly and for your excellent support of CKAN but as for some of the proposals for the future of Spacedock, I think they would deter users more than they would encourage them to use the site. Obviously you should take my opinion as someone who only uses a handful of mods, so value it accordingly. Just my 2 pennies  

P.S. I've posted this before but it's worth adding again that I STRONGLY suggest you use KerbalX as an example of a site that has a stellar search/sort ability. the "tags" will be more "social flavored garbage" IMO. Unless you totally restrict tags to a few presets, it's gonna be a #makewhatevertagiwantcauseitscool nightmare.

Edited March 2, 2016 by Elway358
added Kerbalx bit

[Olympic1]

On 28-2-2016 at 4:32 AM, Mokmo said:

BIG HEADS UP FOR THE DEVS 

I just got a mod-update e-mail and the "to" field has over a dozen adresses visible. Seems your e-mail is misconfigured. 

@godarklight has fixed this by calling the "send_mail" directly due to caching issues. This fix is temporarily untill we can figure it out.

[VITAS]

if you wnt you can continue having wild fantasies about SD becoming some sort of facebook or github issue report thingy....or you could tell me something about the colors and layout of my screen (you could even make your own screens and post them).

its up to you

btw this forum IS social media

[Lelo]

As much as I appreciate this great project, I have an honest question: why is Curse hated so much?

Edited March 2, 2016 by Lelo

[Elway358]

8 minutes ago, VITAS said:

if you wnt you can continue having wild fantasies about SD becoming some sort of facebook or github issue report thingy....or you could tell me something about the colors and layout of my screen (you could even make your own screens and post them).

its up to you

btw this forum IS social media

Just giving you an observation from outside of your bubble is all. Colors should be a very very small side issue tbh. Colors that people don't like more than likely will not stop them from using a good site. On the other hand, a nice colored site that's a pile of useless fluff that is already handled better by other sites will be just that.

Again, I thank you all for getting the mods back up quickly and having CKAN integrated nicely. Other than that, I'll step aside and let you color  

[VITAS]

My small cdn test setup for spacedock:

[godarklight]

18 hours ago, Lelo said:

As much as I appreciate this great project, I have an honest question: why is Curse hated so much?

To be honest, I'm not completely sure - Curse *works*, and thats mostly all modders care about. Some are ideologically opposed to curse, but I am not, and I use curse myself. I'm sure most of the other spacedock members feel the same way - we just offer an alternative.

 

As for social media features, this is one case where I'm 100% with @ferram4 here, It's another place for bug reports to pop up and we like keeping things all in once place, so I'd be against any form of commenting system or trying to be "social media-y", as we are a mod hoster, not a social network platform.

[TiktaalikDreaming]

20 hours ago, Lelo said:

As much as I appreciate this great project, I have an honest question: why is Curse hated so much?

I don't know about others, but for me, I'll basically use the simplest site with the least advertising.  There's a trade off if those two don't match up.  I don't know if I can give a clear numerical analysis.  Basically, I'm against the pervasive third party ads that tend to be on websites.  Mostly due to them being the main attack vector for compromising systems.  And I've known too many people involved in advertising.  And then simple is good, for everyone.

Curse is overly complex, and ad supported.  I don't blame them, but if I have a choice, I'll choose other.

[CyberFoxx]

Not sure if this is a problem on CKAN's end, or SpaceDock's end, so I'll be posting this in both threads:

$ ./ckan.exe install CustomClusters --verbose
311 [1] INFO CKAN.CmdLine.MainClass (null) - Verbose logging enabled
367 [1] INFO CKAN.CmdLine.MainClass (null) - Using KSP install at /home/cyberfoxx/.local/share/Steam/steamapps/common/Kerbal Space Program
2748 [1] INFO CKAN.Registry (null) - Not registering GameData/ModuleManager.2.6.20.dll, it belongs to ModuleManager
2748 [1] INFO CKAN.Registry (null) - Registering PartIconFixer_1_2 from GameData/PartIconFixer_1_2.dll
2749 [1] INFO CKAN.Registry (null) - Not registering GameData/000_FilterExtensions/FilterExtensions.dll, it belongs to FilterExtensions
2756 [1] INFO CKAN.Registry (null) - Not registering GameData/000_Toolbar/Toolbar.dll, it belongs to Toolbar
2757 [1] INFO CKAN.Registry (null) - Not registering GameData/000_USITools/DynamicTanks.dll, it belongs to USITools
2757 [1] INFO CKAN.Registry (null) - Not registering GameData/000_USITools/USITools.dll, it belongs to USITools
2774 [1] INFO CKAN.Registry (null) - Not registering GameData/ASET/ASET_Props/Plugin/ASETPropsIdentifier.dll, it belongs to ASETProps
2776 [1] INFO CKAN.Registry (null) - Not registering GameData/AntennaRange/ARVoidPanel.dll, it belongs to AntennaRange
2776 [1] INFO CKAN.Registry (null) - Not registering GameData/AntennaRange/AntennaRange.dll, it belongs to AntennaRange
2776 [1] INFO CKAN.Registry (null) - Registering AstrotechUtilities from GameData/Astrotech/AstrotechUtilities.dll
2776 [1] INFO CKAN.Registry (null) - Registering CareerLite from GameData/Astrotech/CareerLite/plugins/CareerLite.dll
2777 [1] INFO CKAN.Registry (null) - Not registering GameData/AutoRove/AutoRove.dll, it belongs to AutoRove
2777 [1] INFO CKAN.Registry (null) - Not registering GameData/BahaSP/Plugins/BDAnimationModules.dll, it belongs to BDAnimationModules
2778 [1] INFO CKAN.Registry (null) - Not registering GameData/BetterBurnTime/BetterBurnTime.dll, it belongs to BetterBurnTime
2779 [1] INFO CKAN.Registry (null) - Not registering GameData/CapCom/CapCom.dll, it belongs to CapCom
2780 [1] INFO CKAN.Registry (null) - Not registering GameData/ContractConfigurator/CC_RemoteTech.dll, it belongs to ContractConfigurator
2780 [1] INFO CKAN.Registry (null) - Not registering GameData/ContractConfigurator/ContractConfigurator.dll, it belongs to ContractConfigurator
2780 [1] INFO CKAN.Registry (null) - Not registering GameData/ContractConfigurator/MiniAVC.dll, it belongs to ContractConfigurator
2784 [1] INFO CKAN.Registry (null) - Not registering GameData/ContractPacks/AnomalySurveyor/AnomalySurveyor.dll, it belongs to ContractConfigurator-AnomalySurveyor
2786 [1] INFO CKAN.Registry (null) - Not registering GameData/ContractPacks/KFiles/MiniAVC.dll, it belongs to ContractConfigurator-KFiles
2786 [1] INFO CKAN.Registry (null) - Not registering GameData/ContractPacks/KerbinSpaceStation/MiniAVC.dll, it belongs to ContractConfigurator-KerbinSpaceStation
2787 [1] INFO CKAN.Registry (null) - Not registering GameData/ContractPacks/Spacetux/UnmannedContracts/UnmannedContracts.dll, it belongs to ContractConfigurator-UnmannedContracts
2788 [1] INFO CKAN.Registry (null) - Not registering GameData/ContractsWindow/ContractsWindow.dll, it belongs to ContractsWindowPlus
2856 [1] INFO CKAN.Registry (null) - Not registering GameData/CryoEngines/Versioning/MiniAVC.dll, it belongs to CryoEngines
2857 [1] INFO CKAN.Registry (null) - Not registering GameData/CryoTanks/Plugins/SimpleBoiloff.dll, it belongs to CryoTanks
2857 [1] INFO CKAN.Registry (null) - Not registering GameData/CustomBarnKit/CustomBarnKit.dll, it belongs to CustomBarnKit
2857 [1] INFO CKAN.Registry (null) - Not registering GameData/DMagicOrbitalScience/Plugins/DMagic.dll, it belongs to DMagicOrbitalScience
2861 [1] INFO CKAN.Registry (null) - Not registering GameData/DPSoundFX/Plugins/DockingSounds.dll, it belongs to DockingSounds
2861 [1] INFO CKAN.Registry (null) - Not registering GameData/DefaultActionGroups/DefaultActionGroups.dll, it belongs to DefaultActionGroups
2862 [1] INFO CKAN.Registry (null) - Not registering GameData/DeployableEngines/Plugins/DeployableEngines.dll, it belongs to DeployableEngines
2862 [1] INFO CKAN.Registry (null) - Not registering GameData/Diazo/AGExt/AGExt.dll, it belongs to AGExt
2862 [1] INFO CKAN.Registry (null) - Not registering GameData/Diazo/AGExt/kOSVoidAction.dll, it belongs to AGExt
2862 [1] INFO CKAN.Registry (null) - Not registering GameData/Diazo/ActsEW/ActsEW.dll, it belongs to ActsEW
2862 [1] INFO CKAN.Registry (null) - Not registering GameData/Diazo/AutoAction/AutoAction.dll, it belongs to AutoAction
2863 [1] INFO CKAN.Registry (null) - Not registering GameData/Diazo/LandingHeight/LandingHeight.dll, it belongs to LandingHeight
2863 [1] INFO CKAN.Registry (null) - Not registering GameData/DistantObject/DistantObject.dll, it belongs to DistantObject
2863 [1] INFO CKAN.Registry (null) - Not registering GameData/EVAEnhancements/EVAEnhancements.dll, it belongs to EVAEnhancements
2863 [1] INFO CKAN.Registry (null) - Not registering GameData/EVAManager/EVAManager.dll, it belongs to EVAManager
2863 [1] INFO CKAN.Registry (null) - Not registering GameData/EVA_OK/EVA_OK.dll, it belongs to EVAOK
2864 [1] INFO CKAN.Registry (null) - Not registering GameData/EditorExtensionsRedux/EditorExtensionsRedux.dll, it belongs to EditorExtensionsRedux
2864 [1] INFO CKAN.Registry (null) - Not registering GameData/EditorExtensionsRedux/MiniAVC.dll, it belongs to EditorExtensionsRedux
2864 [1] INFO CKAN.Registry (null) - Not registering GameData/EngineLight/EngineLight.dll, it belongs to EngineLighting
2864 [1] INFO CKAN.Registry (null) - Not registering GameData/EngineLight/MiniAVC.dll, it belongs to EngineLighting
2864 [1] INFO CKAN.Registry (null) - Not registering GameData/EnhancedNavBall/Plugins/EnhancedNavBall.dll, it belongs to EnhancedNavBall
2865 [1] INFO CKAN.Registry (null) - Not registering GameData/EnvironmentalVisualEnhancements/Plugins/Atmosphere.dll, it belongs to EnvironmentalVisualEnhancements
2865 [1] INFO CKAN.Registry (null) - Not registering GameData/EnvironmentalVisualEnhancements/Plugins/CelestialShadows.dll, it belongs to EnvironmentalVisualEnhancements
2865 [1] INFO CKAN.Registry (null) - Not registering GameData/EnvironmentalVisualEnhancements/Plugins/CityLights.dll, it belongs to EnvironmentalVisualEnhancements
2865 [1] INFO CKAN.Registry (null) - Not registering GameData/EnvironmentalVisualEnhancements/Plugins/EVEManager.dll, it belongs to EnvironmentalVisualEnhancements
2865 [1] INFO CKAN.Registry (null) - Not registering GameData/EnvironmentalVisualEnhancements/Plugins/PQSManager.dll, it belongs to EnvironmentalVisualEnhancements
2865 [1] INFO CKAN.Registry (null) - Not registering GameData/EnvironmentalVisualEnhancements/Plugins/ShaderLoader.dll, it belongs to EnvironmentalVisualEnhancements
2865 [1] INFO CKAN.Registry (null) - Not registering GameData/EnvironmentalVisualEnhancements/Plugins/Terrain.dll, it belongs to EnvironmentalVisualEnhancements
2865 [1] INFO CKAN.Registry (null) - Not registering GameData/EnvironmentalVisualEnhancements/Plugins/Utils.dll, it belongs to EnvironmentalVisualEnhancements
2865 [1] INFO CKAN.Registry (null) - Not registering GameData/FieldExperience/FieldExperience.dll, it belongs to FieldExperience
2866 [1] INFO CKAN.Registry (null) - Not registering GameData/Firespitter/Plugins/Firespitter.dll, it belongs to FirespitterCore
2866 [1] INFO CKAN.Registry (null) - Not registering GameData/FlagRotate/FlagRotate.dll, it belongs to FlagRotate
2866 [1] INFO CKAN.Registry (null) - Not registering GameData/GCMonitor/GCMonitor.dll, it belongs to GCMonitor
2866 [1] INFO CKAN.Registry (null) - Not registering GameData/GravityTurn/Plugins/GravityTurn.dll, it belongs to GravityTurn
2867 [1] INFO CKAN.Registry (null) - Not registering GameData/HangarGrid/Plugins/HangarGrid.dll, it belongs to HangarGrid
2869 [1] INFO CKAN.Registry (null) - Not registering GameData/HeatControl/Versioning/MiniAVC.dll, it belongs to HeatControl
2871 [1] INFO CKAN.Registry (null) - Not registering GameData/HideEmptyTechNodes/HideEmptyTechNodes.dll, it belongs to HideEmptyTechNodes
2871 [1] INFO CKAN.Registry (null) - Not registering GameData/HotSpot/Plugins/HotSpot.dll, it belongs to HotSpot
2872 [1] INFO CKAN.Registry (null) - Not registering GameData/HullCameraVDS/Plugins/HullCamera.dll, it belongs to HullcamVDS
2873 [1] INFO CKAN.Registry (null) - Not registering GameData/InterstellarFuelSwitch/Plugins/InterstellarFuelSwitch.dll, it belongs to InterstellarFuelSwitch-Core
2873 [1] INFO CKAN.Registry (null) - Not registering GameData/InterstellarFuelSwitch/Plugins/MiniAVC.dll, it belongs to InterstellarFuelSwitch-Core
2873 [1] INFO CKAN.Registry (null) - Not registering GameData/InterstellarFuelSwitch/Plugins/Scale_Redist.dll, it belongs to InterstellarFuelSwitch-Core
2876 [1] INFO CKAN.Registry (null) - Not registering GameData/JSI/RasterPropMonitor/Plugins/RasterPropMonitor.dll, it belongs to RasterPropMonitor-Core
2877 [1] INFO CKAN.Registry (null) - Not registering GameData/KAS/Plugins/KAS.dll, it belongs to KAS
2877 [1] INFO CKAN.Registry (null) - Not registering GameData/KAS/Plugins/MiniAVC.dll, it belongs to KAS
2880 [1] INFO CKAN.Registry (null) - Not registering GameData/KIS/Plugins/KIS.dll, it belongs to KIS
2880 [1] INFO CKAN.Registry (null) - Not registering GameData/KIS/Plugins/MiniAVC.dll, it belongs to KIS
2881 [1] INFO CKAN.Registry (null) - Not registering GameData/KSP-AVC/KSP-AVC.dll, it belongs to KSP-AVC
2883 [1] INFO CKAN.Registry (null) - Not registering GameData/KerbalAtomics/Versioning/MiniAVC.dll, it belongs to KerbalAtomics
2883 [1] INFO CKAN.Registry (null) - Not registering GameData/KerbalEngineer/KerbalEngineer.dll, it belongs to KerbalEngineerRedux
2883 [1] INFO CKAN.Registry (null) - Not registering GameData/KerbalEngineer/MiniAVC.dll, it belongs to KerbalEngineerRedux
2884 [1] INFO CKAN.Registry (null) - Not registering GameData/KerbalJointReinforcement/Plugin/KerbalJointReinforcement.dll, it belongs to KerbalJointReinforcement
2885 [1] INFO CKAN.Registry (null) - Not registering GameData/KerbalKonstructs/KerbalKonstructs.dll, it belongs to KerbalKonstructs
2890 [1] INFO CKAN.Registry (null) - Not registering GameData/KerbalRenamer/plugins/Renamer.dll, it belongs to KerbalRenamer
2890 [1] INFO CKAN.Registry (null) - Not registering GameData/KerbalStats/Plugins/KerbalStats.dll, it belongs to KerbalStats
2890 [1] INFO CKAN.Registry (null) - Not registering GameData/Kerbaltek/HyperEdit_1.4.2.dll, it belongs to HyperEdit
2891 [1] INFO CKAN.Registry (null) - Not registering GameData/KerboKatz/KerboKatzUtilities.dll, it belongs to KerboKatzUtilities
2891 [1] INFO CKAN.Registry (null) - Not registering GameData/KerboKatz/CraftHistory/CraftHistory.dll, it belongs to CraftHistory
2892 [1] INFO CKAN.Registry (null) - Not registering GameData/KerboKatz/ForScienceContinued/ForScienceContinued.dll, it belongs to ForScienceContinued
2894 [1] INFO CKAN.Registry (null) - Not registering GameData/KerboKatz/RecoverAll/RecoverAll.dll, it belongs to RecoverAll
2894 [1] INFO CKAN.Registry (null) - Not registering GameData/KerboKatz/SmallUtilities/AutoBalancingLandingLeg/AutoBalancingLandingLeg.dll, it belongs to KerboKatzSmallUtilities-AutoBalancingLandingLeg
2894 [1] INFO CKAN.Registry (null) - Not registering GameData/KerboKatz/SmallUtilities/FillSpotsWithTourists/FillSpotsWithTourists.dll, it belongs to KerboKatzSmallUtilities-FillSpotsWithTourists
2895 [1] INFO CKAN.Registry (null) - Not registering GameData/KerboKatz/SmallUtilities/PhysicalTimeRatioViewer/PhysicalTimeRatioViewer.dll, it belongs to KerboKatzSmallUtilities-PhysicalTimeRatioViewer
2895 [1] INFO CKAN.Registry (null) - Not registering GameData/Klockheed_Martian_Gimbal/Plugins/km_Gimbal.dll, it belongs to KlockheedMartian-Gimbal
2895 [1] INFO CKAN.Registry (null) - Registering KspPlayers from GameData/KspPlayers/KspPlayers.dll
2896 [1] INFO CKAN.Registry (null) - Registering MiniAVC from GameData/KspPlayers/MiniAVC.dll
2897 [1] INFO CKAN.Registry (null) - Not registering GameData/LightsOut/LightsOut.dll, it belongs to LightsOut
2900 [1] INFO CKAN.Registry (null) - Not registering GameData/MagicSmokeIndustries/Plugins/InfernalRobotics.dll, it belongs to InfernalRobotics
2900 [1] INFO CKAN.Registry (null) - Not registering GameData/MagicSmokeIndustries/Plugins/KSPAPIExtensions.dll, it belongs to InfernalRobotics
2900 [1] INFO CKAN.Registry (null) - Not registering GameData/MagicSmokeIndustries/Plugins/Scale_Redist.dll, it belongs to InfernalRobotics
2903 [1] INFO CKAN.Registry (null) - Not registering GameData/MechJeb2/Plugins/MechJeb2.dll, it belongs to MechJeb2
2910 [1] INFO CKAN.Registry (null) - Not registering GameData/NRAP/Plugins/NRAP.dll, it belongs to KerbalNRAP
2912 [1] INFO CKAN.Registry (null) - Not registering GameData/NavyFish/Plugins/Docking Port Alignment Indicator/DPAI_RPM.dll, it belongs to DockingPortAlignmentIndicator
2912 [1] INFO CKAN.Registry (null) - Not registering GameData/NavyFish/Plugins/Docking Port Alignment Indicator/DockingPortAlignment.dll, it belongs to DockingPortAlignmentIndicator
2912 [1] INFO CKAN.Registry (null) - Not registering GameData/NavyFish/Plugins/Docking Port Alignment Indicator/MiniAVC.dll, it belongs to DockingPortAlignmentIndicator
2912 [1] INFO CKAN.Registry (null) - Not registering GameData/NavyFish/Plugins/Docking Port Alignment Indicator/ModuleDockingNodeNamed.dll, it belongs to DockingPortAlignmentIndicator
2915 [1] INFO CKAN.Registry (null) - Not registering GameData/NearFutureConstruction/Versioning/MiniAVC.dll, it belongs to NearFutureConstruction
2918 [1] INFO CKAN.Registry (null) - Not registering GameData/NearFutureElectrical/Plugins/NearFutureElectrical.dll, it belongs to NearFutureElectrical-Core
2918 [1] INFO CKAN.Registry (null) - Not registering GameData/NearFutureElectrical/Versioning/MiniAVC.dll, it belongs to NearFutureElectrical
2929 [1] INFO CKAN.Registry (null) - Not registering GameData/NearFuturePropulsion/Plugins/KSPAPIExtensions.dll, it belongs to NearFuturePropulsion
2929 [1] INFO CKAN.Registry (null) - Not registering GameData/NearFuturePropulsion/Plugins/NearFuturePropulsion.dll, it belongs to NearFuturePropulsion
2930 [1] INFO CKAN.Registry (null) - Not registering GameData/NearFuturePropulsion/Versioning/MiniAVC.dll, it belongs to NearFuturePropulsion
2931 [1] INFO CKAN.Registry (null) - Not registering GameData/NearFutureSolar/Plugins/NearFutureSolar.dll, it belongs to NearFutureSolar-Core
2931 [1] INFO CKAN.Registry (null) - Not registering GameData/NearFutureSolar/Versioning/MiniAVC.dll, it belongs to NearFutureSolar
2933 [1] INFO CKAN.Registry (null) - Not registering GameData/NearFutureSpacecraft/Versioning/MiniAVC.dll, it belongs to NearFutureSpacecraft
2933 [1] INFO CKAN.Registry (null) - Not registering GameData/Nereid/FinalFrontier/Plugins/FinalFrontier.dll, it belongs to FinalFrontier
2945 [1] INFO CKAN.Registry (null) - Not registering GameData/Nereid/S.A.V.E/Plugins/S.A.V.E.dll, it belongs to SAVE
2947 [1] INFO CKAN.Registry (null) - Not registering GameData/PartCommander/PartCommander.dll, it belongs to PartCommander
2948 [1] INFO CKAN.Registry (null) - Not registering GameData/PlanetShine/Plugins/MiniAVC.dll, it belongs to PlanetShine
2948 [1] INFO CKAN.Registry (null) - Not registering GameData/PlanetShine/Plugins/PlanetShine.dll, it belongs to PlanetShine
2954 [1] INFO CKAN.Registry (null) - Not registering GameData/PlanetaryBaseInc/Plugins/PlanetarySurfaceStructures.dll, it belongs to KerbalPlanetaryBaseSystems
2955 [1] INFO CKAN.Registry (null) - Not registering GameData/PortraitStats/PortraitStats.dll, it belongs to PortraitStats
2956 [1] INFO CKAN.Registry (null) - Not registering GameData/PreciseNode/plugins/PreciseNode.dll, it belongs to PreciseNode
2956 [1] INFO CKAN.Registry (null) - Not registering GameData/ProceduralFairings/KSPAPIExtensions.dll, it belongs to ProceduralFairings
2956 [1] INFO CKAN.Registry (null) - Not registering GameData/ProceduralFairings/ProceduralFairings.dll, it belongs to ProceduralFairings
2958 [1] INFO CKAN.Registry (null) - Not registering GameData/ProceduralParts/Plugins/KSPAPIExtensions.dll, it belongs to ProceduralParts
2958 [1] INFO CKAN.Registry (null) - Not registering GameData/ProceduralParts/Plugins/ProceduralParts.dll, it belongs to ProceduralParts
2958 [1] INFO CKAN.Registry (null) - Not registering GameData/ProgressParser/ProgressParser.dll, it belongs to ProgressParser
2958 [1] INFO CKAN.Registry (null) - Not registering GameData/QuantumStrutsContinued/Plugins/QuantumStrutsContinued.dll, it belongs to QuantumStrutsContinued
2959 [1] INFO CKAN.Registry (null) - Not registering GameData/QuickBrake/Plugins/QuickBrake.dll, it belongs to QuickBrake
2959 [1] INFO CKAN.Registry (null) - Not registering GameData/QuickExit/Plugins/QuickExit.dll, it belongs to QuickExit
2959 [1] INFO CKAN.Registry (null) - Not registering GameData/QuickScroll/Plugins/QuickScroll.dll, it belongs to QuickScroll
2959 [1] INFO CKAN.Registry (null) - Not registering GameData/QuickSearch/Plugins/QuickSearch.dll, it belongs to QuickSearch
2960 [1] INFO CKAN.Registry (null) - Not registering GameData/QuickSearch/Plugins/QuickSearch2.dll, it belongs to QuickSearch
2960 [1] INFO CKAN.Registry (null) - Not registering GameData/RCSBuildAid/Plugins/RCSBuildAid.dll, it belongs to RCSBuildAid
2960 [1] INFO CKAN.Registry (null) - Not registering GameData/RCSBuildAid/Plugins/RCSBuildAidToolbar.dll, it belongs to RCSBuildAid
2960 [1] INFO CKAN.Registry (null) - Not registering GameData/REPOSoftTech/AmpYear/MiniAVC.dll, it belongs to AmpYearPowerManager
2961 [1] INFO CKAN.Registry (null) - Not registering GameData/REPOSoftTech/AmpYear/Plugins/AYInterfaces.dll, it belongs to AmpYearPowerManager
2961 [1] INFO CKAN.Registry (null) - Not registering GameData/REPOSoftTech/AmpYear/Plugins/AmpYear.dll, it belongs to AmpYearPowerManager
2962 [1] INFO CKAN.Registry (null) - Not registering GameData/REPOSoftTech/DeepFreeze/MiniAVC.dll, it belongs to DeepFreeze
2963 [1] INFO CKAN.Registry (null) - Not registering GameData/REPOSoftTech/DeepFreeze/Plugins/DFInterface.dll, it belongs to DeepFreeze
2963 [1] INFO CKAN.Registry (null) - Not registering GameData/REPOSoftTech/DeepFreeze/Plugins/DeepFreeze.dll, it belongs to DeepFreeze
2963 [1] INFO CKAN.Registry (null) - Not registering GameData/REPOSoftTech/DeepFreeze/Plugins/SMInterface.dll, it belongs to DeepFreeze
2964 [1] INFO CKAN.Registry (null) - Not registering GameData/REPOSoftTech/KabinKraziness/Plugins/KKInterfaces.dll, it belongs to AmpYearPowerManager
2969 [1] INFO CKAN.Registry (null) - Not registering GameData/RcsSounds/Plugins/RcsSounds.dll, it belongs to RCSSounds
2970 [1] INFO CKAN.Registry (null) - Not registering GameData/RealChute/Plugins/RealChute.dll, it belongs to RealChute
2980 [1] INFO CKAN.Registry (null) - Not registering GameData/SCANsat/Plugins/SCANmechjeb.dll, it belongs to SCANsat
2980 [1] INFO CKAN.Registry (null) - Not registering GameData/SCANsat/Plugins/SCANsat.dll, it belongs to SCANsat
2981 [1] INFO CKAN.Registry (null) - Not registering GameData/SETIcontracts/MiniAVC.dll, it belongs to SETI-Contracts
2981 [1] INFO CKAN.Registry (null) - Not registering GameData/SETIrebalance/MiniAVC.dll, it belongs to SETI-BalanceMod
2985 [1] INFO CKAN.Registry (null) - Not registering GameData/ShipManifest/Plugins/CLSInterfaces.dll, it belongs to ShipManifest
2985 [1] INFO CKAN.Registry (null) - Not registering GameData/ShipManifest/Plugins/SMInterface.dll, it belongs to ShipManifest
2985 [1] INFO CKAN.Registry (null) - Not registering GameData/ShipManifest/Plugins/ShipManifest.dll, it belongs to ShipManifest
2986 [1] INFO CKAN.Registry (null) - Not registering GameData/SimpleConstruction/Plugins/KSPAPIExtensions.dll, it belongs to SimpleConstruction
2986 [1] INFO CKAN.Registry (null) - Not registering GameData/SimpleConstruction/Plugins/Launchpad.dll, it belongs to SimpleConstruction
2986 [1] INFO CKAN.Registry (null) - Not registering GameData/SmartStage/Plugins/SmartStage.dll, it belongs to SmartStage
2987 [1] INFO CKAN.Registry (null) - Not registering GameData/SmokeScreen/SmokeScreen.dll, it belongs to SmokeScreen
3027 [1] INFO CKAN.Registry (null) - Registering KSPSteamCtrlr from GameData/Squad/Plugins/KSPSteamCtrlr.dll
3027 [1] INFO CKAN.Registry (null) - Registering Steamworks from GameData/Squad/Plugins/Steamworks.NET.dll
3036 [1] INFO CKAN.Registry (null) - Not registering GameData/StageRecovery/StageRecovery.dll, it belongs to StageRecovery
3036 [1] INFO CKAN.Registry (null) - Not registering GameData/StockBugFixPlus/StockBugFixPlusController.dll, it belongs to StockBugFixPlus
3036 [1] INFO CKAN.Registry (null) - Not registering GameData/StockBugFixPlus/InFlightHighlightOff/InFlightHighlightOff.dll, it belongs to StockBugFixPlus
3037 [1] INFO CKAN.Registry (null) - Not registering GameData/StockBugFixPlus/ModuleAeroSurfacePlus/ModuleAeroSurfacePlus.dll, it belongs to StockBugFixPlus
3037 [1] INFO CKAN.Registry (null) - Not registering GameData/StockBugFixPlus/ModuleControlSurfacePlus/ModuleControlSurfacePlus.dll, it belongs to StockBugFixPlus
3037 [1] INFO CKAN.Registry (null) - Not registering GameData/StockBugFixPlus/ModuleGimbalPlus/ModuleGimbalPlus.dll, it belongs to StockBugFixPlus
3037 [1] INFO CKAN.Registry (null) - Not registering GameData/StockBugFixPlus/ModuleParachutePlus/ModuleParachutePlus.dll, it belongs to StockBugFixPlus
3037 [1] INFO CKAN.Registry (null) - Not registering GameData/StockBugFixPlus/ModuleProceduralFairingFix/ModuleProceduralFairingFix.dll, it belongs to StockBugFixPlus
3037 [1] INFO CKAN.Registry (null) - Not registering GameData/StockBugFixPlus/ModuleWheelPlus/ModuleWheelPlus.dll, it belongs to StockBugFixPlus
3037 [1] INFO CKAN.Registry (null) - Not registering GameData/StockBugFixPlus/PilotRSASFix/PilotRSASFix.dll, it belongs to StockBugFixPlus
3037 [1] INFO CKAN.Registry (null) - Not registering GameData/StockBugFixPlus/SymmetryActionFix/SymmetryActionFix.dll, it belongs to StockBugFixPlus
3037 [1] INFO CKAN.Registry (null) - Not registering GameData/StockClamshellFairings/StockClamshellFairings.dll, it belongs to StockClamshellFairings
3038 [1] INFO CKAN.Registry (null) - Not registering GameData/SurfaceLights/SurfaceLights.dll, it belongs to surfacelights
3039 [1] INFO CKAN.Registry (null) - Not registering GameData/TacFuelBalancer/MiniAVC.dll, it belongs to TacFuelBalancer
3039 [1] INFO CKAN.Registry (null) - Not registering GameData/TacFuelBalancer/TacFuelBalancer.dll, it belongs to TacFuelBalancer
3039 [1] INFO CKAN.Registry (null) - Not registering GameData/TakeCommand/TakeCommand.dll, it belongs to TakeCommand
3039 [1] INFO CKAN.Registry (null) - Not registering GameData/TarsierSpaceTech/MiniAVC.dll, it belongs to TarsierSpaceTechnologyWithGalaxies
3039 [1] INFO CKAN.Registry (null) - Not registering GameData/TarsierSpaceTech/TarsierSpaceTech.dll, it belongs to TarsierSpaceTechnologyWithGalaxies
3041 [1] INFO CKAN.Registry (null) - Not registering GameData/TextureReplacer/Plugins/TextureReplacer.dll, it belongs to TextureReplacer
3044 [1] INFO CKAN.Registry (null) - Not registering GameData/ThrottleControlledAvionics/Plugins/ThrottleControlledAvionics.dll, it belongs to ThrottleControlledAvionics
3044 [1] INFO CKAN.Registry (null) - Not registering GameData/ToadicusTools/ToadicusTools.dll, it belongs to ToadicusTools
3044 [1] INFO CKAN.Registry (null) - Not registering GameData/Trajectories/Plugin/Trajectories.dll, it belongs to Trajectories
3044 [1] INFO CKAN.Registry (null) - Not registering GameData/TreeToppler/TreeToppler.dll, it belongs to TreeToppler
3045 [1] INFO CKAN.Registry (null) - Not registering GameData/TriggerTech/KSPAlternateResourcePanel/KSPAlternateResourcePanel.dll, it belongs to AlternateResourcePanel
3047 [1] INFO CKAN.Registry (null) - Not registering GameData/TriggerTech/KerbalAlarmClock/KerbalAlarmClock.dll, it belongs to KerbalAlarmClock
3049 [1] INFO CKAN.Registry (null) - Not registering GameData/TriggerTech/TransferWindowPlanner/TransferWindowPlanner.dll, it belongs to TransferWindowPlanner
3051 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakScale/plugins/KSPAPIExtensions.dll, it belongs to TweakScale
3051 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakScale/plugins/Scale.dll, it belongs to TweakScale
3051 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakScale/plugins/Scale_Editor.dll, it belongs to TweakScale
3051 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakScale/plugins/Scale_Redist.dll, it belongs to TweakScale
3051 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakableEverything/TweakableControlSurfaces.dll, it belongs to TweakableEverything
3051 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakableEverything/TweakableDockingNode.dll, it belongs to TweakableEverything
3052 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakableEverything/TweakableEVA.dll, it belongs to TweakableEverything
3052 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakableEverything/TweakableFuelPumps.dll, it belongs to TweakableEverything
3052 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakableEverything/TweakableGimbals.dll, it belongs to TweakableEverything
3052 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakableEverything/TweakableIntakes.dll, it belongs to TweakableEverything
3052 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakableEverything/TweakableParachutes.dll, it belongs to TweakableEverything
3052 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakableEverything/TweakableReactionWheels.dll, it belongs to TweakableEverything
3052 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakableEverything/TweakableSAS.dll, it belongs to TweakableEverything
3052 [1] INFO CKAN.Registry (null) - Not registering GameData/TweakableEverything/TweakableSolarPanels.dll, it belongs to TweakableEverything
3056 [1] INFO CKAN.Registry (null) - Not registering GameData/UmbraSpaceIndustries/Karbonite/Karbonite.dll, it belongs to Karbonite
3058 [1] INFO CKAN.Registry (null) - Not registering GameData/UmbraSpaceIndustries/KarbonitePlus/KarbPlus.dll, it belongs to KarbonitePlus
3059 [1] INFO CKAN.Registry (null) - Not registering GameData/UmbraSpaceIndustries/Kolonization/KolonyTools.dll, it belongs to USI-UKS-Shared
3061 [1] INFO CKAN.Registry (null) - Not registering GameData/UmbraSpaceIndustries/LifeSupport/USILifeSupport.dll, it belongs to USI-LS
3063 [1] INFO CKAN.Registry (null) - Not registering GameData/UmbraSpaceIndustries/SrvPack/AirbagTools.dll, it belongs to USI-SRV
3063 [1] INFO CKAN.Registry (null) - Not registering GameData/UmbraSpaceIndustries/SrvPack/Lifeboat.dll, it belongs to USI-SRV
3065 [1] INFO CKAN.Registry (null) - Not registering GameData/UmbraSpaceIndustries/WarpDrive/WarpEngine.dll, it belongs to AlcubierreStandalone
3065 [1] INFO CKAN.Registry (null) - Not registering GameData/UnmannedBeforeManned/MiniAVC.dll, it belongs to UnmannedBeforeManned
3080 [1] INFO CKAN.Registry (null) - Not registering GameData/VesselMover/VesselMover.dll, it belongs to VesselMover
3081 [1] INFO CKAN.Registry (null) - Not registering GameData/WasdEditorCamera/MiniAVC.dll, it belongs to WasdEditorCameraContinued
3081 [1] INFO CKAN.Registry (null) - Not registering GameData/WasdEditorCamera/Plugins/WasdEditorCamera.dll, it belongs to WasdEditorCameraContinued
3081 [1] INFO CKAN.Registry (null) - Not registering GameData/WaypointManager/WaypointManager.dll, it belongs to WaypointManager
3082 [1] INFO CKAN.Registry (null) - Not registering GameData/WheelSounds/Plugins/WheelSounds.dll, it belongs to RoverWheelSounds
3085 [1] INFO CKAN.Registry (null) - Not registering GameData/WildBlueIndustries/000WildBlueTools/Plugins/MiniAVC.dll, it belongs to WildBlueTools
3085 [1] INFO CKAN.Registry (null) - Not registering GameData/WildBlueIndustries/000WildBlueTools/Plugins/WildBlueTools.dll, it belongs to WildBlueTools
3089 [1] INFO CKAN.Registry (null) - Registering Buffalo from GameData/WildBlueIndustries/Buffalo/Plugins/Buffalo.dll
3094 [1] INFO CKAN.Registry (null) - Not registering GameData/WildBlueIndustries/Pathfinder/Plugins/Pathfinder.dll, it belongs to Pathfinder
3095 [1] INFO CKAN.Registry (null) - Not registering GameData/Workshop/Plugins/Workshop.dll, it belongs to Workshop
3096 [1] INFO CKAN.Registry (null) - Not registering GameData/[x] Science!/MiniAVC.dll, it belongs to xScience
3096 [1] INFO CKAN.Registry (null) - Not registering GameData/[x] Science!/[x] Science!.dll, it belongs to xScience
3505 [1] INFO CKAN.RelationshipResolver (null) - Resolving relationships for CustomClusters
3505 [1] INFO CKAN.RelationshipResolver (null) - Resolving dependencies for CustomClusters
3509 [1] INFO CKAN.RelationshipResolver (null) - Resolving relationships for CustomClusters
3509 [1] INFO CKAN.RelationshipResolver (null) - Resolving dependencies for CustomClusters
About to install...

 * Custom Clusters 0.53.1

Continue? [Y/n] y

Downloading "https://ckan1.spacedock.info/storage/Randazzo_9223/Custom_Clusters_-_More_freedom_in_engine_design/Custom_Clusters_-_More_freedom_in_engine_design-0.53.1.zip" (libcurl)
4980 [1] INFO CKAN.Curl (null) - Using curl-ca bundle: (none)
5568 [8] INFO CKAN.NetAsyncDownloader (null) - Error downloading https://ckan1.spacedock.info/storage/Randazzo_9223/Custom_Clusters_-_More_freedom_in_engine_design/Custom_Clusters_-_More_freedom_in_engine_design-0.53.1.zip: CKAN.Kraken: SslPeerCertificate
5569 [8] INFO CKAN.NetAsyncDownloader (null) - All files finished downloading
Failed to download "https://ckan1.spacedock.info/storage/Randazzo_9223/Custom_Clusters_-_More_freedom_in_engine_design/Custom_Clusters_-_More_freedom_in_engine_design-0.53.1.zip" - error: SslPeerCertificate
One or more files failed to download, stopped.

And just as a test, I tried with using curl from the command line:

$ curl -sv https://ckan1.spacedock.info/storage/Randazzo_9223/Custom_Clusters_-_More_freedom_in_engine_design/Custom_Clusters_-_More_freedom_in_engine_design-0.53.1.zip -o Custom_Clusters_-_More_freedom_in_engine_design-0.53.1.zip
*   Trying 46.101.184.174...
* Connected to ckan1.spacedock.info (46.101.184.174) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [61 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3349 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [589 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
* 	 subject: C=DE; CN=i.52k.de; [email protected]
* 	 start date: Mar 24 02:00:07 2015 GMT
* 	 expire date: Mar 23 18:41:38 2016 GMT
* 	 subjectAltName does not match ckan1.spacedock.info
* SSL: no alternative certificate subject name matches target host name 'ckan1.spacedock.info'
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, Client hello (1):
} [2 bytes data]

If I'm reading it right, curl/libcurl is saying that SpaceDock doesn't have a valid SSL cert entry for ckan1.spacedock.info. I had just switched from using OpenSSL to LibreSSL, so it might be a bit more strict on this.

Just thought I'd bring this up and hopefully there is some sort of fix to be had...