Docs

Minecraft plugin licenses

Buy a key in the store, put it in your plugin config, and the ShortN license SDK keeps the server validated and up to date.

Buy and install

Open the store and filter by Plugins (or pick a plugin product).
Complete checkout — the key is emailed and shown under My keys.
Download the JAR from Downloads (or the product page) when a file is attached to that product.
Put the JAR in your Paper plugins folder and set license.key in config.yml, then restart.

Open store · My keys

Config

Typical config block (exact keys may match your plugin README):

license:
  key: "YOUR-LICENSE-KEY"
  server-url: "https://store2.shortn.info"
  # hwid-override: ""   # optional; leave empty for auto fingerprint

Server HWID

Licenses bind to a server fingerprint (not a player). Reusing a key on another machine needs a free activation slot or an admin rebind. Changing hardware may require releasing a device under My keys.

Updates

Plugins check the update channel against Downloads bound to the product. You will see a console notice when a newer JAR is available — replace the file manually (no hot-swap).

For developers

Integrate the shortn-license Java SDK (shaded into the plugin). Core HTTP APIs:

POST /api/v1/license/validate
GET /api/v1/plugin/update
POST /api/v1/plugin/heartbeat