Ksp mod download ksp avc

CKAN files should have a naming scheme of their mod's identifier, followed by a dash, followed by the version number, followed by the extension. For example: RealSolarSystem For compatibility with pre-release clients, and the v1. This document describes the CKAN specification 'v1. Changes since spec 1 are marked with v1.

For maximum compatibility, using older spec versions is preferred when newer features are not required. This is the globally unique identifier for the mod, and is how the mod will be referred to by other CKAN documents. This is the identifier that will be used whenever the mod is referenced by depends , conflicts , or elsewhere.

Identifiers must be both: case sensitive for machines, and unique regardless of capitalization for human consumption and case-ignorant systems. Example: MyMod must always be expressed as MyMod, but another module cannot assume the mymod identifier. For most mods, this means the identifier should be the name of the directory in GameData in which the mod would be installed, or the name of the. This is the human readable name of the mod, and may contain any printable characters.

The author, or list of authors, for this mod. No restrictions are placed upon this field. A fully formed URL, indicating where a machine may download the described version of the mod. Note: This field is not required if the kind is metapackage or dlc. The license v1. The same rules as per the Debian license specification apply, with the following modifications:.

The following license strings are also valid and indicate other licensing not described above:. A single license v1. If different assets in the mod have different licenses, the most restrictive license should be specified, which may be restricted. It may be omitted, in which case zero is assumed. It is provided to allow mistakes in the version numbers of older versions of a package, and also a package's previous version numbering schemes, to be left behind. It is usually the version number of the original mod from which the CKAN file is created.

Usually this will be in the same format as that specified by the mod author s ; however, it may need to be reformatted to fit into the package management system's format and comparison scheme. First the initial part of each string consisting entirely of non-digit characters is determined. These two parts one of which may be empty are compared lexically. If a difference is found it is returned. The lexical comparison is a comparison of ASCII values modified so that all the letters sort earlier than all the non-letters.

Then the initial part of the remainder of each string which consists entirely of digit characters is determined. The numerical values of these two parts are compared, and any difference found is returned as the result of the comparison. For these purposes an empty string which can only occur at the end of one or both version strings being compared counts as zero. These two steps comparing and removing initial non-digit strings and initial digit strings are repeated until a difference is found or both strings are exhausted.

Note that the purpose of epochs is to allow us to leave behind mistakes in version numbering, and to cope with situations where the version numbering scheme changes. It is not intended to cope with version numbers containing strings of letters which the package management system cannot interpret such as ALPHA or pre- , or with silly orderings. A list of install directives for this mod, each must contain exactly one of three source directives:. If no install sections are provided, a CKAN client must find the top-most directory in the archive that matches the module identifier, and install that with a target of GameData.

In other words, the default install section is:. A comment field, if included, is ignored. MIT License. Use this GitHub Action with your project Add this Action to an existing workflow or create a new one. Branches Tags. Could not load branches. Could not load tags. Latest commit. Git stats 73 commits. Failed to load latest commit information.

Total Views 1,, Older Stats. Total Items 21, Older Stats. Internet Archive's 25th Anniversary Logo. Search icon An illustration of a magnifying glass. User icon An illustration of a person's head and chest. Sign up Log in. Web icon An illustration of a computer application window Wayback Machine Texts icon An illustration of an open book.

Books Video icon An illustration of two cells of a film strip. Video Audio icon An illustration of an audio speaker. Audio Software icon An illustration of a 3. Software Images icon An illustration of two photographs. Images Donate icon An illustration of a heart shape Donate Ellipses icon An illustration of text ellipses. Media Type Media Type. Available on CKAN. License: GPLv3. Have a question or require some help? Leave a message in this thread or PM me.

Just bundle the. Because of the bundled nature, the player will be given the option to allow update checking on the first run. If the player does disable update checking, it will continue to run in local mode assessing game version compatibility. MiniAVC-V2 will always run from the most up-to-date version which has been bundled with any of the installed add-ons. For more information read the online readme file. This software contacts the internet to check if add-ons have newer versions available.

Data is only read from the internet and no personal information is sent. All remote destinations set in version files are up to the respective add-on developers and I hold no responsibility for how these features are used. Awesome, and thanks for updating this as well as your time in dealing with my issue over the weekend.

Say there's a situation where the local config has a KSP version of 1. The mod author doesn't want to push a new release but also doesn't want the nagging "wrong version" pop ups to occur, so they update the remote config to use a range of KSP 1.

Does this mean that the mod author cannot do this and instead MUST release a new version just for updating the. You know, this is why I released a beta , and contacted a lot of the major mod authors via PM, including yourself. It was something I had done during testing, and forgot to remove, but I put it in the notes as I do all changes.

Everything has 2 sides In some cases this has simply not worked and with the information now I assume, that I continued to get a nag screen because AVC used the remote file, which the author didn't updated and my local change wasn't taken into account So an active author can push our a release but an inactive author can not update the remote.

So in the end I think both solution have up- and downsides Sorry, I just decided to read through what bugs you had fixed after you posted the release, saw that comment and then thought of that situation. I honestly haven't used KSP-AVC in years other than the mini-avc bugging me every time I start up my current game so I wasn't even sure what it would do before and just wanted to know if that situation was correct.

Thank you for looking at it, it was just a bit frustrating that none of the people this was aimed at took the time to look at it. Anyway, I'm thinking about adding a setting to make this optional.