Plugin Manifest¶
This document defines the file found at the root of your plugin folder. For example, see Fundamental’s plugin.json file.
JSON paths are denoted in “flat format”, as used by jq.
¶
String. Required.
The unique identifier for your plugin. Case-sensitive. Slugs may only contain letters and , numbers , hyphens , and underscores .
After your plugin is released, the slug must never change, otherwise patch compatibility would be broken. To guarantee uniqueness, it is a good idea to prefix the slug by your “brand name” if available, e.g. “MyCompany-MyPlugin”.
The word “slug” comes from web publishing to represent URL paths that never change, which in turn comes from typesetting.
¶
String. Required.
The human-readable name for your plugin. Used for labeling your plugin the VCV Library.
Unlike slugs, the name can be changed at any time without breaking patch compatibility.
¶
String. Required.
The version of your plugin should follow the form . Do not include the “v” prefix—this is added automatically where appropriate.
The version should match the version of Rack your plugin is built for, e.g. 1. You are free to choose the part of your plugin version. For example, MyPlugin 1.4.2 would specify that your plugin is compatible with Rack 1.X.
If you publish the source code in a git repository, it is recommended to add a git tag with and .
¶
String. Required.
The license of your plugin. Use for commercial and freeware plugins.
If your plugin uses a common open-source license, use the identifier string from the SPDX License List, such as , , , , , etc.
¶
String. Optional.
Prefix string for all modules in your plugin. For example, the brand “VCV” is used by the Fundamental plugin to create “VCV VCF”, VCV Unity”, etc. If blank or undefined, the plugin name is used.
¶
String. Optional.
Homepage for the source code. For GitHub URLs, use the main project page, not the URL.
¶
String. Optional.
Link to donation page for users who wish to donate. E.g. PayPal.Me, Cash App links.
¶
Array of strings. Optional.
List of tags representing the functions and/or properties of the module. All tags must match the list of allowed tags in Rack, case-insensitive.
¶
String. Optional.
A one-line summary of the module’s purpose. Displayed in the Module Browser tooltip.