Back to blog

Minecraft Plugin Licensing Explained: How License Keys Work in 2026

Updated Dan, co-founder

Plugin licensing is how a paid Minecraft plugin checks that the server running it belongs to someone who bought it. The buyer gets a license key, the plugin asks a license server whether that key is allowed to run, and the plugin only loads if the answer is yes.

This guide explains how that works in practice: what happens during a check, how keys reach buyers on each marketplace, what you can sell with licenses beyond "bought it once", and what to look for in a licensing system. If you mainly want to stop piracy, read how to protect your Minecraft plugin alongside this.

The three parts of a licensing system

Every licensing system, homemade or hosted, has the same three parts:

  1. License keys. One per purchase, each tied to a plugin and carrying its own rules: when it expires, and how many servers can use it at once.
  2. A license server. It stores the keys and answers one question when a plugin starts: is this key allowed to run here?
  3. A check in your plugin. Usually a few lines in onEnable() that read the buyer's key, ask the license server and disable the plugin if the answer is no.

Around those you need a way to create keys (by hand, or automatically when someone buys) and a way to manage them afterwards: extend one, raise its limit, revoke it if it leaks.

What happens during a license check

Here's a check from start to finish, using MC License as the example. The steps are much the same in any well-built system.

  1. The server starts and your plugin enables. It reads the buyer's key from a file in the plugin folder. With MC License that file is mclicense.txt, which the library creates for the buyer to paste their key into. On BuiltByBit, the key is already written into the jar at download, so there's nothing to paste.
  2. The plugin generates a nonce, a random value used for this one request.
  3. It sends the key, your plugin's ID and the nonce to the license server.
  4. The license server checks the key. Does it exist for this plugin? Has it expired? Is the server's IP blacklisted? Would this server take the key over its limit?
  5. The server answers with a status, such as valid, expired, max_ips (too many servers), blacklisted or not_found, and signs the whole response, nonce included, with its private RSA key.
  6. The plugin verifies the answer. It checks the signature against the public key it carries and makes sure the nonce matches the one it sent. A response that fails either check is rejected, however it got there.
  7. The plugin enables or disables itself based on the status, and logs the result to the console so the server owner knows what happened.

In code, all of that is one call:

if (!MCLicense.validateKey(this, "yourPluginId")) {
    Bukkit.getPluginManager().disablePlugin(this);
    return;
}

Steps 5 and 6 are the ones that matter most. Without a signature, anyone can run a fake license server that says "valid" to every key. Without a nonce, anyone can record one real "valid" response and replay it forever. (The MC License security page covers both.) Adding a license check to a Paper or Spigot plugin goes through the setup step by step, including Gradle, Maven and shading.

How buyers get their keys

A license check is only as good as your key delivery. If buyers wait hours for a key, they leave bad reviews. If you have to create every key by hand, you'll eventually stop bothering. Each marketplace works differently:

Where you sell How the key gets to the buyer What the buyer does
BuiltByBit An external license key placeholder asks your license server for a key at download time and writes it into the jar Nothing
Voxel Shop (Polymart) The buyer's details are written into the download, and the purchase is verified with Voxel Shop the first time the plugin starts Nothing
Tebex A webhook creates the key when payment completes, and it's emailed to the buyer Pastes the key into a file
Direct sales, commissions You create the key from the dashboard or the API Pastes the key into a file
SpigotMC Not allowed: premium resource guidelines prohibit licensing systems n/a

The SpigotMC rule catches people out. If you sell there as well, ship a license-free build for SpigotMC. Where to sell your plugin compares the marketplaces in full.

With MC License, BuiltByBit, Voxel Shop and Tebex sales all create a managed license automatically. How automatic license delivery works covers what's automated and what isn't.

What you can sell with license keys

A license key carries rules, and those rules let you sell more than a one-off purchase. Two settings do most of the work: expiry and server limit.

  • One-off purchase. No expiry, a server limit of one or two. This is what most marketplace plugins are.
  • Rental or subscription. A key that expires after 30 days or a year. Extend it when the buyer renews. If they don't, the plugin stops at the end of the period.
  • Free trial. A key that expires after a few days, so server owners can try the full plugin before buying. If they then buy from you directly, extend the same key instead of issuing a new one.
  • Server or network tiers. Charge more for a higher server limit: one price for a single server, another for a network running the plugin on ten.
  • Commission handover. Deliver a custom plugin on a key that expires shortly after the payment due date, and remove the expiry once you're paid. Tell the client upfront, so it reads as normal terms rather than a trap.

In MC License these are just settings on a license: an expiry date (or none) and a maximum number of servers. Set a default per plugin and change individual licenses from the dashboard or the API.

What licensing doesn't do

Licensing is worth having, but it's easy to expect too much of it.

  • It doesn't stop someone cracking the check out. Anyone willing to decompile your jar can find the check and delete it. Licensing makes sharing a copy fail. Obfuscation makes cracking it slower. Neither makes it impossible.
  • It isn't your terms of sale. A license key controls whether the plugin runs. What a buyer is allowed to do with your plugin (resell it, edit it, use it on a network) belongs in the terms on your listing.
  • It adds a network dependency. The server needs to reach your license server when the plugin starts, so do the check off the main thread with a timeout, and decide what happens when the check can't complete, as opposed to when it comes back invalid.

Your options

There are three realistic ways to license a plugin:

  • Build your own. A key table and an endpoint is a weekend. Signed responses, nonces, server limits, marketplace integrations and keeping it online indefinitely is a lot more. Should you build your own? is an honest breakdown, including when building does make sense.
  • Self-host an existing system. You get a working system, but your VPS and its uptime become part of every customer's server startup.
  • Use a hosted platform. Someone else runs the license server, and you add a library and a check. We compare the main options, including Lukittu, LicenseGate, SunLicense, ObsidianLicense and Keygen, in the best Minecraft plugin licensing systems.

How to choose a licensing system

Whatever you pick, check these:

  • Signed responses and a nonce on every check. If a system can't say how it stops a fake license server or a replayed response, it doesn't.
  • Delivery for the marketplaces you sell on. Manual key handling doesn't scale past your first few sales. Check how each of your marketplaces is supported, not just whether it's listed.
  • Per-license control. Server limits, expiry dates and revoking, set per plugin and changeable per buyer.
  • Something for your buyers. A way for buyers to check their own key, like a public license checker, saves support tickets.
  • An API. So you can script bulk changes, connect your own store, or move your licenses elsewhere later.
  • A price that fits your sales. If you sell three copies a month, an expensive plan eats the margin. If you sell three hundred, it's a rounding error.

Getting started with MC License

MC License is built by the team behind LearnSpigot, which has helped more than 15,000 developers learn to make plugins. It covers everything in this guide: signed and nonce-checked validation, server limits, expiry, IP blacklisting, automatic delivery on BuiltByBit, Voxel Shop and Tebex, a public license checker, a Discord bot, collaborators and a REST API.

  1. Create a free account and add your plugin, or import it from SpigotMC, BuiltByBit or Voxel Shop.
  2. Add the library and the check to your plugin (docs).
  3. Connect your marketplace, or create keys yourself from the dashboard or API.

Pricing: Basic is $4.99 a month (or $49.99 a year) for 3 plugins with 50 licenses each. Professional is $7.99 a month (or $79.99 a year) with unlimited plugins and licenses. Lifetime is a one-off $99 with everything in Professional. Basic and Professional start with a free trial, and no card is needed.

Questions? Ask us on Discord.

Ready to protect your plugins?

Create a free account and get started in minutes.

Get started free