Licence key
Last modified: 25 July 2026
Where the key goes
license:
key: 'YOUR-LICENCE-KEY'Keys are 24 characters; dashes are cosmetic. The panel checks the format as you type, but only the plugin can tell you whether a key is genuinely valid.
How it is validated
On every startup the plugin validates the key against the Sniffer Studio licensing API and caches the signed result. Validation is signature-checked against a key baked into the jar, so a cached decision cannot be forged offline.
Offline grace
If the licensing API cannot be reached, the plugin falls back to the cached decision for up to seven days from the moment that decision was issued. Inside that window your server starts normally through an outage. Outside it — or with no cached grant at all — startup is denied with an offline licence error.
Current licensing API state is on the status page.
No key, or an invalid one
Self-host and embedded modes require a valid licence key. Without one, the plugin refuses to start; it does not silently run unmoderated, and it does not interfere with Simple Voice Chat.
Cloud mode is different: the processor token is the entitlement, so the cloud configuration does not need a licence key.
What the licence controls
For cloud subscriptions the licence decides which language packs you may use, your per-minute request allowance and the expiry date. Those are enforced by the processor on every request rather than by the plugin, so editing your own config cannot widen your access — see tokens and entitlements.