srakasingles.blogg.se -

Best ksp mods 1.0.2 install#
Best ksp mods 1.0.2 mod#
Best ksp mods 1.0.2 archive#
Best ksp mods 1.0.2 Patch#

Identifier should be same as the ModuleManager name.

Best ksp mods 1.0.2 mod#

If the mod would generate a FOR pass in ModuleManager, then the Example: MyMod must always be expressed as MyMod, but another module Identifiers must be both: case sensitive for machines, and unique regardless of capitalization for human consumption and case-ignorant systems. The mod is referenced (by depends, conflicts, or elsewhere). This is the identifier that will be used whenever It may only consist of ASCII-letters, ASCII-digits and - (dash). Will be referred to by other CKAN documents. This is the globally unique identifier for the mod, and is how the mod For maximumĬompatibility, using older spec versions is preferred when newer features are Changes since spec 1Īre marked with v1.2 through to v1.26 respectively. This document describes the CKAN specification 'v1.26'. Reference CKAN client that will read this file.įor compatibility with pre-release clients, and the v1.0 client, the special ckan file.Ī vx.x string (eg: "v1.2"), being the minimum version of the The version number of the CKAN specification used to create this. The metadata file provides machine-readable information about aĭistribution. "abstract" : "Realistic jet engines for KSP ", KSP-RealSolarSystem-Bundler Example CKAN file The CKAN metadata spec is inspired by the CKANįiles are simply JSON files using UTF-8 as character-encoding.Įxcept where stated otherwise all strings should be printable unicode only.ĬKAN files should have a naming scheme of their mod's identifier,įollowed by a dash, followed by the version number, followed by The CKAN fileĪ CKAN file is designed to contain all the relevant meta-infoĪbout a mod, including its name, license, download location,ĭependencies, compatible versions of KSP, and the like. Presently the authoritative CKAN metadata repository isĪ JSON Schema is provided for validation purposes.Īny CKAN file must conform to this schema to be considered valid.

It is an error for a distribution (zipfile) to contain more than one.

CKAN files may be placed anywhere inside a distribution.

The meta-data file may be included in the distribution, to facilitateĮasier indexing.

This facilities easy building of indexes, and means meta-dataĬan be created independently of the distribution itself, easing

The meta-data file must be detachable from the distribution.

Each distribution (a mod and its associated files) must have anĪssociated meta-data file that describes its contents.

The fundamental design of the CKAN is as follows: Problems will be eliminated (reducing the workload on authors), andĪ more straightforward path of installing mods is provided (making

Best ksp mods 1.0.2 install#

To release and install modules, it is hoped that many of the misinstall The goal of the CKAN is to provide a network that is easy to useįor both mod authors and end users. With over 11,000 contributors and 30,000 distributions. (the CTAN), the most successful has been for Perl (the CPAN),

Best ksp mods 1.0.2 archive#

There have been many comprehensive archive networks for various " optional" in this document are to be interpreted as described in " shall not", " should", " should not", " recommended", " may" and The key words " must", " must not", " required", " shall", This document, and all associated files, are licensed under the MIT/Expat

Best ksp mods 1.0.2 Patch#

Send pull requests to patch this document and associated files. Please open discussions in the issues list, and This is a Request For Comments on the Comprehensive Kerbal Archive The Comprehensive Kerbal Archive Network (CKAN)