Terabit
Back to knowledgebase
Minecraft

How to Protect Your Minecraft Server Against Griefing with CoreProtect

Set up CoreProtect, investigate grief quickly, and roll back damage safely using a repeatable workflow for beginner server admins.

March 29, 2026 by Terabit Editorial / 3 min read

MinecraftCoreProtectAnti-GriefingServer Security

CoreProtect is one of the most practical anti-griefing tools for Minecraft Java servers because it gives you evidence first, then rollback controls second. If you run a public or semi-public server, this should be part of your default moderation stack.

What CoreProtect gives you that manual moderation cannot

Without block logging, grief reports become guesswork. With CoreProtect, you can answer three key questions quickly:

  • Who changed this block?
  • When did it happen?
  • How much should be reverted?

That combination lets you roll back only the damage you want, instead of restoring from a full backup and affecting innocent players.

For command behavior and parameters, use the official command reference: CoreProtect Commands.

Before you begin

  • Use a modern Java server stack such as Paper. If needed, see Paper Getting Started.
  • Make sure you can access your server console or have operator permissions.
  • Install plugins only from trusted sources and verify version compatibility.

Install and confirm CoreProtect is working

  1. Install the plugin and restart the server.
  2. Run /co status in console or in-game.
  3. Confirm there are no startup errors in logs.
  4. Place and break a test block in spawn.
  5. Run /co i and click the test area to confirm actions are being logged.

If inspect mode reports placement/break history, logging is active.

Fast incident response workflow

Use this exact flow when you receive a grief report:

  1. Go to the damaged location.
  2. Enable inspector mode with /co i.
  3. Click affected blocks to identify likely users and timestamps.
  4. Run a lookup to scope damage by user, time, and radius.
  5. Preview and execute the rollback only after the scope looks correct.

Start narrow. A broad rollback creates avoidable side effects.

Command patterns you will use most

/co i
/co lookup u:PlayerName t:2h r:30
/co rollback u:PlayerName t:2h r:30
/co restore u:PlayerName t:2h r:30
/co rollback u:PlayerName t:2h r:30 #preview
/co purge t:30d

Notes:

  • lookup finds data; rollback reverts it; restore undoes a rollback.
  • #preview lets you validate scope before committing.
  • purge controls database growth by deleting old log data.

All parameters and examples are documented here: CoreProtect Commands.

Keep your data useful over time

CoreProtect is strongest when retention is intentional.

  • Keep enough history to cover your usual dispute window (for many communities, 14 to 30 days is a good start).
  • Schedule periodic purges to avoid unbounded database growth.
  • Review storage settings as your server scales.

For permissions design (who can inspect vs rollback), use CoreProtect Permissions.

Common mistakes to avoid

  • Rolling back globally when the incident is local.
  • Skipping lookup and guessing the guilty player.
  • Running rollback commands without a time window.
  • Giving rollback access to too many staff members.
  • Never purging old data.

Trusted references