HeadDB supports modern Paper and Folia servers.
The Paper/Folia plugin requires Java 25 or newer. The API and core modules target Java 21.
No. Vault is optional and is required only when economy support is enabled.
A new installation needs network access to download the public database. After a successful download, HeadDB can load the last verified local cache while the remote service is unavailable.
The active verified database remains available when one was already loaded. HeadDB records the failure without replacing the working snapshot.
Useful commands:
/hdb status
/hdb verify
/hdb refresh
/hdb report
HeadDB may load verified artifacts from disk and then confirm through the remote manifest that they are unchanged. No full download is needed, so the active snapshot remains cache-sourced.
Scheduled checks are enabled by default every six hours. Configure the interval under refresh.scheduled in config.yml.
Yes. Authorized administrators can apply local visibility and metadata overrides. These changes affect only that server.
Custom Heads are server-local heads created and managed by staff. They may be saved as drafts and published later.
Custom Categories are server-local categories that appear alongside public categories and organize remote or local content.
Those identifiers are retained for backward compatibility. The current public feature names are Custom Heads and Custom Categories.
No. Favorites are stored per player on the server.
A running JVM cannot load the replacement plugin classes safely. HeadDB downloads or stages the JAR, then the server must restart to load it.
Production servers commonly keep it disabled and use notifications plus a controlled restart. Database updates are separate and can refresh automatically without replacing the plugin JAR.
Back up:
config.yml
gui.yml
sounds.yml
economy.yml
messages/
storage/headdb.db
Yes. Integrate through headdb-api and Bukkit's service provider system rather than depending on internal Paper classes or reading cache/storage files directly.