Licensing

DaisyFilter is a paid plugin and checks its licence every time the server starts.

If you bought it on BuiltByBit

There is nothing to configure. Your licence key is applied to your download automatically — install the jar, start the server, and you should see:

[DaisyFilter] License validated. Thank you for supporting DaisyFilter.

If you were issued a key directly

Put it in plugins/DaisyFilter/license.yml:

key: "YOUR-LICENSE-KEY"

That file is generated on the first start — including a start that was refused — so it is always there to paste into.

What it needs

Outbound HTTPS to license.daisy.cat on port 443, at every startup.

There is no offline or cached mode. This is deliberate, and it has one consequence worth knowing before you buy: an air-gapped server cannot run DaisyFilter. If your host firewalls outbound traffic, allow that destination.

Validation sends your licence key, a hardware id, MAC address, operating system and the connecting IP. It sends no player data of any kind — no names, no UUIDs, no messages, no moderation records. See Privacy for everything that leaves your server.

If DaisyFilter refuses to start

Your server keeps running

Only DaisyFilter is disabled. The server starts normally, which means chat, commands, signs, books and anvils are unfiltered until this is resolved. The console says so in those words — check for it after any restart that followed a network or host change.

Look for a single SEVERE line at startup carrying a code:

Code	What happened	What to do
LK-01	Your download was built while the licence service was failing, so no key was applied to it.	Download the resource again. The old download stays broken — re-downloading is the only fix.
LK-02	The jar never went through a purchase, so no key was applied.	Download from your purchase. If you were issued a key directly, put it in license.yml.
LK-03	No key anywhere — nothing injected and license.yml is empty.	Paste your key into license.yml.
LK-04	Should not happen.	Contact support and quote the log line; seeing this at all is useful information.

Anything else is a rejection or a connection failure, and prints the reason followed by after 2 attempts. A validation attempt gives up after about 12 seconds, so a firewalled host fails in well under a minute rather than hanging.

Common causes of a rejection:

• You moved the server to new hardware. Licences are bound to the machine. Contact support for a reset — this is routine, not an accusation.
• Outbound 443 is blocked. See Troubleshooting, where the symptoms overlap with the separate first-boot library download.
• The key was mistyped. Keys are pasted, not retyped.

Support

Quote your licence fingerprint, never your key. It is a short non-secret identifier that is safe to paste into a ticket or a screenshot:

/daisyfilter status

The License: line is your fingerprint. BuiltByBit installs also keep a copy in plugins/DaisyFilter/secrets/license.properties; a manually issued key has no such file, so /daisyfilter status is the reliable place to look.

Treat license.yml and anything in secrets/ as credentials — do not post them publicly or commit them anywhere.