Minecraft plugin CoreProtect

🔌 About CoreProtect

CoreProtect — is a plugin for Minecraft servers that provides fast, efficient data logging, lookup and rollback/restore tools for server administrators. CoreProtect records many player and world events so you can inspect changes, search historical actions, and quickly rollback or restore damage with minimal impact on server performance.

🎯 Purpose

CoreProtect is designed to solve griefing, accidental damage, or any situation where you need to determine "who did what" and optionally revert it. It is built for servers that require reliable, low‑overhead logging and fast rollbacks on Paper and Spigot platforms. CoreProtect runs multi‑threaded to avoid significant TPS impact. ()

⚙ Core features

• Fast, efficient block/entity/action logging (SQLite by default). ()
• Advanced lookup and paginated results with filters (user, time, radius, action, include/exclude). ()
• Rollback and restore operations with preview and undo support. ()
• Block inspector mode for quick in‑game inspection of who placed/used blocks. ()
• Optional MySQL support and database migration tools (some migration features are Patreon builds). ()
• Multi‑world support, WorldEdit integration, liquid/tree tracking, container/inventory logging, chat and session logging. ()

🧩 Who it's for

CoreProtect suits server owners, admins, and moderators who run:

• Survival and towny servers
• Large networks and multi‑world servers
• Servers that need robust anti‑griefing tools with fast rollbacks

🏗 Example uses

• Inspect who placed a suspicious block using the inspector and revert a griefed area with /co rollback.
• Lookup inventory transactions or chest activity to investigate item theft.
• Purge old log data to reduce disk usage while keeping recent history.

⌨️ Commands

Use the primary command prefix /co. (Full command reference available in the documentation.) ()

Notes: /co near and /co undo are aliases. See official docs for parameter examples and pagination. ()

🔐 Permissions

CoreProtect uses the Spigot permission system. The main permission nodes and defaults are listed in the official docs. ()

If you do not wish to require op for /co, configure permissions via your permissions plugin (LuckPerms, etc.). ()

⚙ Installation

📥 Installation

• Download the CoreProtect .jar from the official downloads. ()
• Place the .jar in your server plugins/ folder.
• Start or fully restart the server (do not use /reload).
• Verify the plugin initializes and that logs mention the version in console (/co status). ()

📦 Dependencies

• CoreProtect does not require external economy/chat libraries to run — it functions standalone. Documentation lists SQLite as the default storage and optional MySQL support. No mandatory external plugin dependencies are required. ()

🧾 Configuration

• The documentation states CoreProtect works out of the box with minimal configuration; optional settings are available in the docs. If you change config files, restart the server or use /co reload. Some Patreon builds include extra migration utilities. ()

🔁 Database support

• SQLite is used by default for local storage.
• MySQL is supported for larger servers; migration tools exist (some features limited to Patreon builds). ()

🧠 Additional information

Known conflicts & limitations

• CoreProtect logs many event types and integrates with WorldEdit, but any server using multiple log/rollback plugins should test interactions on a staging server first. Documentation and community guidance should be consulted for proxy/distributed setups. ()

FAQ

1. Can CoreProtect rollback WorldEdit actions? — Yes; CoreProtect logs and can rollback many WorldEdit changes (see lookup/rollback parameters). ()
2. Does CoreProtect require MySQL? — No. SQLite is default; MySQL is optional for larger setups. ()
3. Is there a GUI? — CoreProtect is command/in‑game inspector driven; output is paginated text. ()
4. Are database migrations supported? — Migration between SQLite and MySQL is available; note that some migration features are Patreon builds. ()

Telemetry & support

• CoreProtect includes telemetry/statistics tooling referenced in the project (bStats presence indicated in the repo). ()
• Official support channels: GitHub issues and Discord (official invite listed in the project resources). ()

When adding CoreProtect to a Paper/Spigot network, follow the documentation for large‑scale deployments and database tuning. For full command reference and permission details consult the official docs. ()