Metadata Webtool

1. SpaceDock ID
   

1. User name
   
2. Repository name
   
3. Filter Regular Expression
   Case-sensitive C# semantics
   By default NetKAN will look for a zip file in the release. If there are multiple zip files it'll produce an error as it doesn't know which one to use. You can use this field to provide a regular expression to filter which file to use

1. URI
   

Must start with any of: #/ckan/spacedock/ , #/ckan/github/ , #/ckan/http/

1. $kref
   

Paste metadata from an existing netkan:

1. NetKAN File Contents
   

Fill in all fields on your own—good luck!

1. Identifier - Machine-friendly name for the mod (only numbers, letters, and dashes, no spaces)
   
2. Name - User-friendly name for the mod
   
3. Installs .version file
4. Mod Version
   
5. Abstract - A short description of what the mod does
   
6. Download URI
   
7. Mod Authors (one per line)
   
8. License(s)
   Add Users can choose to which of these to adhere
   About valid licenses

   Search by name
   

   License ID
   
9. Game version
   examples: ==1.0 or <=1.1>=1.0.3 - set to any (or leave empty) to state compatibility with all versions
   While not technically mandatory, not providing this field is considered bad practice.

1. Homepage
   URI to the preferred landing page for the mod
2. Repository
   URI to the repository where the mod's source can be found
3. CI
   Continuous Integration (e.g. Jenkins) Server where the module is being built
4. SpaceDock
   URI to the mod's SpaceDock page
5. Manual
   URI to the mod's user manual if it exists
6. License
   URI to the mod's license
7. Bugtracker
   URI to the mod's bugtracker if it exists (Preferred page to post problems/questions)
8. Screenshot
   A direct URL to a screenshot of the mod

1. Mod type (choose at least one)
2. Mod descriptors (choose zero or more)

If this mod requires other mods to be installed alongside it, use Relationships. Do not use install instructions to install multiple mods.

Selecting the .zip file on your computer will enable automatic path completion.
No data will be uploaded anywhere.

1. Install file/folder
   into GameData Ships Ships/SPH Ships/VAB Ships/@thumbs/VAB Ships/@thumbs/SPH Ships/Script Tutorial Scenarios Missions GameRoot as
   Remove

You can add version restrictions. For example SomeModID can be restricted like SomeModID ==1.0 or SomeModID <=1.1 >=1.0.3

1. Depends on (mod will not run without it)
   Add
   Search by name
   

   Requirement ID
   
2. Recommends (mod is greatly complimented by these mods)
   Add
   Search by name
   

   Recommendation ID
   
3. Suggests (mod is complimented by these mods)
   Add
   Search by name
   

   Suggestion ID
   
4. Supports (mod has specific code to relating to these mods ex. Toolbar integration)
   Add
   Search by name
   

   Supported ID
   
5. Conflicts with (mod will break or be broken by these mods)
   Add
   Search by name
   

   Conflicted ID
   

1. Release Status stable testing development
2. Provides (can be installed instead of these mods without problems)
   Add
   Search by name
   

   Provided ID
   

1. $kref
   
2. Update JSON
   {}