Changelog

Changelog

2.1.0

Added

• Storage statistics: /up stats now shows the space used by every log type (blocks, containers, items, entities, chat, players, interactions) with the number of rows. See Purge.
• /up clear <category> [t:<time>]: delete a whole log type or only its old entries to save space, with a confirmation step (/up clear confirm). The database is compacted afterwards. The staff audit log is protected. See Purge.
• log.creative: items taken from the creative inventory can be switched on or off separately, also per world. See Configuration.
• Discord notifications: alerts and staff actions can be posted to Discord, with separate webhooks (discord.alerts-webhook, discord.audit-webhook), an alert level filter (discord.min-level) and a list of staff commands to report (discord.audit-events). Startup errors such as an unreachable database are reported too. See Investigation and Alerts and Configuration.
• Usage statistics (bStats): anonymous usage statistics for the Paper edition. They can be turned off, see FAQ.

Changed

• Creative inventory logging now records the amount that was really added. Before, nothing was logged when the player already had one item of that kind, so taking more of it went unnoticed. The create entries carry creative in their meta field.
• clear was added to the possible values of discord.audit-events. The default list of new config.yml files includes it. Existing files need it added by hand.
• Alerts posted to Discord start at level MEDIUM by default (discord.min-level: 2). Set it to 1 to receive LOW alerts as before.
• detection.discord-webhook still works and is used when discord.alerts-webhook is empty.

2.0.0

Added

• Multi-platform architecture: Native support for Paper and Fabric from a unified codebase.
• Database backends and live migration: DuckDB (default), SQLite, MySQL and ClickHouse, including live migration via /up migrate-db.
• Expanded rollback and restore: containers, player inventories, entity kills (killed mobs are revived) and entity spawns.
• Command rollback (#command): /fill, /setblock and /clone are logged and can be rolled back, restored and looked up. Toggle with log.command-blocks. See Rollback and Restore.
• Incident investigation: /up investigate lists suspects with a risk level, causes, affected containers and entities. See Investigation and Alerts.
• Player and entity timeline: /up timeline <player|#entity>, for example /up timeline #enderman.
• Cause tracking: likely cause of block and entity changes, including who ignited TNT.
• Anomaly detection and alerts: X-ray, spawner and optional rules, configurable under detection.*, with an optional Discord webhook.
• Staff audit log: /up audit.
• Crash recovery: interrupted rollbacks resume after a restart.
• CoreProtect importer: /up import-coreprotect. See Migrating from CoreProtect.
• Database compaction: /up compact, optionally automatic with retention.aggregate-after-days. See Purge.
• New logged actions: inventory transactions, drops and pickups, villager trades, entity spawns, teleports, username history.
• Granular block state logging as -block and +block.
• Advanced search and pagination: long parameter names, f: filters and /up lookup <page>:<rows>.
• Execution flags: #preview, #verbose, #silent, #optimize, #command, #dry.
• Granular purging by radius, world, block type or entity kills.
• Configuration and filtering: blacklist.txt (id@user syntax) and per-world settings.
• Developer and client APIs: CoreProtect API v13 style API and a networking API for client mods such as Watson.

Changed

• Refreshed chat UI in a green-and-white theme.
• 20-line chat limit: long results are split into clickable pages that account for wrapped lines (chat.width-px).
• DuckDB is the default database for new installations.
• Generated config files no longer contain comments.

---

Related pages: Home · Commands