ConsentGate
Changelog
0.3.02026-10-09
Translatable error messages and automatic config updates.
Added
- Kick messages for errors, such as a busy gate, a timeout, or a storage failure, can be changed and translated with the new
error-*keys in the message files. - Missing settings are added to
config.yml, and missing keys to the bundled message files, when the plugin starts. Your values and comments are kept, and the server log lists what was added. If a file cannot be updated safely, it is left unchanged, the log shows a warning, and startup continues. Make a file read-only to keep it as it is.
Changed
- Paper and Velocity now use the same wording for the same error. A few messages changed slightly, for example a Paper timeout now shows "Consent request timed out."
Upgrading from 0.2.0
Back up the plugin folder, stop the server or proxy, replace the JAR, and start again. The new message keys are added to en-US.properties and id-ID.properties automatically.
0.2.02026-09-25
Easier first setup.
Added
- Empty MySQL/MariaDB databases get their tables automatically. No SQL import is needed. First setup needs
CREATE,REFERENCES,SELECT,INSERT, andUPDATEon the dedicated database. - A disabled gate can be enabled with
consentgate reloadafter settingenabled: true.consentgate validatealso works while disabled, without opening storage.
Changed
- The generated config and starter documents explain setup, scopes, version changes, and setting limits.
- Existing tables are checked and never overwritten to repair or upgrade a schema.
Upgrading from 0.1.0
Back up the plugin folder, stop the server or proxy, replace the JAR, and start again. Existing config, messages, documents, and consent records are kept, and document versions do not need to change. Copy new settings or comments from the default config if you want them.
0.1.02026-09-23
First release for Paper and Velocity.
Added
- Required documents and explicit acceptance before backend connection (Velocity) or world entry (Paper).
- Java dialogs with pages, formatting, translations, and an optional language selector.
- Optional native Bedrock forms through Geyser on the same proxy or server.
- Document versions: players accept again when a document changes.
- SQLite, MySQL, and MariaDB storage, with a local cache for short database outages.
- Acceptance history kept on reset.
- Admin commands: status, reset, preview, document viewing, validate, and reload.